canepat
canepat
https://github.com/erigontech/silkworm/actions/runs/9143609277/job/25140482058 I suspect it's due to missing check on presence of non-empty `params`, but I've not analysed the stack trace properly.
See https://github.com/erigontech/rpc-tests/pull/177 for a list of integration tests where this happens
We're putting very focused effort in stabilising our implementation of `debug` and `trace` API endpoints. This is the main tracking issue. Individual issues are listed below: - [x] #2111 -...
RPC integration tests against E3 fail intermittently often (even if not always) because of `rpcdaemon` unexpected termination: https://github.com/erigontech/silkworm/actions/runs/11576758305/job/32227046300?pr=2463 This started to happen after switching to usage of gRPC for remote...
One of the main features of Erigon3 is moving most of the state content (i.e. account/storage/code) and its validity proof (i.e. commitment) to snapshot flat files. This architectural change requires...
We use some sample header/body/transaction snapshots for unit testing, which were generated without any specific automation some time ago and have a slightly custom format, in the sense they start...
One of the main features of Erigon3 is moving most of the state content (i.e. account/storage/code) and its validity proof (i.e. commitment) to snapshot flat files. This is accomplished by...
One of the main features of Erigon3 is moving most of the state content (i.e. account/storage/code) and its validity proof (i.e. commitment) to snapshot flat files. This architectural change requires...