graphprotocol / graphprotocol/graph-node
[Bug] Subgraph fails with non-deterministic error duplicate entity in result set
Open
Nobody has claimed this yet.
bug
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
Subgraph fails with an error that is non-deterministic, that should probably be deterministic
Relevant log output
internal constraint violated: duplicate entity FeeRecord[0xf6dc7014f8ae2e55f87d886206d2219e59a0d47f_0xae78736cd615f374d3085123a210448e74fc6393] in result set, block = 17694794
IPFS hash
QmVtNnXse2zWVRsfNGW8SxvipS9SVwC7g9qyQMHvUQbqAP
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
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 investigating the reported “duplicate entity ... in result set” failure for the supplied IPFS hash and block 17694794. Reproduce the non-deterministic subgraph failure and trace the result-set handling that emits this constraint violation. Done means the failure is understood and produces a deterministic, verified outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- backend, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100