mindstyle85

celestia1 + 38 chars

let me add here so i dont clutter, after i removed subgraphs i didnt need anymore, graphman must have done something as ive got new SGDs now in my db....

@azf20 @fordN lmk if you need any more info, tagged you on discord too but here might be easier

> Hi @mindstyle85 I think in this case the `indexer-agent` is redeploying the subgraphs when it is started up, @fordN is there a recommended way to handle this? cc @lutter...

> So to clarify: > > * You stopped the indexer agent > * You ran `graphman --config graphman.toml remove indexer-agent/pkAyYrk93g` then `unused record` and then `unused remove` > *...

hey @azf20 i restarted the indexer stack today (graph node, indexer, agent) , and it seems actually that also causes those same subgraphs to come back again and they were...

now another report from mips participant about graphman issues (same error i see in some of those subgraphs that were added to our indexing without me actually having a rule...

> 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?...

> 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...

Hello! this to me looks like you dont have the appropriate GO version installed by the looks of it, and also make sure you installed all the library packages needed...