-
Notifications
You must be signed in to change notification settings - Fork 3
Bidirectional Sync (Part 2) #671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
e5d6db9
do not treat failed syncs as successfull
volovyks abcbd99
broadcast_sync refactor, bug fixes, dummy storage layer sync processing
volovyks 5840d53
remove sync unit tests (tmp)
volovyks 97bb642
naive prune and bidyrectional sync test implementation
volovyks a33b416
refactor helpers, remove old sync test
volovyks aab9394
e2e sync integration test
volovyks 78a46c4
clippy
volovyks 7c5fa6e
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks 432e33b
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks d5bb994
use Redis to manage holders
volovyks e5f1dc3
distinguish participands and holders
volovyks 69db15c
clippy
volovyks c5412ca
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks d93b951
set holders in tets
volovyks 847e369
return Result on fetch_owned
volovyks 46b1d6d
define type for sync response
volovyks 55a5004
do not recycle presignatures, add a guard on active participants
volovyks 37851a5
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks 0af3865
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks 24c373d
do not add reserved to owned during sync
volovyks 52138a8
Revert "do not recycle presignatures, add a guard on active participa…
volovyks 8dc0c3a
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks 1b207be
Merge branch 'develop' into serhii/sync-to-active-fix
volovyks File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,6 +2,7 @@ | |
| .direnv | ||
| .DS_Store | ||
| .idea | ||
| .vscode | ||
|
|
||
| tmp | ||
| *.log | ||
|
|
||
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
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
Oops, something went wrong.
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.
Why do we need to track these separately? Could we not just remove non-holders from the participants list?
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.
We absolutely can. But I wanted to distinguish holders and participants. Mostly for debugging and storage analysis. Also,
holdersare not a part of the serialized object to avoid deserialization/serailzation of each artifact.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.
Okay, it just seemed like a lot of extra complexity with the separate tracking in Redis. But if you see enough value in having it, I have no problem with it.