David Lutterkort
David Lutterkort
This requires rewinding all your subgraphs. I put instructions on how to do that [here](https://github.com/graphprotocol/mission-control-indexer/tree/master/utils/db)
I've added links to the tracking issues to the text. I agree that it's unfortunate that we have these open to dos in there, but I also think it accurately...
This here causes me headaches: > **Should we go straight to custom ID fields (e.g. hash and number for blocks) or stick to id for the initial pass? (My recommendation:...
On second thought, I wonder if we shouldn't just do these checks every time `graph-node` starts and complain loudly if one of them fails. A problem in cross-shard comms will...
@Zerim one thing I don't understand about uncles is that they only need to have valid block headers, which means to me that that is all you can reliably query...
Yes, that would be a way to fix that - we'd need to select the replica at the beginning of the query and use it to process everything. But that...
They are not needed for copy/grafting; `graph-node` handles that already by picking the right shard/foreign schema as needed. The problem with these views is in how they interact with updates...
It is ready for review in the sense that it does what it claims to do, but it introduces a bunch of machinery whose full value we'd only reap if...
Rebased to latest master and addressed review comment
Yes, very much. Waiting on @saihaj to be ready to try this out and incorporate it into `graph-cli`