embarklabs
/
embark
mirror of https://github.com/embarklabs/embark.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
embark/src/lib/constants.json

79 lines
1.8 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",
Changed scaffolding to service
2018-10-05 23:13:00 +00:00
"scaffold": "scaffold",
get context from cmd ran and use arrays of contexts
2018-04-25 14:34:17 +00:00
"test": "test",
"reset": "reset",
check context and on changing context, load plugins that work
2018-04-24 18:42:56 +00:00
"any": "any"
},
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": {
refactor(blockchain/accounts): refactor blockchain config accounts
2018-11-21 21:57:58 +00:00
"clients": {
"geth": "geth",
"parity": "parity"
},
finish hiding logs
2018-05-22 18:13:56 +00:00
"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 is livenet
2018-08-23 10:06:47 +00:00
"livenet": 1,
warn if mismatch on network id
2018-07-31 13:59:27 +00:00
"testnet": 3,
"ropsten": 3,
"rinkeby": 4
fix(deployment): add a message when the errror is about the input
2018-11-15 19:19:44 +00:00
},
"gasAllowanceError": "Returned error: gas required exceeds allowance or always failing transaction",
"gasAllowanceErrorMessage": "Failing call, this could be because of invalid inputs or function guards that may have been triggered, or an unknown error."
add storageProcessesLauncher that can work for swarm or ipfs
2018-05-23 19:10:53 +00:00
},
"storage": {
"init": "init",
fix(@embark/core): Restart IPFS after CORS Update When adding URLs to IPFS CORS that are not localhost, the IPFS daemon needed to be restarted after non-localhost CORS updates were added to the IPFS config. Without the restart, any non-localhost URLs added to the CORS were not being sent in the CORS header. After this change, when the IPFS process is run, the following happens: 1. IPFS config is checked if the correct CORS settings are present in the config. 2. If not present, they are updated and IPFS is restarted. 3. If they are present, continue without restarting IPFS.
2018-11-28 01:46:47 +00:00
"initiated": "initiated",
"restart": "restart"
use constants instead of magic numbers
2018-10-16 15:16:47 +00:00
},
"tests": {
"gasLimit": 6000000
},
"codeGenerator": {
"gasLimit": 6000000
Addressed PR comments *Console.js* - Moved `DEFAULT_PROCESS` const to outside of the `Console` class (but inside the module). - Removed `(` and `)` from `.filter` in `getProcessLogs()`. - Updated comments *logger.js* - Moved `dateFormat` and `logRegex` to constants outside of `Logger` class - Moved the `parseLogFile` method inside of the `Logger` class (ES6 style) - Added a log limit to the `parseLogFile` method - Added the log path to the constants file and used inside of `Logger` *cmd_controller.js* - Defaulted `this.context` to `[constants.context.any]` in the constructor. - Changed `’embark’` to split modules`coreProcess` and `loggerApi`. *engine.js* - Changed `’embark’` to split modules`coreProcess` and `loggerApi`.
2018-10-09 23:15:39 +00:00
},
"logs": {
Embark blockchain logs when running standalone When running `embark blockchain` followed by `embark run` previously, logs generated in the standalone `embark blockchain` process were black boxed and not accessible to the main Embark process. This is fixed by creating a client IPC connection in the `embark blockchain` process that connects to the IPC server connection running in `embark run`. The connection is made by way of polling `ipc.connect` and continues polling even after a connection is made in case `embark run` is killed and restarted without restarting `embark blockchain`. `LogHandler` was introduced to extrapolate functionality used in `ProcessLauncher` that needed to also be used in the standalone blockchain process. It also caps the number of logs that are stored in memory per process by a constant value defined in `constants.json`. A `blockchain_listener` was module was created (and run inside of `embark run`) that listens for logs emitted by the `embark blockchain` client IPC and runs them through the `LogHandler`. Additionally, this module registers the API endpoints needed to handle requests for blockchain process logs in the cockpit (which were 404’ing before). # Conflicts: # lib/modules/blockchain_process/blockchain.js
2018-10-22 12:56:14 +00:00
"logPath": ".embark/logs/",
"maxLogLength": 1500
feat: strategy for deployment Allow implicit and explicit for deployment strategy implicit: all contracts are deployed explicit: only specified contracts are deployed Default value: implicit
2018-11-07 11:35:51 +00:00
},
"deploymentStrategy": {
"implicit": "implicit",
"explicit": "explicit"
Merge branch 'master' into feature/deployment-strategy
2018-11-08 21:35:04 +00:00
},
refactor(ENS): adds a whitelist for ens Enables only the use of domains in that white list
2018-11-22 13:47:39 +00:00
"embarkResourceOrigin": "http://embark",
"ens": {
"whitelist": [
"eth",
"xyz"
]
}
fix(deployment): add a message when the errror is about the input
2018-11-15 19:19:44 +00:00
}