Leonardo Yvens

Actually in a call by block hash going to the block cache is always necessary anyways, so this wouldn't add overhead in that case which is the relevant one in...

Great stuff! One thing I hadn't previously considered is handling reverts. In the DB we get that for free, but we need to also revert the in-memory state. It might...

This PR is now sufficient to to merge for internal testing, after review and integration cluster of course. There is a severe though infrequent known bug, which is that if...

Integration cluster shows no divergences, merging!

@colonelssecretspices That would be a new issue affecting decoding call triggers, this issue is about handlers that do not exist in the mapping.

@obernardovieira After #2797 the error message should become more specific. If you could reproduce again and send me the subgraph id on Discord I can try to look into the...

At the moment you have to run nginx in front of graph-node to expose subscriptions and queries on the same port. The support for subscriptions in graph-node has issues and...

@j-mars Looks like the port is already in use by another process in your system. That issue is not specific to graph node.

We hit this issue when multiplexing many grpc streams on a same channel with tonic. The fix for us was to set a very high connection window size, to try...

I believe the [lack of Send bounds](https://github.com/rust-lang/rust/issues/103854) would need to be resolved for async fn in traits to be suitable for tower.