8 Commits

Author	SHA1	Message	Date
emizzle	f36dfd0b1c	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 16:34:16 -04:00
Jonathan Rainville	2fe1b05492	use embarkJS secureSend	2018-08-21 16:11:06 -04:00
Jonathan Rainville	c211430fbd	use secureSend for deploy	2018-08-21 16:11:06 -04:00
Jonathan Rainville	083c936351	create separate function for secure send	2018-08-21 16:10:22 -04:00
Iuri Matias	53cd27b87d	move subscriptions listener to blockchain connector module	2018-08-21 16:09:48 -04:00
Jonathan Rainville	e5c498b59d	hotfix network id comparison string vs number	2018-08-21 16:07:58 -04:00
Jonathan Rainville	ca32d7aac0	warn if mismatch on network id	2018-08-21 16:05:59 -04:00
Iuri Matias	4919114f36	move blockchain connection code to its own module	2018-08-21 16:04:22 -04:00