fix(cache): data race when refreshing cached messages#7398
Merged
Conversation
Avoid a data race when refreshing cached messages by making all necessary adjustments before insertion into the cache. Signed-off-by: Sebastian Mayr <smayr@barracuda.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7398 +/- ##
==========================================
+ Coverage 55.70% 60.00% +4.30%
==========================================
Files 224 273 +49
Lines 10016 17982 +7966
==========================================
+ Hits 5579 10790 +5211
- Misses 3978 6564 +2586
- Partials 459 628 +169 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yongtang
approved these changes
Jul 3, 2025
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.
1. Why is this pull request needed and what does it do?
This fixes a data race where one goroutine refreshes a cached message while another one serves the same message from the cache. Since the refreshed message is modified after insertion into the cache, this leads to the following data race:
It's pretty trivial to fix by mutating the refreshed message before insertion into the cache.
2. Which issues (if any) are related?
3. Which documentation changes (if any) need to be made?
4. Does this introduce a backward incompatible change or deprecation?