[airflow-ctl/v0-1-test] Fix airflowctl list operations ignoring the requested offset (#70989) - #71119
Merged
henry3260 merged 1 commit intoAug 5, 2026
Conversation
…equested offset (apache#70989) (cherry picked from commit b541458)
henry3260
marked this pull request as ready for review
August 5, 2026 12:19
henry3260
requested review from
bugraoz93,
dheerajturaga and
potiuk
as code owners
August 5, 2026 12:20
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.
Backport of #70989 to
airflow-ctl/v0-1-test. Cherry-picked cleanly, no conflicts and no adaptation needed —execute_liston this branch is identical to main's pre-fix state.BaseOperations.execute_listaccepts anoffsetbut never sent it on the first request, so paging started at the server default while the loop still resumed atoffset + limit— a non-zero offset both returned the wrong first page and skipped the rows in between.offset=100, limit=2returned rows 0-1, then jumped to row 102.Sending
offset=0is equivalent to omitting it — the API'sQueryOffsetalready defaults to0, so this is compatible.(cherry picked from commit b541458)
Co-authored-by: rjgoyln 151457491+rjgoyln@users.noreply.github.com
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines