graphprotocol / graphprotocol/indexer
Indexer agent 0.21.4 crash looping due to syncing specific subgraph - [GraphQL] internal constraint violated: the entityCount for <Qm> is not representable as a u64
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Logs here :
{"level":50,"time":1728384890252,"pid":1,"hostname":"954f476b32b8","name":"IndexerAgent","component":"GraphNode","err":{"type":"IndexerError","message":"Failed to query indexing status API","stack":"IndexerError: Failed to query indexing status API\n at indexerError (/opt/indexer/packages/indexer-common/dist/errors.js:179:12)\n at GraphNode.subgraphDeploymentsAssignments (/opt/indexer/packages/indexer-common/dist/graph-node.js:175:51)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async GraphNode.subgraphDeployments (/opt/indexer/packages/indexer-common/dist/graph-node.js:106:17)\n at async retries (/opt/indexer/packages/indexer-common/dist/graph-node.js:69:37)\n at async RetryOperation._fn (/opt/indexer/node_modules/p-retry/index.js:50:12)","code":"IE018","explanation":"https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie018","cause":{"type":"CombinedError","message":"[GraphQL] internal constraint violated: the entityCount for QmP5v5YNiVdm4jKArgkpAg52zSGcpdhCGtM7zEuwuS3vLD is not representable as a u64","name":"CombinedError","graphQLErrors":[{"message":"internal constraint violated: the entityCount for QmP5v5YNiVdm4jKArgkpAg52zSGcpdhCGtM7zEuwuS3vLD is not representable as a u64"}],"response":{"size":0,"timeout":0}}},"msg":"Failed to query indexing status API"}
Subgraph affected :
QmP5v5YNiVdm4jKArgkpAg52zSGcpdhCGtM7zEuwuS3vLD (DODOEX TOKEN POLYGON Upgraded)
Reference : Discord (This is pretty old but the same error, maybe there's a correlation)
Graph-node version : 0.35.1
Indexer agent : 0.21.4
Indexer service : 0.21.4
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 with packages/indexer-common/dist/graph-node.js, especially GraphNode.subgraphDeploymentsAssignments, and the IE018 handling described in packages/indexer-common/dist/errors.js. Investigate the indexing status response for the affected subgraph and the GraphQL entityCount constraint; done means the agent no longer crash loops when this condition occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100