Repository navigation
feat: let the sync operator set an outage traffic allowance #71
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
Open
timwu20
wants to merge
11
commits into
main
Choose a base branch
from
feat/outage-traffic-allowance
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+983
−60
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ba3d0ff
feat: let the sync operator set an outage traffic allowance [ci]
timwu20 308b1c4
fix: tighten the outage traffic allowance after review
timwu20 bbea08c
fix: fall back to the plain top-up when the wallet does not cover the…
timwu20 89b0dfc
test: have alice transact during the outage, and reuse the splitwell …
timwu20 9feb7ff
fix: address the re-review of the outage traffic allowance [ci]
timwu20 6a6bb91
fix: reconcile dedicated-synchronizer traffic by polling, and drop th…
timwu20 c78ddd0
fix: address the review of the polling trigger and the shortfall top-…
timwu20 6f76e28
refactor: leave the outage settlement top-up to a follow-up PR [ci]
timwu20 17f563e
fix: address the first review of the split outage allowance [ci]
timwu20 0eb7cc8
docs: describe when operators' traffic limits can flip, and test the …
timwu20 1e7b8cd
refactor: handle dedicated traffic grants as on the global synchroniz…
timwu20 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
312 changes: 300 additions & 12 deletions
312
...rg/lfdecentralizedtrust/splice/integration/tests/SyncOperatorTrafficIntegrationTest.scala
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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.
shouldn't this be shared between gsync and dsync?
Uh oh!
There was an error while loading. Please reload this page.
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.
Do you mean the rule for which members get skipped? The SV trigger already skips the members it grants unlimited traffic, its SV nodes, through
trafficLimitOffset. The equivalent here would be the synchronizer's mediators, whichMediatorUnlimitedTrafficTriggergrants unlimited traffic. I can share one hook for "members granted unlimited traffic" between the two triggers and skip those, instead of filtering by member type. Should I do that in this PR, or did you have something broader in mind, like sharing the reconcile step itself?