Skip to content

fix: select newest subgraph version regardless of sync status #1155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
suchapalaver wants to merge 1 commit into from
Closed

fix: select newest subgraph version regardless of sync status #1155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions src/client_query.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -493,15 +493,16 @@ fn build_candidates_list(
let mut candidates_list = Vec::new();
let mut candidates_errors = BTreeMap::default();

// Select the latest subgraph version where indexers are near chain head, or else the latest.
let cutoff = chain_head.saturating_sub(blocks_per_minute * 30);
// Select the latest subgraph version that has any indexers allocated, or else the latest.
// We prefer the newest version to ensure schema compatibility (newer versions may have breaking
// schema changes). Sync status is handled later by indexer selection within the deployment.
let deployment = *subgraph_versions
.iter()
.find(|v| {
indexings
.iter()
.filter_map(|(_, result)| result.as_ref().ok())
.any(|i| (i.id.deployment == **v) && (i.progress.latest_block > cutoff))
.any(|i| i.id.deployment == **v)
})
.unwrap_or(&subgraph_versions[0]);

Expand Down