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
Unable to sync QoS subgraph QmZmb6z87QmqBLmkMhaqWy7h2GLF1ey8Qj7YSRuqSGMjeH
Tested with firehose / non firehose / clear call cache block cache / rewind / resync from scratch.
Graphnode 0.36.1 and 0.37.0 the same error
Relevant log output
Mar 24 18:56:21.615 ERRO Subgraph instance failed to run: store error: No rows affected. This could be due to an attempt to revert beyond earliest_block + reorg_threshold, runner_index: 325, sgd: 1192, subgraph_id: QmZmb6z87QmqBLmkMhaqWy7h2GLF1ey8Qj7YSRuqSGMjeH, component: SubgraphInstanceManager
IPFS hash
QmZmb6z87QmqBLmkMhaqWy7h2GLF1ey8Qj7YSRuqSGMjeH
Subgraph name or link to explorer
No response
Some information to help us out
Tick this box if this bug is caused by a regression found in the latest release.
Tick this box if this bug is specific to the hosted service.
I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
Linux
The text was updated successfully, but these errors were encountered:
Bug report
Unable to sync QoS subgraph
QmZmb6z87QmqBLmkMhaqWy7h2GLF1ey8Qj7YSRuqSGMjeH
Tested with firehose / non firehose / clear call cache block cache / rewind / resync from scratch.
Graphnode 0.36.1 and 0.37.0 the same error
Relevant log output
IPFS hash
QmZmb6z87QmqBLmkMhaqWy7h2GLF1ey8Qj7YSRuqSGMjeH
Subgraph name or link to explorer
No response
Some information to help us out
OS information
Linux
The text was updated successfully, but these errors were encountered: