David Lutterkort

That should have been created as a GiST index.

In this case, since the user asked for an index on `pool`, it should be a BTree index. Had they asked for an index involving `block_range`, we would have to...

It seems that a `MemoryAccessError` comes from deep within wasmtime. Since this seems to be related to loading a lot of entities, I wonder if it just means that the...

Here's my take on this: * In general, we should defer creating BTree attribute indexes on all subgraphs until the subgraph is synced. What we really want is to kick...

The problem here is that even for Python 2, the mandatory utf8 conversion makes things that used to work break: if a config file contains invalid utf8, augeas is perfectly...

@Artanicus we seem to have the problem that we do not have a maintainer for python-augeas anymore, and I do not feel well enough versed in the world of Python...

Maybe I spoke too soon. @thedrow: are you still able to maintain python-augeas? I just noticed that you merged a couple PR's recently. Could you make a new release?

@ptoscano yes, that is really bad. I still don't feel well-equipped to do Python release, and my offer to appoint anybody who raises their hand as maintainer of `python-augeas` still...

> Nice - would this primarily be an update [here](https://thegraph.com/docs/en/developer/assemblyscript-api/#removing-entities-from-the-store), or is this also about documentation within the graph-node repo? No, I think that would be all in the docs...

There's one issue here when it comes to querying data from the `Store`: with prefetching, we sometimes join two tables for a query `parents { children { id } }`...