Tomasz Kajetan Stańczak
Tomasz Kajetan Stańczak
Was running it with Nethermind node so I will need to check if the data format is unexpected - still it should not cause server to crash.
progress: 1 } 0|node-app-goerli | 2019-01-04 21:53 +00:00: [eth] =i= SYNC UPDATE: { startingBlock: 0, 0|node-app-goerli | 2019-01-04 21:53 +00:00: currentBlock: 317791, 0|node-app-goerli | 2019-01-04 21:53 +00:00: highestBlock: 317791, 0|node-app-goerli...
including output from the logs of eth-net-intelligence-api
seems that that our current test version has getLatestBlock JSON RPC failures
logs on Nethermind side look fine now (but I was fixing BigInteger parsing just today so maybe the new version solves it) 2019-01-04 23:19:35.9323|TRACE|49|JsonRpc.Modules.ModuleBase|eth_syncing request, result: 318134/318134 2019-01-04 23:19:36.4326|TRACE|54|JsonRpc.Modules.ModuleBase|eth_syncing request,...
Depends on #2995
Thanks @MaxTeiger -> @cbermudez97 will look at running Sokol smoke tests and will recommend you the best course of action (but he will only be online in around 3 hours).
has some disadvantages too, does not allow for any quick fixes and adjustment or config fixes without release