graphprotocol/graph-node v0.29.0-rc.0

on GitHub

v0.29.0-rc.0 is the first release candidate for the upcoming v0.29.0. This release candidate is intended for testnet use only.

$ docker pull graphprotocol/graph-node:v0.29.0-rc.0

Upgrade notes

• This release includes a determinism fix that affect a very small number of subgraphs on the network (we counted 2): if a subgraph manifest had one data source with no contract address, listening to the same events or calls of another data source that has a specified address, then the handlers for those would be called twice. After the fix, this will happen no more, and the handler will be called just once like it should.

  Affected subgraph deployments:

  • Qmccst5mbV5a6vT6VvJMLPKMAA1VRgT6NGbxkLL8eDRsE7
  • Qmd9nZKCH8UZU1pBzk7G8ECJr3jX3a2vAf3vowuTwFvrQg

  Here's an example manifest, taking a look at the data sources of name ERC721 and CryptoKitties, both listen to the Transfer(...) event. Considering a block where there's only one occurence of this event, graph-node would duplicate it and call handleTransfer twice. Now this is fixed and it will be called only once per event/call that happened on chain.

  In the case you're indexing one of the impacted subgraphs, you should first upgrade the graph-node version, then rewind the affected subgraphs to the smallest startBlock of their subgraph manifest. To achieve that the graphman rewind CLI command can be used.

  See #4055 for more information.

• This release fixes another determinism bug that affects a handful of subgraphs. The bug affects all subgraphs which have an apiVersion older than 0.0.5 using call handlers. While call handlers prior to 0.0.5 should be triggered by both failed and successful transactions, in some cases failed transactions would not trigger the handlers. This resulted in nondeterministic behavior. With this version of graph-node, call handlers with an apiVersion older than 0.0.5 will always be triggered by both successful and failed transactions. Behavior for apiVersion 0.0.5 onward is not affected.

  The affected subgraphs are:

  • QmNY7gDNXHECV8SXoEY7hbfg4BX1aDMxTBDiFuG4huaSGA
  • QmYzsCjrVwwXtdsNm3PZVNziLGmb9o513GUzkq5wwhgXDT
  • QmccAwofKfT9t4XKieDqwZre1UUZxuHw5ynB35BHwHAJDT
  • QmYUcrn9S1cuSZQGomLRyn8GbNHmX8viqxMykP8kKpghz6
  • QmecPw1iYuu85rtdYL2J2W9qcr6p8ijich9P5GbEAmmbW5
  • Qmaz1R8vcv9v3gUfksqiS9JUz7K9G8S5By3JYn8kTiiP5K

  In the case you're indexing one of the impacted subgraphs, you should first upgrade the graph-node version, then rewind the affected subgraphs to the smallest startBlock of their subgraph manifest. To achieve that the graphman rewind CLI command can be used.

  See #4149 for more information.

What's new

• Grafted subgraphs can now add their own data sources. #3989, #4027, #4030
• Add support for filtering by nested interfaces. #3677
• Add support for message handlers in Cosmos #3975
• Dynamic data sources for Firehose-backed subgraphs. #4075
• Various logging improvements. #4078, #4084, #4031, #4144, #3990
• Some DB queries now have GCP Cloud Insight -compliant tags that show where the query originated from. #4079
• New configuration variable GRAPH_STATIC_FILTERS_THRESHOLD to conditionally enable static filtering based on the number of dynamic data sources. #4008
• New configuration variable GRAPH_STORE_BATCH_TARGET_DURATION. #4133

Docker image

• The official Docker image now runs on Debian 11 "Bullseye". #4081
• We now ship envsubst with the official Docker image, allowing you to easily run templating logic on your configuration files. #3974

Graphman

We have a new documentation page for graphman, check it out here!

• Subgraph pruning with graphman! #3898, #4125, #4153, #4152, #4156, #4041
• New command graphman drop to hastily delete a subgraph deployment. #4035
• New command graphman chain call-cache for clearing the call cache for a given chain. #4066
• Add --delete-duplicates flag to graphman check-blocks by @tilacog in #3988

Performance

• Restarting a node now takes much less time because postgres_fdw user mappings are only rebuilt upon schema changes. If necessary, you can also use the new commands graphman database migrate and graphman database remap to respectively apply schema migrations or run remappings manually. #4009, #4076
• Database replicas now won't fall behind as much when copying subgraph data. #3966 #3986
• Block handlers optimization with Firehose >= 1.1.0. #3971
• Reduced the amount of data that a non-primary shard has to mirror from the primary shard. #4015
• We now use advisory locks to lock deployments' tables against concurrent writes. #4010

Bug fixes

• Fixed a bug that would cause some failed subgraphs to never restart. #3959
• Fixed a bug that would cause bad POIs for Firehose-backed subgraphs when processing CREATE calls. #4085
• Fixed a bug which would cause failure to redeploy a subgraph immediately after deletion. #4044
• Firehose connections are now load-balanced. #4083
• Determinism fixes. See above. #4055, #4149

Dependency updates

Full Changelog: v0.28.2...v0.29.0-rc.0