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

on GitHub

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

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

What's new

• Fulltext searches can now be combined with where filtering, further narrowing down search results. #4442
• Tweaked how RPC provider limiting rules are interpreted from configurations. In particular, node IDs that don't match any rules of a provider won't have access to said provider instead of having access to it for an unlimited number of subgraphs. Read the docs for more information. #4353
• Introduced WASM host function store.get_in_block, which is a much faster variant of store.get limited to entities created or updated in the current block. #4540
• The entity cache that graph-node keeps around is much more efficient, meaning more cache entries fit in the same amount of memory resulting in a performance increase under a wide range of workloads. #4485
• The subgraph_deploy JSON-RPC method now accepts a history_blocks parameter, which indexers can use to set default amounts of history to keep. #4564
• IPFS requests for polling file data sources are not throttled anymore (also known as concurrency or burst limiting), only rate-limited. #4570
• Exponential requests backoff is now "jittered", smoothing out request spikes. #4476
• RPC provider responses that decrease the chain head block number (non-monotonic) are now ignored, increasing resiliency against inconsistent provider data. #4354
• It's now possible to to have a Firehose-only chain with no RPC provider at all in the configuration. #4508, #4553
• The materialized views in the info schema (table_sizes, subgraph_sizes, and chain_sizes) that provide information about the size of various database objects are now automatically refreshed every 6 hours. #4461
• Adapter selection now takes error rates into account, preferring adapters with lower error rates. #4468
• The substreams protocol has been updated to sf.substreams.rpc.v2.Stream/Blocks. #4556
• Removed support for GRAPH_ETHEREUM_IS_FIREHOSE_PREFERRED, REVERSIBLE_ORDER_BY_OFF, and GRAPH_STORE_CONNECTION_TRY_ALWAYS env. variables. #4375, #4436

Bug fixes

• Fixed a bug that would cause subgraphs to fail with a subgraph writer poisoned by previous error message following certain database errors. #4533
• Fixed a bug that would cause subgraphs to fail with a store error: no connection to the server message when database connection e.g. gets killed. #4435
• The subgraph_reassign JSON-RPC method doesn't fail anymore when multiple deployment copies are found: only the active copy is reassigned, the others are ignored. #4395
• Fixed a bug that would cause on_sync handlers on copied deployments to fail with the message Subgraph instance failed to run: deployment not found [...]. #4396
• Fixed a bug that would cause the copying or grafting of a subgraph while pruning it to incorrectly set earliest_block in the destination deployment. #4502
• Handler timeouts would sometimes be reported as deterministic errors with the error message Subgraph instance failed to run: Failed to call 'asc_type_id' with [...] wasm backtrace [...]; this error is now nondeterministic and recoverable. #4475
• Fixed faulty exponential request backoff behavior after many minutes of failed requests, caused by an overflow. #4421
• json.fromBytes and all BigInt operations now require more gas, protecting against malicious subgraphs. #4594, #4595
• Fixed faulty startBlock selection logic in substreams. #4463

Graphman

• The behavior for graphman prune has changed: running just graphman prune will mark the subgraph for ongoing pruning in addition to performing an initial pruning. To avoid ongoing pruning, use graphman prune --once (docs). #4429
• The env. var. GRAPH_STORE_HISTORY_COPY_THRESHOLD –which serves as a configuration setting for graphman prune– has been renamed to GRAPH_STORE_HISTORY_REBUILD_THRESHOLD. #4505
• You can now list all existing deployments via graphman info --all. #4347
• The command graphman chain call-cache remove now requires --remove-entire-cache as an explicit flag, protecting against accidental destructive command invocations. #4397
• graphman copy create accepts two new flags, --activate and --replace, which make moving of subgraphs across shards much easier. #4374
• The log level for graphman is now set via GRAPHMAN_LOG or command line instead of GRAPH_LOG. #4462
• graphman reassign now emits a warning when it suspects a typo in node IDs. #4377

Metrics and logging

• Subgraph syncing time metric deployment_sync_secs now stops updating once the subgraph has synced. #4489
• New endpoint_request metric to track error rates of different providers. #4490, #4504, #4430
• New metrics chain_head_cache_num_blocks, chain_head_cache_oldest_block, chain_head_cache_latest_block, chain_head_cache_hits, and chain_head_cache_misses to monitor the effectiveness of graph-node's in-memory chain head caches. #4440
• The subgraph error message store error: Failed to remove entities is now more detailed and contains more useful information. #4367
• eth_call logs now include the provider string. #4548
• Tweaks and small changes to log messages when resolving data sources, mappings, and manifests. #4399
• FirehoseBlockStream and FirehoseBlockIngestor now log adapter names. #4411
• The deployment_count metric has been split into deployment_running_count and deployment_count. #4401, #4398

Full Changelog: v0.30.0...aa6677a