David Lutterkort

The error `store error: relation "sgd2.router" does not exist` comes from an internal cache where we [cache details](https://github.com/graphprotocol/graph-node/blob/master/store/postgres/src/relational.rs#L1342-L1452) about a subgraph's layout in the database for up to 5 minutes...

Just in case it wasn't clear from my previous comment: the database is totally fine despite this error.

I just opened PR #4044 that will make sure the error `store error: relation "sgd2.router" does not exist` does not appear anymore when rapidly deleting and redeploying a subgraph.

I just ran this query against the hosted service (by using the URL `https://api.thegraph.com/subgraphs/id/Qme5mFGEqDg1KJ8PeaWj7vPDccTpSeHGPz9Zr8T4zAqJ3F`) The first time, the query took 20s, subsequent executions, even with small changes in the timestamp,...

Quick note on rebasing: please always rebase with `git rebase master ` not by merging master into the branch since that leads to funky looking merge commits.

You can achieve that by manipulating what's in `/augeas/load` which is what ultimately governs what gets loaded (the filters/transforms from the lenses are used to prepopulate that) After loading your...

Closing this for now - feel free to reopen if it should turn out this doesn't work for you.

Unfortunately, no there is no way to save what you have set up in `/augeas/load`. The best option I can think of is to script the setup by using one...

I have to think about that a bit how that should work internally as issuing a `load` then will need to interleave loading files with matching and adding to the...

Not a fix, just a quick diagnosis: the problem is that filter_siblings in jmt.c calls itself recursively, and we simply run out of stack space with a large file.