Ford
It's been AWHILE now. Any word on updating the vulnerable dependency?
Hey @dvdplm, sorry just seeing this. I'll take a look tomorrow!
I'm seeing similar behavior. After rewinding a subgraph it was able to sync back to chain head successfully and continue syncing healthily. However, the failed status has not cleared. Here...
Hey @mindstyle85, in the situation where you remove a subgraph, then find that it is redeployed I have a few questions: - Is the indexer-agent redeploying it? You can check...
Ok, so the behavior you observed is that a subgraph deployment began syncing even though there is no corresponding rule for that subgraph? Is there also an allocation being created?...
Ya figured as much, makes perfect sense as it would be very expensive to check the logs in every block in the range. It could be very nice though as...
In my experience missed logs are one of the most common issues with RPC providers running at scale, so I'm trying to find solutions to verify those results out of...
Both `indexer-service` and `indexer-agent`?
Ok, that's what I'm seeing too. I'm able to reproduce on `indexer-service`; I'm getting an odd `segfault` error that doesn't produce any logs. I'm bisecting back through git commit history...
I wonder if we should include a migration script with this PR to reassign (to existing node id) and pause any subgraph deployments that are currently assigned to node_id =...