Fix a potential deadlock that could occur when encoding for REST. #429
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
|
|
||
| return [self RESTDictionaryWithObjectEncoder:objectEncoder | ||
| operationSetUUIDs:operationSetUUIDs | ||
| state:state |
|
Fix tests, re-indent and ship! |
richardjrossiii
force-pushed
the
richardross.restdictionary.deadlock
branch
from
d2f1ec5 to
6a9dcc2
Compare
richardjrossiii
added a commit
that referenced
this pull request
Oct 16, 2015
….deadlock Fix a potential deadlock that could occur when encoding for REST.
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.
We didn't actually need to hold the lock here, and if we did, another thread could have acquired these locks in another order, causing a deadlock.
Should help to fix #398, #11, and a few others.