Skip to content

fix(query): use observed progress for indexer feedback - #1224

Merged
tmigone merged 1 commit into
graphprotocol:mainfrom
graphops:chris/qos-observed-progress
Nov 10, 2026
Merged

tmigone merged 1 commit into
graphprotocol:mainfrom
graphops:chris/qos-observed-progress

Conversation

@chriswessels

Copy link
Copy Markdown
Contributor

The explicit-indexer query path feeds the global chain head into that indexer's performance snapshot, including after timeouts or responses without progress metadata. This can incorrectly credit a lagging indexer with progress it never reported.

Use the same response-derived progress extraction in both query paths: graph-indexed on successful responses, the reported latest block on missing-block errors, and no progress for other failures. Tests cover each outcome. Global chain progress still supplies the existing lag calculation.

Validation (on this independent branch):

  • cargo +nightly-2026-06-11 fmt --all -- --check
  • cargo +1.95.0 clippy --all-targets --all-features -- -Dwarnings --force-warn deprecated --force-warn dead-code
  • cargo +1.95.0 test

@chriswessels
chriswessels marked this pull request as ready for review October 29, 2026 13:48
@tmigone
tmigone merged commit 59d2a27 into graphprotocol:main Nov 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants