status-im
/
embark-area-51
mirror of https://github.com/status-im/embark-area-51.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
embark-area-51/lib/constants.json

54 lines
1.2 KiB
JSON
Raw Normal View History

add code to import in solcP
2018-04-19 18:26:11 +00:00
{
check context and on changing context, load plugins that work
2018-04-24 18:42:56 +00:00
"httpContractsDirectory": ".embark/contracts/",
"contexts": {
"simulator": "simulator",
"blockchain": "blockchain",
get context from cmd ran and use arrays of contexts
2018-04-25 14:34:17 +00:00
"templateGeneration": "templateGeneration",
"run": "run",
"upload": "upload",
"build": "build",
Adding light monitor
2018-07-23 09:36:53 +00:00
"console": "console",
get context from cmd ran and use arrays of contexts
2018-04-25 14:34:17 +00:00
"graph": "graph",
"test": "test",
"reset": "reset",
check context and on changing context, load plugins that work
2018-04-24 18:42:56 +00:00
"any": "any"
},
"events": {
redeploy with right config on config change
2018-04-27 19:10:24 +00:00
"contractFilesChanged": "contractFilesChanged",
"contractConfigChanged": "contractConfigChanged"
make pipeline js in a different process (still doesnt work)
2018-05-07 18:30:30 +00:00
},
add eventWrapper not tested
2018-05-15 21:08:08 +00:00
"process": {
clonflict for silent
2018-05-28 15:48:27 +00:00
"processLaunchRequest": "process:launch-request",
"processLaunchComplete": "process:launch-complete",
add eventWrapper not tested
2018-05-15 21:08:08 +00:00
"log": "log",
"events": {
"on": "on",
"request": "request",
"response": "response"
}
},
make pipeline js in a different process (still doesnt work)
2018-05-07 18:30:30 +00:00
"pipeline": {
"init": "init",
"build": "build",
"initiated": "initiated",
add eventWrapper not tested
2018-05-15 21:08:08 +00:00
"built": "built"
finish hiding logs
2018-05-22 18:13:56 +00:00
},
"blockchain": {
"blockchainReady": "blockchainReady",
Handle geth process exit via crash/kill and also via killing `embark blockchain` First case - run `embark run` which starts a blockchain node, then manually kill the `geth` process. Would throw `{ [Error: connect ECONNREFUSED 127.0.0.1:8543] message: 'connect ECONNREFUSED 127.0.0.1:8543', code: -32603 }` error and ruins the dashboard. Second case, 1) run `embark blockchain` 2) run `embark run` 3) kill `embark blockchain` throws the error `{ [Error: connect ECONNREFUSED 127.0.0.1:8543] message: 'connect ECONNREFUSED 127.0.0.1:8543', code: -32603 }` and ruins the dashboard. The first case was solved by having the child blockchain process that spawns geth listen for geth exit, then kill itself. The second case required updating of `eth-block-tracker` to v4.0.1 inside of the `embark-web3-provider-engine`. v4.0.1 was a major version update and introduced breaking changes. Those changes were handled inside of `embark-web3-provider-engine`, covered in **blocker** PR https://github.com/jrainville/provider-engine/pull/1.
2018-06-22 12:52:15 +00:00
"blockchainExit": "blockchainExit",
finish hiding logs
2018-05-22 18:13:56 +00:00
"init": "init",
Fixing conflicts
2018-06-11 20:43:08 +00:00
"initiated": "initiated",
warn if mismatch on network id
2018-07-31 13:59:27 +00:00
"servicePortOnProxy": 10,
"networkIds": {
"mainnet": 1,
"testnet": 3,
"ropsten": 3,
"rinkeby": 4
}
add storageProcessesLauncher that can work for swarm or ipfs
2018-05-23 19:10:53 +00:00
},
"storage": {
"init": "init",
"initiated": "initiated"
check context and on changing context, load plugins that work
2018-04-24 18:42:56 +00:00
}
add code to import in solcP
2018-04-19 18:26:11 +00:00
}