-
Notifications
You must be signed in to change notification settings - Fork 80
fix(webrtc): warp sync slow initialization and webrtc handshake bug #3256
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
gab8i
wants to merge
7
commits into
main
Choose a base branch
from
gab_webrtc
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.
Open
Changes from 3 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
344d501
Fix WebRTC notification handshake deadlock in multi-stream task loop
haikoschol 1ab3ecc
Fix warp sync initialization
timwu20 1ad0581
Merge branch 'main' into gab_webrtc
lrubasze 4004824
refactor(warp_sync): rename to optimistic_finalized_block_height
gab8i 118c250
fix(webrtc): register write_listener before async block
gab8i 9c02618
chore: use non-nightly rustfmt
gab8i 56fb349
Merge branch 'main' into gab_webrtc
gab8i 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
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.
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.
Should we move the
write_ready.listen()outside theBox::pinfuture?Currently, the write listener is registered once the the
when_substreams_rw_readyis firstly polled.This means we could arrive in a situation where
.notify(usize::MAX);is called before registering the listener call.For this to happen we need to:
message_sending.as_ref().as_pin_ref().is_none()should have some data to effectively take theNonepath and ignore thewhen_substreams_rw_ready.select_next_some()Moving the listener above
Box::pinsolves this regardless of which states callwhen_substreams_rw_ready.poll_nextand avoids the problem entirelyThere 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.
You are totally right, it should definitely be moved out so that it is registered and the async block later on depends on the registered event listener!