graphprotocol / graphprotocol/graph-node

lastHealthyBlock is never populated

Open
#4,414 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Stale
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.

  1. Deploy the gravatar subgraph from the docs
  2. 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 }
				}
			}
		}
	`)
  1. Notice that lastHealthyBlock is null

What is the expected behavior?
That lastHealthyBlock should be populated

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.