Backport of Fix potential race on core.activityLog into release/1.13.x #22572
Conversation
This file contains 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
hc-github-team-secure-vault-core
force-pushed
the
backport/use-locked-activitylog-pointer/frankly-better-gull
branch
from
b9e761c to
13ce45d
Compare
hc-github-team-secure-vault-core
force-pushed
the
backport/use-locked-activitylog-pointer/frankly-better-gull
branch
from
8c00fab to
e18b721
Compare
github-actions
bot
added
the
hashicorp-contributed-pr
mpalmi
approved these changes
Aug 25, 2023
mpalmi
deleted the
backport/use-locked-activitylog-pointer/frankly-better-gull
branch
|
Build Results: |
|
CI Results: |
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
This PR is auto-generated from #22571 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.
This PR addresses a potential race introduced in #18809. We want to make sure the activitylog doesn't change from underneath us, so we should make sure to use the activitylog pointer we've copied in a read lock, rather than
c.activityLog.Overview of commits