Commit Graph

98 Commits

Author SHA1 Message Date
Andre Medeiros 8be8ca508f Fix failing test on blockchain 2018-08-21 15:33:00 -04:00
Jonathan Rainville a3d612f8ba remove use of initConfig 2018-08-21 15:30:43 -04:00
Jonathan Rainville ff340fe88c remove useless change 2018-08-21 15:30:10 -04:00
Jonathan Rainville 01900f8c6e wip fixes 2018-08-21 15:26:31 -04:00
Jonathan Rainville 18f60768f9 fix when using mining script 2018-08-21 15:21:24 -04:00
Jonathan Rainville fcbd4739dc only put isDev when specifically set 2018-08-21 15:20:11 -04:00
Jonathan Rainville cf403df1fb make it work 2018-08-21 15:18:12 -04:00
Jonathan Rainville 3e65d1c11b add geth miner. Needs to change eth and web3 2018-08-21 15:18:12 -04:00
Jonathan Rainville 1970f8fc53 use right path depending of os 2018-08-21 15:18:12 -04:00
Jonathan Rainville 5581964fab conflict in package json 2018-08-21 15:17:05 -04:00
emizzle bcd5593040 Updated online/offline event checks so they are run during initialisation.
Changed the online event to `once` and set it to be bound every time the node goes offline.

The above changes handle the case where:
1) `embark run` runs and starts geth.
2) geth is killed manually
3) `embark blockchain` is run in separate process to restart geth
4) the `embark run` process detects this change and restarts the web3 provider and recompiles/deploys/builds

Every time `embark blochain` is restarted, an error is appended and all are emitted from the `eth-block-tracker`. This is a bug but can't figure out where it originates. The downside is that if, for example, `embark blockchain` is restarted 4 times, there will be 4 errors emitted from the `eth-block-tracker`. Because of this, errors emitted from `eth-block-tracker` have been reduced to trace to avoid clogging the logs.
2018-08-21 15:08:25 -04:00
emizzle ee59d43c77 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-08-21 15:08:25 -04:00
Michael Bradley, Jr d70264adb6 blockchain -- defaultHost, dockerHostSwap 2018-08-02 15:31:55 -05:00
emizzle 9b41fa8ac2 Modified DevFunds to “factory pattern”
Added a “factory pattern” to DevFunds to allow for async calls to be made during object construction. This allows for `web3.eth.getAccounts` to be called and the `accounts` property assigned on instantiation.

This modification allows each unit test case to be run independently of the others.
2018-08-01 11:35:42 +10:00
emizzle 7cb9cd5622 Basic unit tests complete for dev funds
Finished added unit tests for dev_funds. These are weak tests as the FakeIpcProvider does not provide enough support for keeping track of accounts and balances and instead we are injecting the provider responses in the tests, which kind of defeats the purposes of the tests. Instead, the FakeIpcProvider should be a little smarter and do more of what a real node would do.
2018-07-31 14:59:55 +10:00
Iuri Matias 69f356b3f0 only use personal in --dev mode 2018-07-19 10:58:47 +03:00
emizzle 9382f98933 Housekeeping and removal of none additions
Clean up debugging statements from fund_accounts.

Removed the addition of the nonce increment for contracts deploy as this was only affecting mneumonic-generated accounts which is not meant for dev environment.
2018-07-18 14:08:32 +02:00
Iuri Matias 91f1748d60 don't wait for account funds 2018-07-17 17:30:23 +03:00
emizzle 11d6980f70 further dev funding 2018-07-16 18:48:32 +02:00
Iuri Matias f2213970f7 first stab at funding accounts in geth given config 2018-07-13 15:56:59 +03:00
Jonathan Rainville da01ab15db enable using both syncMode and syncmode 2018-07-06 09:31:28 -04:00
Iuri Matias 289be4b8a4 check for cmd not found in stderr 2018-07-04 16:40:46 +03:00
Iuri Matias a7a6a62edc make linter happy 2018-07-04 16:36:49 +03:00
Iuri Matias 6c03a2e212 ignore stderr since geth outputs normal logs to it 2018-07-04 16:10:12 +03:00
Jonathan Rainville ffb3ec544b fix account initialization and address use 2018-07-03 14:55:04 -04:00
Iuri Matias 76ab330546 add debug option 2018-06-18 09:44:16 -04:00
Jonathan Rainville d77083ee8c enable syncMode 2018-06-15 16:33:59 -04:00
Iuri Matias e0ff5b3580 remove anoying backtrace 2018-06-12 13:58:21 -04:00
Richard Ramos 9e92069667 Fixing conflicts 2018-06-11 16:44:34 -04:00
Richard Ramos 38e6a9571d Updating tests 2018-06-11 16:43:26 -04:00
Richard Ramos 48a3f2afdc Fixing conflicts 2018-06-11 16:43:08 -04:00
Iuri Matias a4985fde40 make proxy mode the default 2018-06-11 16:40:59 -04:00
Richard Ramos 0f853ba841 Typo 2018-06-11 16:40:59 -04:00
Richard Ramos c1621c4029 Websocket support 2018-06-11 16:40:59 -04:00
Richard Ramos bf25381fa6 Rebasing changes from develop 2018-06-11 16:40:14 -04:00
Richard Ramos 05f5a145f1 Added proxy to blockchain 2018-06-11 16:38:29 -04:00
emizzle a11047c681 Further fixes for starting dappConnection processes automatically
moved storage process launching to storage module

refactored all cases of storage url building to util methods

updated cors so that a processes will not include itself in cors list

changed child process command console output to trace, so it's visible when --logLevel == trace
2018-06-01 13:36:46 +10:00
emizzle 927f562a41 Fixed issue with CORS domains for auto-started geth, swarm, and ipfs processes.
Fixes after rebase:
* De-duped i18n en.json
* Re-built package-lock.json

Current WIP is auto-starting storage processes defined in dappConnection config.
2018-06-01 13:35:25 +10:00
Jonathan Rainville 138aaf39ff fix processes on ubuntu 2018-05-30 11:03:33 -04:00
Jonathan Rainville 2f3a94f3a1 little fixes 2018-05-30 11:03:33 -04:00
Jonathan Rainville 2023689eb2 fix tests 2018-05-30 11:03:33 -04:00
Jonathan Rainville 8655b49a39 change ipfs to spawn too 2018-05-30 11:03:33 -04:00
Jonathan Rainville 3f671c2fb0 conflict in en.json 2018-05-30 11:03:33 -04:00
Jonathan Rainville d36af9f5e1 fix blockchain start 2018-05-30 11:03:33 -04:00
Jonathan Rainville 4e20e82edf conflict in blockchain 2018-05-30 11:03:33 -04:00
Jonathan Rainville e67fafdc29 conflict in en.json 2018-05-30 10:57:25 -04:00
Eric Mastro cfcdc0e15d Changed path depth warning to path length
* Updated the path depth warning to check that the dapp path length is <= 66 characters.
* Updated the blockchain process to silent:false when loglevel == trace.
* Updated the path warning so that it would appear in the console regardless of loglevel (and silent:true)
2018-05-25 13:42:18 +10:00
Iuri Matias 99b931d230 rename method 2018-05-23 12:33:59 -04:00
Iuri Matias fe4dd67979 warn about path depth 2018-05-23 12:33:21 -04:00
Jonathan Rainville 1bca31184e always show process messages if error and catch geth errors 2018-05-23 11:17:03 -04:00