|
2 | 2 |
|
3 | 3 | ## Unreleased |
4 | 4 |
|
5 | | -#### Upgrade notes |
| 5 | +## v0.29.0 |
| 6 | + |
| 7 | +### Upgrade notes |
| 8 | + |
| 9 | +- 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. |
| 10 | + |
| 11 | + Affected subgraph deployments: |
| 12 | + |
| 13 | + - `Qmccst5mbV5a6vT6VvJMLPKMAA1VRgT6NGbxkLL8eDRsE7` |
| 14 | + - `Qmd9nZKCH8UZU1pBzk7G8ECJr3jX3a2vAf3vowuTwFvrQg` |
| 15 | + |
| 16 | + Here's an example [manifest](https://ipfs.io/ipfs/Qmd9nZKCH8UZU1pBzk7G8ECJr3jX3a2vAf3vowuTwFvrQg), 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. |
| 17 | + |
| 18 | + 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. |
| 19 | + |
| 20 | + See [#4055](https://github.com/graphprotocol/graph-node/pull/4055) for more information. |
| 21 | + |
| 22 | +* 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. |
| 23 | + |
| 24 | + The affected subgraphs are: |
| 25 | + |
| 26 | + - `QmNY7gDNXHECV8SXoEY7hbfg4BX1aDMxTBDiFuG4huaSGA` |
| 27 | + - `QmYzsCjrVwwXtdsNm3PZVNziLGmb9o513GUzkq5wwhgXDT` |
| 28 | + - `QmccAwofKfT9t4XKieDqwZre1UUZxuHw5ynB35BHwHAJDT` |
| 29 | + - `QmYUcrn9S1cuSZQGomLRyn8GbNHmX8viqxMykP8kKpghz6` |
| 30 | + - `QmecPw1iYuu85rtdYL2J2W9qcr6p8ijich9P5GbEAmmbW5` |
| 31 | + - `Qmaz1R8vcv9v3gUfksqiS9JUz7K9G8S5By3JYn8kTiiP5K` |
| 32 | + |
| 33 | + 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. |
| 34 | + |
| 35 | + See [#4149](https://github.com/graphprotocol/graph-node/pull/4149) for more information. |
| 36 | + |
| 37 | +### What's new |
| 38 | + |
| 39 | +* Grafted subgraphs can now add their own data sources. [#3989](https://github.com/graphprotocol/graph-node/pull/3989), [#4027](https://github.com/graphprotocol/graph-node/pull/4027), [#4030](https://github.com/graphprotocol/graph-node/pull/4030) |
| 40 | +* Add support for filtering by nested interfaces. [#3677](https://github.com/graphprotocol/graph-node/pull/3677) |
| 41 | +* Add support for message handlers in Cosmos [#3975](https://github.com/graphprotocol/graph-node/pull/3975) |
| 42 | +* Dynamic data sources for Firehose-backed subgraphs. [#4075](https://github.com/graphprotocol/graph-node/pull/4075) |
| 43 | +* Various logging improvements. [#4078](https://github.com/graphprotocol/graph-node/pull/4078), [#4084](https://github.com/graphprotocol/graph-node/pull/4084), [#4031](https://github.com/graphprotocol/graph-node/pull/4031), [#4144](https://github.com/graphprotocol/graph-node/pull/4144), [#3990](https://github.com/graphprotocol/graph-node/pull/3990) |
| 44 | +* Some DB queries now have GCP Cloud Insight -compliant tags that show where the query originated from. [#4079](https://github.com/graphprotocol/graph-node/pull/4079) |
| 45 | +* New configuration variable `GRAPH_STATIC_FILTERS_THRESHOLD` to conditionally enable static filtering based on the number of dynamic data sources. [#4008](https://github.com/graphprotocol/graph-node/pull/4008) |
| 46 | +* New configuration variable `GRAPH_STORE_BATCH_TARGET_DURATION`. [#4133](https://github.com/graphprotocol/graph-node/pull/4133) |
| 47 | + |
| 48 | +#### Docker image |
| 49 | +* The official Docker image now runs on Debian 11 "Bullseye". [#4081](https://github.com/graphprotocol/graph-node/pull/4081) |
| 50 | +* We now ship [`envsubst`](https://github.com/a8m/envsubst) with the official Docker image, allowing you to easily run templating logic on your configuration files. [#3974](https://github.com/graphprotocol/graph-node/pull/3974) |
| 51 | + |
| 52 | +#### Graphman |
| 53 | + |
| 54 | +We have a new documentation page for `graphman`, check it out [here](https://github.com/graphprotocol/graph-node/blob/2da697b1af17b1c947679d1b1a124628146545a6/docs/graphman.md)! |
| 55 | + |
| 56 | +* Subgraph pruning with `graphman`! [#3898](https://github.com/graphprotocol/graph-node/pull/3898), [#4125](https://github.com/graphprotocol/graph-node/pull/4125), [#4153](https://github.com/graphprotocol/graph-node/pull/4153), [#4152](https://github.com/graphprotocol/graph-node/pull/4152), [#4156](https://github.com/graphprotocol/graph-node/pull/4156), [#4041](https://github.com/graphprotocol/graph-node/pull/4041) |
| 57 | +* New command `graphman drop` to hastily delete a subgraph deployment. [#4035](https://github.com/graphprotocol/graph-node/pull/4035) |
| 58 | +* New command `graphman chain call-cache` for clearing the call cache for a given chain. [#4066](https://github.com/graphprotocol/graph-node/pull/4066) |
| 59 | +* Add `--delete-duplicates` flag to `graphman check-blocks` by @tilacog in https://github.com/graphprotocol/graph-node/pull/3988 |
| 60 | + |
| 61 | +#### Performance |
| 62 | +* 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](https://github.com/graphprotocol/graph-node/pull/4009), [#4076](https://github.com/graphprotocol/graph-node/pull/4076) |
| 63 | +* Database replicas now won't fall behind as much when copying subgraph data. [#3966](https://github.com/graphprotocol/graph-node/pull/3966) [#3986](https://github.com/graphprotocol/graph-node/pull/3986) |
| 64 | +* Block handlers optimization with Firehose >= 1.1.0. [#3971](https://github.com/graphprotocol/graph-node/pull/3971) |
| 65 | +* Reduced the amount of data that a non-primary shard has to mirror from the primary shard. [#4015](https://github.com/graphprotocol/graph-node/pull/4015) |
| 66 | +* We now use advisory locks to lock deployments' tables against concurrent writes. [#4010](https://github.com/graphprotocol/graph-node/pull/4010) |
| 67 | + |
| 68 | +#### Bug fixes |
| 69 | +* Fixed a bug that would cause some failed subgraphs to never restart. [#3959](https://github.com/graphprotocol/graph-node/pull/3959) |
| 70 | +* Fixed a bug that would cause bad POIs for Firehose-backed subgraphs when processing `CREATE` calls. [#4085](https://github.com/graphprotocol/graph-node/pull/4085) |
| 71 | +* Fixed a bug which would cause failure to redeploy a subgraph immediately after deletion. [#4044](https://github.com/graphprotocol/graph-node/pull/4044) |
| 72 | +* Firehose connections are now load-balanced. [#4083](https://github.com/graphprotocol/graph-node/pull/4083) |
| 73 | +* Determinism fixes. **See above.** [#4055](https://github.com/graphprotocol/graph-node/pull/4055), [#4149](https://github.com/graphprotocol/graph-node/pull/4149) |
| 74 | + |
| 75 | +#### Dependency updates |
| 76 | + |
| 77 | +| Dependency | updated to | |
| 78 | +| ------------------- | ---------- | |
| 79 | +| `anyhow` | 1.0.66 | |
| 80 | +| `base64` | 0.13.1 | |
| 81 | +| `clap` | 3.2.23 | |
| 82 | +| `env_logger` | 0.9.1 | |
| 83 | +| `iana-time-zone` | 0.1.47 | |
| 84 | +| `itertools` | 0.10.5 | |
| 85 | +| `jsonrpsee` | 0.15.1 | |
| 86 | +| `num_cpus` | 1.14.0 | |
| 87 | +| `openssl` | 0.10.42 | |
| 88 | +| `pretty_assertions` | 1.3.0 | |
| 89 | +| `proc-macro2` | 1.0.47 | |
| 90 | +| `prometheus` | 0.13.3 | |
| 91 | +| `protobuf-parse` | 3.2.0 | |
| 92 | +| `semver` | 1.0.14 | |
| 93 | +| `serde_plain` | 1.0.1 | |
| 94 | +| `sha2` | 0.10.6 | |
| 95 | +| `structopt` | removed | |
| 96 | +| `tokio-stream` | 0.1.11 | |
| 97 | +| `tokio-tungstenite` | 0.17.2 | |
| 98 | +| `tower-test` | `d27ba65` | |
| 99 | +| `url` | 2.3.1 | |
| 100 | + |
| 101 | +<!-- |
| 102 | +* build(deps): bump anyhow from 1.0.65 to 1.0.66 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4107 |
| 103 | +* build(deps): bump base64 from 0.13.0 to 0.13.1 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4104 |
| 104 | +* build(deps): bump clap from 3.2.22 to 3.2.23 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4106 |
| 105 | +* build(deps): bump env_logger from 0.9.0 to 0.9.1 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3955 |
| 106 | +* build(deps): bump iana-time-zone from 0.1.44 to 0.1.47 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3892 |
| 107 | +* build(deps): bump itertools from 0.10.3 to 0.10.5 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3996 |
| 108 | +* build(deps): bump num_cpus from 1.13.1 to 1.14.0 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4141 |
| 109 | +* build(deps): bump openssl from 0.10.41 to 0.10.42 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4022 |
| 110 | +* build(deps): bump pretty_assertions from 1.2.1 to 1.3.0 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3906 |
| 111 | +* build(deps): bump proc-macro2 from 1.0.46 to 1.0.47 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4068 |
| 112 | +* build(deps): bump prometheus from 0.13.2 to 0.13.3 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4105 |
| 113 | +* build(deps): bump protobuf-parse from 3.1.0 to 3.2.0 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3997 |
| 114 | +* build(deps): bump semver from 1.0.12 to 1.0.14 by @dependabot in https://github.com/graphprotocol/graph-node/pull/3994 |
| 115 | +* build(deps): bump serde_plain from 1.0.0 to 1.0.1 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4103 |
| 116 | +* graph,node: Migrate from structopt to clap v3 by @tilacog in https://github.com/graphprotocol/graph-node/pull/3982 |
| 117 | +* build(deps): bump tokio-tungstenite from 0.14.0 to 0.17.2 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4064 |
| 118 | +* build(deps): bump tokio-stream from 0.1.10 to 0.1.11 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4057 |
| 119 | +* build(deps): bump tower-test from `c049ded` to `d27ba65` by @dependabot in https://github.com/graphprotocol/graph-node/pull/4102 |
| 120 | +* build(deps): bump url from 2.3.0 to 2.3.1 by @dependabot in https://github.com/graphprotocol/graph-node/pull/4023 |
| 121 | +* Replace unmaintained `jsonrpc` crate with `jsonrpsee` by @neysofu in https://github.com/graphprotocol/graph-node/pull/3949 |
| 122 | +--> |
6 | 123 |
|
7 | | -- This release includes a **determinism fix** that should affect very few subgraphs on the network (currently only two). There was an issue that 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, the handlers for those would be called twice. With the fix, this will happen no more, the handler will be called just once like it should. |
8 | | - - The two affected deployments are: `Qmccst5mbV5a6vT6VvJMLPKMAA1VRgT6NGbxkLL8eDRsE7` and `Qmd9nZKCH8UZU1pBzk7G8ECJr3jX3a2vAf3vowuTwFvrQg`; |
9 | | - - Here's an example [manifest](https://ipfs.io/ipfs/Qmd9nZKCH8UZU1pBzk7G8ECJr3jX3a2vAf3vowuTwFvrQg), 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. |
10 | | - - In the case you're indexing one of those, 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. |
| 124 | +**Full Changelog**: https://github.com/graphprotocol/graph-node/compare/v0.28.2...v0.29.0-rc.0 |
11 | 125 |
|
12 | 126 | ## v0.28.2 |
13 | 127 |
|
|
0 commit comments