graphprotocol / graphprotocol/graph-node
File data source data loss on non-deterministic error retry
Open
Nobody has claimed this yet.
bug
offchain
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
If a data source is created in block N, but found only in block N + 1, and there is a non-deterministic error in block N + 1 after it is found (e.g. when writing to the store), the data will be lost if we don't somehow re-insert it into the offchain monitor.
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 how file data sources move from block N into the offchain monitor and how retries handle non-deterministic errors in block N + 1. Reproduce the case where the data source is found before a store write fails, then verify that retry processing preserves it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100