Results 82 issues of David Lutterkort

Some of the subgraph runner tests graft directly onto the subgraph head. PR #5135 made that very verboten, which would make those tests fail. For expediency, the PR just disables...

bug
good first issue
Stale

### Description When syncing a subgraph that has limited history, i.e. has `history_blocks` set, we should not keep any history while we are syncing more than `history_blocks` away from the...

enhancement
area/indexing
Stale

### Description Most subgraphs are maintained in git, but once they are deployed, the connection to the source is lost. Subgraph schemas should make it possible to include a URL...

enhancement
needs discussion
needs planning
Stale

The rewritten Python bindings do a bunch of conversion to/from utf8, even though the underlying augeas library does not care whether strings it works on are valid utf8 or not....

The functions in the `store` module (`get`, `set`, `remove`) are a bit confusing right now when subgraph use `Bytes` as their `id`; the host interface still requires that the `id`...

Right now, `indexer-agent` deploys subgraphs under the name `indexer-agent/` into `graph-node`. That makes it impossible to use some `graph-node` features, especially deployment rules to control how deployments are indexed. The...

enhancement
p2

### Which packages are impacted by your issue? @graphprotocol/graph-cli ### Describe the issue I installed the `graph` command using the script from `http://cli.thegraph.com/install.sh` into `~/packages/graph`. Using that without a `package.json`...

bug

Subgraph composition as described in the RFCs so far has two properties that lead to undesirable behavior for users. * import by subgraph name rather than solely by ID *...

With this PR, debug builds (and only debug builds) pay attention to an environment variable `GRAPH_SECTION_MAP` which will make it print a list of the parent/child relations of stopwatch sections....