graphprotocol / graphprotocol/graph-node
[Bug] entity type `x` is not on the 'entities' list for data source `y`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
QmayWHkdCwBojegpArxYkfiE51FeREcHkBYJCqvhUpfVP2 SG failed with non-deterministic error
2024-06-17T12:07:06.311498831Z stderr F Jun 17 12:07:06.311 ERRO Subgraph failed with non-deterministic error: error while executing at wasm backtrace: 0: 0x4e95 - <unknown>!src/mappings/ipfs-data/handleUserData: entity type UserWeb3mailPreferencesis not on the 'entities' list for data sourceUserData. Hint: Add UserWeb3mailPreferencesto the 'entities' list, which currently is:UserDescription, Keyword. in handler handleUserData at block #51524917 (), retry_delay_s: 245, attempt: 1, sgd: 634767, subgraph_id: QmayWHkdCwBojegpArxYkfiE51FeREcHkBYJCqvhUpfVP2, component: SubgraphInstanceManager
Relevant log output
No response
IPFS hash
QmayWHkdCwBojegpArxYkfiE51FeREcHkBYJCqvhUpfVP2
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 with the reported IPFS hash and the handleUserData handler, then trace how the UserData data source validates its entities list before creating UserWeb3mailPreferences. The issue does not identify a source file, test, or desired fix; completion would require reproducing the non-deterministic failure and establishing a verified correction or clearer diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100