Skip to content
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.

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

Backport of Don't exit just because we think there was a possible deadlock into release/1.13.x #21347

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #21342 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

The below text is copied from the body of the original PR.


Fixes #21338


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/vault-17332-do-not-exit-on-potential-deadlock/strictly-sought-stingray branch from 63035d5 to f5fdf02 Compare June 19, 2023 15:09
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/vault-17332-do-not-exit-on-potential-deadlock/strictly-sought-stingray branch from a60e3e6 to 537132f Compare June 19, 2023 15:09
@ncabatoff ncabatoff merged commit a212330 into release/1.13.x Jun 19, 2023
@ncabatoff ncabatoff deleted the backport/vault-17332-do-not-exit-on-potential-deadlock/strictly-sought-stingray branch June 19, 2023 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants