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

106 lines
2.5 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/",
chore: move console to module
2019-05-01 20:00:04 +00:00
"console": {
"commandHistorySize": "20"
},
check context and on changing context, load plugins that work
2018-04-24 18:42:56 +00:00
"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",
feat(@embark/core): improve long running webpack UI The webpack process took quite a while to run, and there were no updates in the console while running. This PR adds a spinner (when there is no dashboard) and status updates every 5 seconds. When there is a dashboard, the updates are added to a new line. After (with dashboard): ![with dashboard](https://i.imgur.com/zVJH5U4.png) After (`—nodashboard`): ![no dashboard](http://g.recordit.co/2zRNLt51jU.gif) Convert LongRunningProcessTimer to TypeScript PR feedback and consistency changes Changed the constructor signature to accept an options object instead of individual optional parameters, for readability. Changed library_manager to use the spinner when not using the dashboard, for consistency’s sake. Additionally increased the update time for the library manager from 750ms to 1s. Fix lint errors Added `"variable-name": ["allow-leading-underscore”]` to `tslint.json` due to a lack of the ability to prefix backing variables with underscore. This is an [ongoing discussion](https://github.com/palantir/tslint/issues/1489), and something the community thinks should be implemented, as it the preferred way to use a property with backing variable in TypeScript.
2018-11-30 03:11:18 +00:00
"built": "built",
"webpackDone": "webpackDone"
finish hiding logs
2018-05-22 18:13:56 +00:00
},
"blockchain": {
refactor(embark-ui): improve cockpit's contracts explorer Rename contract "Transactions" tab to "Log". Display and allow filtering of all contract methods. Disable debug button for pure/view functions and the constructor. Revise the filtering logic so that filters are combined together. Make the status filter a drop down menu like the others. Revise styling for consistent row height, alignment of text, and button sizes; use a monospaced font in some cases to achieve the effect. Handle enter/return correctly in forms within a contract's Interact tab. Remove event rows from a contract's Interact tab. Track pure/view calls in the blockchain proxy so they can be logged server-side by console listener and reported in Cockpit within a contract's Log tab. Eliminate double logging in the contracts manager. Ensure contracts deployed on a fresh `embark run` have an `address` / `deployedAddress` property.
2019-03-05 22:45:18 +00:00
"call": "eth_call",
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",
refactor(@embark/blockchain): support --simple dapps DApps generated with `new --simple` don't have a blockchain config so ensure that the blockchain proxy and listener (dev_txs) use appropriate provider settings when setting up web3. Without these changes, in a fresh `embark new --simple` project the `embark blockchain` command will encounter unhandled promise rejection with respect to the proxy; `embark run` will encounter similar with respect to dev_txs.
2019-08-07 22:54:14 +00:00
"defaults": {
"rpcPort": 8545,
"wsPort": 8546
},
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,
feat(@embark/proxy): Add dev tx to proxy when request fails to get response Create a dev tx (a 0-value tx that is sent from the —dev account to itself) when a request goes through the proxy, but does not get a response after 5 seconds. Log requests to disk (when log level is trace - enabled with the embark option `—loglevel trace`) that have not received a response and for which a dev tx has been sent. Add logging to a `proxyLogs.json` log file as well, so that this information can be gleaned later for debugging purposes. This particular PR Is meant to workaround an issue with running geth with the `—dev` option, as some transactions appear to get stuck, which then builds up further txs in a queue. Only when another tx is sent is the queue then purged as expected. The remaining issue is that even though a dev tx is sent to relieve the queued txs, the originally offending tx still never receives a response from the node. This was the motivation behind creating a proxy log, so that a dev can inspect the txs that are essentially dropped. **NOTE:** the base branch of this branch is `refactor/devfunds`. Please merge that branch first.
2019-04-04 08:52:09 +00:00
"rinkeby": 4,
"development": 1337,
"development_parity": 17
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",
fix(@embark/core): Proxy support for raw transactions Contract logs were not occuring in the test_app for reasons unknown, except that it seemed to be pinned to the fact that accounts were being defined using a mnemonic. Turns out this caused transactions to be signed, and therefore sent using `eth_sendRawTransaction`. Add ability to decode raw transactions in the proxy so that those transactions are also logged. Refactor Proxy in to a class and add a Proxy unit test test. Remove RLP package, as there is another way to decode a tx without needed an additional package. Replace eth transaction methods with constants throughout the codebase. Add unit tests for Console Listener.
2018-12-14 03:42:40 +00:00
"gasAllowanceErrorMessage": "Failing call, this could be because of invalid inputs or function guards that may have been triggered, or an unknown error.",
"transactionMethods": {
"eth_sendTransaction": "eth_sendTransaction",
"eth_sendRawTransaction": "eth_sendRawTransaction",
"eth_getTransactionReceipt": "eth_getTransactionReceipt"
refactor(@embark/blockchain_process): Refactor dev_funds Change name “DevFunds” to “DevTxs”. Remove unused functions in dev_funds (create accounts, unlock accounts, fund accounts). Add console command `sendtx` to send a one-off dev transaction. Modify the dev tx to send a 0-value tx to itself (ie the `web3.eth.defaultAccount` which is the `—dev` account). Deprecate the command `regularTxs on/off` in favour of `devtxs on/off` (notice the casing). Strip regulartxs from cockpit and modify the browser warning to instruct users to run a console command.
2019-04-04 02:59:41 +00:00
}
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",
feat(@embark/storage): Add command `service ipfs on/off` Add support for ability to start and stop IPFS via command `service ipfs on/off`. Add support for `ProcessState.Errored` process state in the `ProcessManager`. This allows for processes being launched and stopped to trigger an error and the resulting process will be in an errored state. Processes in errored states can still attempt to be started and stopped. `service ipfs on` - starts an IPFS node if not already started. Shows an error if the node is already starting or started. `service ipfs off` - kills the running IPFS node as long as Embark has started the IPFS process. If the IPFS process was started externally, an error is shown. return early
2019-05-02 09:52:13 +00:00
"restart": "restart",
"exit": "storageExit"
use constants instead of magic numbers
2018-10-16 15:16:47 +00:00
},
"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"
]
feat(dapp-config): add dapp connection to dapp config (artifact)
2019-01-23 20:37:53 +00:00
},
feat: enable embark to be run with an external pipeline
2019-02-20 16:19:39 +00:00
"dappArtifacts": {
feat(dapp-config): add dapp connection to dapp config (artifact)
2019-01-23 20:37:53 +00:00
"dir": "config",
feature(@embark/code_generator) generate storage config artifact
2019-01-31 04:58:54 +00:00
"blockchain": "blockchain.json",
"storage": "storage.json",
refactor(generation/embarkjs): generate embarkjs in artifacts dir
2019-02-08 16:41:52 +00:00
"communication": "communication.json",
refactor(generation/contracts): generate contracts to artifact dir
2019-02-08 18:02:42 +00:00
"embarkjs": "embarkjs.js",
feat(@embark/generator): transpile embarkjs.js to be used by node
2019-04-12 16:15:26 +00:00
"embarkjsnode": "embarkjs.node.js",
feat: enable embark to be run with an external pipeline
2019-02-20 16:19:39 +00:00
"contractsJs": "contracts",
"symlinkDir": "modules"
feat(@embark/proxy): Add dev tx to proxy when request fails to get response Create a dev tx (a 0-value tx that is sent from the —dev account to itself) when a request goes through the proxy, but does not get a response after 5 seconds. Log requests to disk (when log level is trace - enabled with the embark option `—loglevel trace`) that have not received a response and for which a dev tx has been sent. Add logging to a `proxyLogs.json` log file as well, so that this information can be gleaned later for debugging purposes. This particular PR Is meant to workaround an issue with running geth with the `—dev` option, as some transactions appear to get stuck, which then builds up further txs in a queue. Only when another tx is sent is the queue then purged as expected. The remaining issue is that even though a dev tx is sent to relieve the queued txs, the originally offending tx still never receives a response from the node. This was the motivation behind creating a proxy log, so that a dev can inspect the txs that are essentially dropped. **NOTE:** the base branch of this branch is `refactor/devfunds`. Please merge that branch first.
2019-04-04 08:52:09 +00:00
},
"environments": {
"development": "development"
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
}
fix(deployment): add a message when the errror is about the input
2018-11-15 19:19:44 +00:00
}