andri lim
andri lim
EDIT: i deleted my comment
I wonder if this is related to `REVERT` abusing the EVM `setError` mechanism. If it is related to `REVERT` after `OOG` then this combination is not covered by eth-tests.
I encounter no assertion error like this when syncing goerli, at least not after calling `persistBlock`
@hmel, can you also post the metamask wallet complete request header and body? because there is possibility it is a [json-rpc](https://github.com/status-im/nim-json-rpc)'s bug.
I see, this is obviously json-rpc problem, it does not recognize both `OPTIONS /` and empty body.
All HTTP local services in nimbus-eth1 have been upgraded to support CORS for both simple and preflighted request. Only websocket services still need upgrade, see status-im/nim-websock#121.
hive will relay the test to https://github.com/ethereum/go-ethereum/tree/master/cmd/devp2p/internal/ethtest from brief glance it looks like ethtest try to connect using `eth/66` first then fallback to `eth/65` or `eth/64`. some of protocol methods...
from windows CI: ``` D:\a\nimbus-eth1\nimbus-eth1\premix\hunter.nim(73, 29) Error: can raise an unlisted exception: Exception ``` this inconsistency probably came from nim stdlib, it's a known old story. some of them already...
> Is the GraphQL code flexible enough to describe what JSON-RPC clients using the above will be looking for? very flexible, you can try our graphql toy server to find...
> Is it difficult to add new types of ad-hoc queries / responses while developing, when you just want to get some new type of data out? It depends on...