5 Commits

Author	SHA1	Message	Date
emizzle	4ce7a179fd	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-26 13:02:41 +10:00
Jonathan Rainville	138aaf39ff	fix processes on ubuntu	2018-05-30 11:03:33 -04:00
Jonathan Rainville	7f45b6724a	finish hiding logs	2018-05-23 11:17:01 -04:00
Jonathan Rainville	7e058e5016	set verbosity to 0 in process	2018-05-23 11:17:01 -04:00
Jonathan Rainville	3fcc36a7a1	launch blockchain in separate process ... works but still cant getAccounts	2018-05-23 11:17:01 -04:00