This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fixing marking blocks as bad & SyncMessage bugs + small client refactoring. #503
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
990c5c8
Refactoring client and fixing mark_as_bad & SyncMessage bugs
4084acd
Removing dangling comment
d3fe3f2
Client refactoring [WIP]
d914a27
Removing lifetimes from Blocks
0864728
Fixing mark_as_bad implementation
a0f930f
Merge branch 'master' into client_bugs
fd63fa6
Update block.rs
f55d111
Merge branch 'master' into client_bugs
f118e30
Renaming variables to more descriptive
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
Submodule tests
updated
19 files
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this introduce a possible deadlock? if so, is it clear and well-documented that this is the canonical order in which to lock these resources?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before verification lock was obtained a the beginning, but processing write-lock was obtained inside the loop - I've just extracted that above the loop, maintaining the order.
Had a quick look on all functions and it's not clear in which order to lock verification and processing - I will look into this.