[indexer] Explicitly disable unfinalized blocks when not set#730
Merged
[indexer] Explicitly disable unfinalized blocks when not set#730
Conversation
…esses and update Docker command template with timeout option
…e Arbitrum Sepolia references with Base Sepolia
…package.json and docker-compose files
…d/explicitly-disable-unfinalized
seunlanlege
approved these changes
Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Subql assumes unfinalized block indexing is true if the node is not explicitly started with
--unfinalized-blocks=false. This PR fixes our docker compose files to set this when we do not desire unfinalized blocks.