Peter Us
Peter Us
Thank you very much for the contribution (and sorry for long response :()! I just recently updated the test suite a bit and added a CI setup. Would you please...
> Hm, the common committee node (go/worker/common/committee/node.go) doesn't seem to be invoking the new history-backed WatchBlocks? This could cause problems as now it doesn't wait for any history reindexing? Yeah...
what are the logs on the peer side in this case? i assume it could be the `"cannot connect to any peers, failing back to seeds"`? so this could explain...
i'm saying that this seednode dialing could be fine (e.g. seed returning the correct peers), but if then for some reason the dialing node couldn't connect to any of the...
@dependabot rebase
Some context from when i looked into it awhile back, in case anyone will look into this more: what happens in the failed round: the proposer's runtime processing takes ~4...
This should be possible with oasis-core#22.0 by using runtime message results.
This is likely an issue on the `oasis-node` side. Can you provide the output of running: ``` oasis-node control status -a unix: ``` and logs from the oasis-node around the...
will be done in https://github.com/oasisprotocol/emerald-web3-gateway/pull/225
nvm, this was not fixed properly, will need one more fix