graphprotocol / graphprotocol/indexer
Indexer-agent: Improve error messages when subgraph deployment query fails
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
This log line is not very helpful for debugging.
component: "NetworkMonitor"
retriesRemaining: 9
error: {}```
Why is the error an empty object?
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 at the Indexer-agent's NetworkMonitor code that emits the “Failed to query subgraph deployments” log line. Trace the failed deployment query and inspect how its error is serialized, then run the relevant agent checks if available. Done means the log exposes a useful underlying error instead of an empty 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