Replace RwLock::try_read
with RwLock::read
in SyncStorage
#2463
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.
Replace
RwLock::try_read
withRwLock::read
inSyncStorage
This pull request replaces the use of
RwLock::try_read
withRwLock::read
in theSyncStorage
.This change prioritizes potential deadlocks over panics. Unwrapping a failed
try_read
can lead to unexpected behavior and difficult-to-debug issues. UsingRwLock::read
ensures that the code will always block until a read lock is acquired, preventing potential panics but introducing the possibility of deadlocks.This change is consistent with the current use of RwLock::write for write operations.
Changes:
RwLock::try_read
withRwLock::read
inSyncStorage
.Rationale:
RwLock::write
for write operations.Potential Issues: