primea / js-primea-hypervisor Goto Github PK

add precompile wast files.

Version 1.5.0 of ethereumjs-block just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-block is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Since JS currently doesn't support i64 values some function of the ethereum system interface will not correctly.

This can be fixed by transcompiling any import that has a i64 params to be two i32 params and transcompiling the where it get called

The other option would just to be to limit the system interface to only have i32 params

Version 0.25.1 of ipfs just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ipfs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

binaryen has these modules now:

wasm.js: wasm.js contains Binaryen components compiled to JavaScript, including the interpreter, asm2wasm, the S-Expression parser, etc., which allow you to use Binaryen with Emscripten and execute code compiled to WASM even if the browser doesn't have native support yet. This can be useful as a (slow) polyfill.

binaryen.js: A stand alone library that exposes Binaryen methods for parsing s-expressions and instantiating WASM modules in JavaScript.

This would eliminate the latest node.js as a prerequisite.

See ethereum/EIPs#150.

• move ports
  • get instance by path
  • signal when moved
    • update non-entryport channels
• send ports in message
• copy ports
• port introspection
  • get type (message / contract / storage)
  • get value
  • get id
• iterate ports
  • order map
• id introspection
• get parent
• get nonce

As an example IO container it could be commandline based.

Two messages to consider:

• send -> prints out the payload with the instance identifier
• receive -> prompts for input with the instance identifier

[1234] < "Hello World"
[1234] > nooooo!

Remove once V8/node is fixed. See https://bugs.chromium.org/p/chromium/issues/detail?id=633895

add the async interface

If it is desired to run Solidity contracts, the VM needs to support precompiles, especially the identity contract.

Implement the precompiles in WASM:

• ecrecover
• sha256
• ripemd160
• identity

Version 9.0.0 of standard just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As standard is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

See https://deterministic.js.org/.

Version 5.1.0 of ethereumjs-util just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-util is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.13.0 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.1.3 of ethereumjs-tx just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-tx is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.2.4 of ethereumjs-tx just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-tx is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

wasm start is currently disallowed. The codeHandler always tries to run main. start is currently a problem since it starts running immediately and there is no way to populate the interface with the wasm instance.

Version 2.12.0 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Chakra-Node sources here: https://github.com/nodejs/node-chakracore

Version 4.6.3 of tape just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tape is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Currently according the wasm JS api all imported function are sync.

This maybe resolved in the Future but for now it doesn't look like an option

Version 8.6.0 of standard just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As standard is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.3.0 of ethereumjs-tx just got published.

This version is covered by your current version range and after updating it in your project the build failed.

ethereumjs-tx is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Carry over from last meeting where we briefly discussed the possibility of a Function Stye API
Here is a really rough sketch of what it might look like

var Environment  = require('ewasm-kernel/environment')
var runTx        = require('ewasm-kernel/runTx.js')
var kernel       = require('ewasm-kernel')

// all state is stored in the Environment 
var environment = new Environment()

// run a tx
var resultingEnvironment  = runTx(tx, environment)
// make a direct call
resultingEnvironment = kernel.callHander('0xaddress', resultingEnvironment)

....
// Debugging
var DebugInterface = require('ewasm-kernel/debugInterface.js')
// get some code from the state
var code = resultingEnvironment.state.get('0xaddress')

var interface = new DebugInterface(resultingEnvironment)
// create a new ewasm instance given some code and a debuging interface
var contractInstance = kernel.codeHandler(code, interface)
// run a contract's method. This is not functional, `resultingEnvironment` would be change here
contractInstance.method()

thoughts? @axic @kumavis

The devDependency coveralls was updated from 3.0.4 to 3.0.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

the kernel isn't a kernel
alternatives

• containerInterface
• containerManager
• actor

// fun c r a z y stuff

• sysInterface
• containerShell
• containerSkin

Version 4.6.2 of tape just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tape is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.1.4 of ethereumjs-tx just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ethereumjs-tx is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.0.0 of documentation just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As documentation is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.13.1 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴