Fix read out of order issue with send method in CommsDecoder#64894
Merged
dabla merged 3 commits intoapache:mainfrom Apr 9, 2026
Merged
Fix read out of order issue with send method in CommsDecoder#64894dabla merged 3 commits intoapache:mainfrom
dabla merged 3 commits intoapache:mainfrom
Conversation
Member
|
I think you accidentally removed a bunch of shared libs |
4918d24 to
4f611df
Compare
4f611df to
5fc6ef7
Compare
Contributor
Author
Yes fixed it |
uranusjr
approved these changes
Apr 8, 2026
Contributor
|
Hi maintainer, this PR was merged without a milestone set.
|
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
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.
This PR fixes a possible read out of order issue with send method in CommsDecoder mentioned by @uranusjr due to the fact that the call to _get_response method wasn't inside the thread_lock due to indentation error.
Added unit test to protect us from such regression in the future.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.