Open cryptovestor21 opened 7 months ago
the entityCount for QmTMKqty5yZvZtB3SwzXUG92aZUH1YQw3VjByGw4wgaMhW is not representable as a u64
Maybe the rewind somehow turned the entity count negative. Which is a bug of course.
@leoyvens I think the problem was coming from that rewind to block 1 when the startblock was actually 51880000 That means the graphnode doesn't handle that scenario, and it created all that chaos.
Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.
Bug report
graph-node:v0.34.1
indexer-agent:v0.20.22
Activities that were undertaken before observing this bug:
QmTMKqty5yZvZtB3SwzXUG92aZUH1YQw3VjByGw4wgaMhW
to block 1 usinggraphman
IMPACT: Production Indexer at risk; we cannot manage our online and offline allocations while we have this issue - ideally need a temp fix for the specific symptoms. Would
graphman drop
resolve the issue? Would the graph-node and indexer-agent be able to handle that and start syncing the sub again from scratch given this is a subgraph in flight with live allocations?Relevant log output
IPFS hash
No response
Subgraph name or link to explorer
https://thegraph.com/explorer/subgraphs/2ufoztRpybsgogPVW6j9NTn1JmBWFYPKbP7pAabizADU?view=Overview&chain=arbitrum-one
Some information to help us out
OS information
Linux