Repository navigation
fix(python): replace schedules across pipeline updates - #201
Merged
Merged
Conversation
tchaton
marked this pull request as ready for review
October 14, 2026 12:09
tchaton
requested review from
ethanwharris,
justusschock,
k223kim,
rusenask and
tejapulagam
as code owners
October 14, 2026 12:09
iandk
approved these changes
Oct 14, 2026
tchaton
enabled auto-merge (squash)
October 14, 2026 13:15
justusschock
approved these changes
Oct 14, 2026
rusenask
approved these changes
Oct 14, 2026
tchaton
disabled auto-merge
October 14, 2026 13:54
bmaydan
pushed a commit
that referenced
this pull request
Oct 14, 2026
1 task
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
4 participants
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.
Repeated
Pipeline.run()updates can leave old schedules active because cleanup uses the immediately preceding run ID instead of the pipeline's original schedule group.Resolve the parent chain, remove schedules associated with earlier runs, and attach replacement schedules to the original pipeline. This also handles older schedules attached directly to an intermediate run and preserves unrelated schedules. Document that omitted or empty schedules remove existing schedules.
Validation: 47 focused pipeline API/core tests passed after rebasing onto main; Ruff and
git diff --checkpassed. Regression coverage includes repeated updates, legacy schedule grouping, empty schedules, and pipeline creation failures. Schedule replacement remains a sequence of API calls, not an atomic operation.— Codex, via /create-pr; text not reviewed