Skip to content

Send failures could lock transport into single concurrency mode #5016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
danielmarbach merged 1 commit into from
Jun 13, 2025
Merged

Send failures could lock transport into single concurrency mode #5016

danielmarbach merged 1 commit into from
Jun 13, 2025

Conversation

@WilliamBZA
Copy link
Member

@WilliamBZA WilliamBZA commented Jun 12, 2025 •
edited
Loading

@WilliamBZA WilliamBZA requested review from afprtclr and hsvotwa June 12, 2025 10:41
@WilliamBZA WilliamBZA added this to the 6.6.4 milestone Jun 12, 2025
@WilliamBZA WilliamBZA added the Bug label Jun 12, 2025
@danielmarbach danielmarbach merged commit 131f129 into release-6.6 Jun 13, 2025
32 checks passed
@danielmarbach danielmarbach deleted the cherry-pick-5014-to-6.6 branch June 13, 2025 07:58
@danielmarbach danielmarbach changed the title Fix race condition in RepeatedFailuresOverTimeCircuitBreaker Send failures could lock transport into single concurrency mode Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@danielmarbach danielmarbach danielmarbach approved these changes

@afprtclr afprtclr afprtclr approved these changes

+1 more reviewer

@hsvotwa hsvotwa hsvotwa approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Bug

Projects

None yet

Milestone

6.6.4

Development

Successfully merging this pull request may close these issues.

5 participants

@WilliamBZA @danielmarbach @hsvotwa @afprtclr