Fix: Improve thread safety in issue acknowledgement#234
Merged
vicsanity623 merged 2 commits intomainfrom Mar 18, 2026
Merged
Conversation
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
2 participants
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.
Summary of Changes
This pull request improves the thread safety of the issue acknowledgement process in the dashboard server. The lock is now held for the entire read-modify-write operation, preventing potential data corruption or inconsistencies.
Technical Impact
The changes ensure that the issue statuses are updated atomically, reducing the risk of concurrent modifications and improving the overall reliability of the system. The updated code maintains the same functionality as before but with enhanced thread safety measures.