Payne

@Jannis looks I'm not the only one, but this seems different than what I got this morning. Still related to the indexer-agent db though.

Does it actually fatal errors out or just continues like nothing had happened?

Can confirm this, two different index-nodes, with two different ETH archive nodes set to them. One archive died, everything died.

This is because the cli apparently outputs a colored scheme and pipes can't handle them by default. If you want to escape the characters do this, for example: `graph indexer...

It isn't, I waited for a minute. It doesn't show up.

@nenadjaja a random subgraph from the list. I also think it's related to a picture used in one of the subgraphs. It's either `Opyn` or `Curve`

Oh wait, no, that's a different issue 🤦‍♂️ I'm sorry, too many things to do, too little sleep. So for this issue, if I open any subgraphs in a new...

https://github.com/graphprotocol/mission-control-indexer/issues/136 This is the one related to curve and opyn images.

Just checked and this is still present. And also for the profile data as well. Basically everything that can be updated through a transaction, will have this issue.

Very likely to be related to: https://github.com/graphprotocol/mission-control-indexer/issues/94