graphprotocol / graphprotocol/graph-node
Inconsistent start_block in subgraph_manifest
Open
Nobody has claimed this yet.
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
There are cases where subgraph_manifest.start_block_number is 0 but start_block_hash is null in the database. Unclear why that is, but the rest of the code expects that they are either both null or both have a non-null value.
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
Start by tracing where subgraph_manifest.start_block_number and start_block_hash are written to the database, since the issue does not name a file or test. Determine how the inconsistent row can be created, then verify that the resulting data keeps both fields null or both non-null.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100