graphprotocol / graphprotocol/graph-node
lastHealthyBlock is never populated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Do you want to request a feature or report a bug?
Not sure. Seems like a bug to me
What is the current behavior?
For all the subgraphs I have deployed so far, I have never seen lastHealthyBlock be anything other than null. Not sure if that's supposed to happen and if yes then why is the key in the first place?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
- Deploy the gravatar subgraph from the docs
- Run the following query
req := graphql.NewRequest(`
query {
indexingStatuses {
subgraph
synced
health
entityCount
node
fatalError
nonFatalErrors
chains {
network
chainHeadBlock { number }
earliestBlock { number }
latestBlock { number }
lastHealthyBlock { number }
}
}
}
`)
- Notice that
lastHealthyBlockisnull
What is the expected behavior?
That lastHealthyBlock should be populated
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report by deploying the gravatar subgraph and running the provided indexingStatuses query. Trace how the chain status fields, especially lastHealthyBlock, are produced and compare that behavior with the expected populated value. Confirm the result against the same query after the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, backend, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100