With release v0.16.0 of graph-ts, graph-cli, and graph-node changes have been made that could lead to new errors if you redeploy the subgraph:
Subgraph entities are validated more strictly than in the past, particularly with respect to non-null type entity fields.
This PR makes a few necessary changes to work with the stricter validation and also uses the new startBlock feature to reduce the work each data source has to do while indexing.
This is a draft release because I rebased on top of recent updates that cause an error:
Subgraph instance failed to run: Error while processing block stream for a subgraph: tried to set entity of type `TokenPurchaseEvent` with ID "1" but an entity of type `AddLiquidityEvent`, which has an interface in common with `TokenPurchaseEvent`, exists with the same ID, code: SubgraphSyncingFailure, id:
Note: v0.16.0 of graph-node will be rolled out to the hosted-service on November 5th, 2019.
With release v0.16.0 of graph-ts, graph-cli, and graph-node changes have been made that could lead to new errors if you redeploy the subgraph:
Subgraph entities are validated more strictly than in the past, particularly with respect to non-null type entity fields. This PR makes a few necessary changes to work with the stricter validation and also uses the new startBlock feature to reduce the work each data source has to do while indexing.
This is a draft release because I rebased on top of recent updates that cause an error:
Note: v0.16.0 of graph-node will be rolled out to the hosted-service on November 5th, 2019.