MQE: info() derive info series @ reference only when the first argument's vector paths are uniform - #16497
MQE: info() derive info series @ reference only when the first argument's vector paths are uniform#16497zenador wants to merge 3 commits into
Conversation
…nt's vector paths are uniform
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7db6783. Configure here.
| if !w.found { | ||
| return nil, 0, false | ||
| } | ||
| return w.first.timestamp, w.first.offset, w.uniform && !w.referenceFree |
There was a problem hiding this comment.
Non-uniform info lookup still pins range
High Severity
infoSelectTimestampAndOffset now returns the first selector's @ timestamp and offset even when uniform is false, but infoSeriesQueriedTimeRange ignores that flag and still pins the info-series fetch window to those values. Mixed-reference info() queries then advertise a too-narrow queried range, so remote execution can omit evaluation-time info series and drop enrichment.
Reviewed by Cursor Bugbot for commit 7db6783. Configure here.


What this PR does
Restore MQE's feature parity with Prometheus for the info function, matching behaviour for tests defined upstream.
Which issue(s) this PR fixes or relates to
Refining the behaviour implemented in #16220
Implements prometheus/prometheus#19387 from upstream that was vendored in #16496
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]. If changelog entry is not needed, please add thechangelog-not-neededlabel to the PR.about-versioning.mdupdated with experimental features.