Frank Mueller 1c8d32c451 Ensuring node synchronisation to avoid "no suitable peers available" errors (#410) ... During CI tests non-deterministic failures with "no suitable peers available" happened. Reason is a not finished synchronisation after starting of node. Added and integrated an EnsureSychronization() almost solved it, but overlapped with new added EnsureNodeSync() in merged develop. Failure stayed, so exchange new algorithm in EsureNodeSync() with former one.		2017-10-21 20:04:07 +03:00
..
faucetcmd.go	Fixed: faucet now accepts HTTPEnabledFlag	2017-08-17 15:58:08 +07:00
lescmd.go	Merging bug/whisper-on-geth1.6.1 (#236) which acts like develop	2017-08-04 23:14:17 +07:00
library.go	Fix make lint warnings (#417)	2017-10-20 12:06:22 +03:00
library_test.go	Validate JSON config (#240)	2017-08-10 22:31:29 +07:00
main.go	Fix make lint warnings (#417)	2017-10-20 12:06:22 +03:00
misccmd.go	cmd/statusd: faucet sub-command added, refs #159	2017-05-16 10:51:11 +03:00
utils.go	Ensuring node synchronisation to avoid "no suitable peers available" errors (#410)	2017-10-21 20:04:07 +03:00
wnodecmd.go	Move accounts to separate package (#360)	2017-09-26 15:44:26 +02:00