graphprotocol / graphprotocol/indexer
Improve error logging on failed network subgraph queries
Open
Nobody has claimed this yet.
indexer-common
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
We need to ensure the error cause is propagated to the indexer.
Example of error without cause:
{"level":40,"time":1651775440589,"pid":1,"hostname":"7275fbff4642","name":"IndexerAgent","component":"Network","indexer":"0xB4B4570df6F7FE320f10Fdfb702dba7e35244550","operator":"0xOPs","retriesRemaining":9,"error":{},"msg":"Failed to query subgraph deployments"}
Contributor guide
No contributing guide indexed for this repository
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 the IndexerAgent Network path that emits "Failed to query subgraph deployments" and inspect how the failed query error is logged. Reproduce a failed subgraph deployment query and verify that its cause is propagated and serialized instead of producing an empty error object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100