tilacog

@vrmiguel and @marcospb19 would be glad to help!

Thanks for the feedback, @paymog. Can you confirm if the `synced` and `failed` fields are set to the expected values once the subgraph resumes syncing?

A Discord user reported that this error showed up in `0.25.2`. The error message was: ``` Error while processing block stream for a subgraph: store error: number of parameters must...

@azf20 I believe it is. Although, I haven't heard from other users about it since it was reopened.

It seems that [`impl QueryFragment for InsertQuery`](https://github.com/graphprotocol/graph-node/blob/28580bb76178bde5e4174dd5f73b1aed0e706b87/store/postgres/src/relational_queries.rs#L1545) is counting the bindings correctly: one for each field plus one for the block range. But `InsertQuery` delegates `walk_ast` to its columns via...

The Anchor crates compile, but actual usage of `#[program]` breaks compilation. Error from my project: ``` ❯ cargo check Checking registry v0.1.0 (/home/tilacog/tiago/code/eiger/axelar/solana-axelar/solana/programs/registry) error[E0621]: explicit lifetime required in the type...

One possible approach would be to enable all lints as warnings (not errors) and gradually fix each category, then promote that category (now corrected) to errors.

Rebased on top of latest `main`

From what we've seen, the problem with grafting is tied to Graph Node's redeployments. So it's likely that the fix will come from that end. The error some indexers were...

Related: https://github.com/graphprotocol/graph-node/issues/4534