Repository navigation
Conversation
zzylol
force-pushed
the
feat/handoff-label-coverage
branch
from
September 30, 2026 18:27
a1c94d6 to
c32b85a
Compare
zzylol
force-pushed
the
feat/handoff-range-bounds
branch
from
September 30, 2026 18:27
2096e3a to
9ed2e69
Compare
RunContext query bounds let reusable programs execute @ start() and @ end() on selectors and subquery grids without embedding deployment timestamps. Missing bounds fail before inputs are consumed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zzylol
force-pushed
the
feat/handoff-label-coverage
branch
from
September 30, 2026 20:25
c32b85a to
9ab8b2c
Compare
zzylol
force-pushed
the
feat/handoff-range-bounds
branch
from
September 30, 2026 20:25
9ed2e69 to
7edd134
Compare
Contributor
Author
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
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.
Stacked on #501.
Why
Planner could not compile PromQL
@ start()and@ end()because the outer range query bounds belong to the deployment.What
Retain those anchors in compiled series windows and subquery grids. Add
RunContext::with_query_rangeso deployments bind outer query bounds per run. Missing or invalid bounds fail before input consumption.Before this PR
a @ start()andmax_over_time(a[2m:1m] @ end())failed native compilation.After this PR
The same reusable plans execute against explicitly supplied outer bounds, including offsets and inner selector anchors, while result timestamps remain the current query evaluation time. Instant-query callers supply equal start/end bounds.
Validation
Compile regression failed before implementation. All 40 fallback tests pass after; runtime tests cover both anchors, offsets, range functions, subquery grids, inner anchors, output timestamps, and missing-bound rejection. Formatting and workspace all-target clippy pass; full workspace test sweep plus corrected old-rejection target pass.
🤖 Generated with Claude Code