graphprotocol / graphprotocol/graph-node
[Bug] INDEXING ERROR: Error: failed to process trigger
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
Error: Processing trigger failed for block #32611263 (0xf7e5…15bf), transaction efe50598548e81c9602286a2b6c300c5da042502800e25632decfd903bce566f. An error occurred during execution at wasm backtrace position 0: 0x512f - !src/mappings/factory/handlePoolCreated. The entity Pool[0xae81fac689a1b4b1e06e7ef4a2ab4cd8ac0a087d] is missing a value for the non-nullable field tick.
Relevant log output
Error: failed to process trigger: block #32611263 (0xf7e5…15bf), transaction efe50598548e81c9602286a2b6c300c5da042502800e25632decfd903bce566f: error while executing at wasm backtrace: 0: 0x512f - <unknown>!src/mappings/factory/handlePoolCreated: Entity Pool[0xae81fac689a1b4b1e06e7ef4a2ab4cd8ac0a087d]: missing value for non-nullable field `tick`: Entity Pool[0xae81fac689a1b4b1e06e7ef4a2ab4cd8ac0a087d]: missing value for non-nullable field `tick`
IPFS hash
No response
Subgraph name or link to explorer
https://thegraph.com/studio/subgraph/quickswap_origin/
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
macOS
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 reproducing the failure at block 32611263 for transaction efe50598548e81c9602286a2b6c300c5da042502800e25632decfd903bce566f, then inspect the src/mappings/factory/handlePoolCreated entry point. Done means determining why Pool.tick is unset and resolving the non-nullable-field error for the reported subgraph.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100