Repository navigation
[v3-3-test] Restore LIMIT 1 on single-row XCom lookups - #72702
Merged
Merged
Conversation
Signed-off-by: PoAn Yang <payang@apache.org> (cherry picked from commit 39a5b93)
pierrejeambrun
requested review from
XD-DENG,
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
henry3260,
jason810496,
kaxil,
rawwar and
shubhamraj-git
as code owners
September 8, 2026 12:03
Contributor
|
Hi maintainer, this PR was merged without a milestone set.
|
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 #72554 to
v3-3-test.Cherry-picked from 39a5b93.
Conflict resolution —
test_xcom.py: the incoming hunk added the new test next totest_create_xcom_entry_with_team_name, amulti_teamtest that does not exist onv3-3-test. Kept only this PR's actual change (test_create_xcom_entry_duplicate_check_is_bounded) and dropped the unrelated team-name test. Every other file applied cleanly;capture_orm_selectscame in with the cherry-pick ofdevel-common/.../asserts.py.Backported tests pass (7 passed); ruff clean.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines