You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The indexer-agent ignores rules for some subgraphs, specifically when several subgraphs have identical createdAt timestamps. The current subgraphDeployments() logic fetches 10 subgraphs at a time, using the condition createdAt_gt the last result of the previous batch. Every time more than one subgraph has the same createdAt, there is a chance that the group spans across two pages, and in such cases, some subgraphs may be missed. This is especially problematic when there are more than 10 subgraphs with the same timestamp (e.g., on the Arbitrum One network, where 14 deployments have the timestamp 1717782397).
The solution would be to stop using createdAt for pagination and use skip: fetched instead.
At the time of this report, the indexer-agent sees 5,373 subgraphs, but by changing the logic, I'm getting 6,461 subgraphs, allowing me to create allocations for subgraphs that were previously invisible to the agent.
The content you are editing has changed. Please copy your edits and refresh the page.
The indexer-agent ignores rules for some subgraphs, specifically when several subgraphs have identical createdAt timestamps. The current subgraphDeployments() logic fetches 10 subgraphs at a time, using the condition createdAt_gt the last result of the previous batch. Every time more than one subgraph has the same createdAt, there is a chance that the group spans across two pages, and in such cases, some subgraphs may be missed. This is especially problematic when there are more than 10 subgraphs with the same timestamp (e.g., on the Arbitrum One network, where 14 deployments have the timestamp 1717782397).
The solution would be to stop using createdAt for pagination and use skip: fetched instead.
At the time of this report, the indexer-agent sees 5,373 subgraphs, but by changing the logic, I'm getting 6,461 subgraphs, allowing me to create allocations for subgraphs that were previously invisible to the agent.
Tasks
The text was updated successfully, but these errors were encountered: