-
Notifications
You must be signed in to change notification settings - Fork 173
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
fix: ws server terminate subscriptions when connection is closed by the client. #483
Merged
Merged
Changes from 6 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
89778ba
fix: server should not send to closed subscription
niklasad1 65821c0
add a test
niklasad1 425bdb2
rewrite me
niklasad1 8b213ef
remove faulty server close
niklasad1 ae44737
fix tests
niklasad1 3fea64f
fix tests
niklasad1 5bc0e02
remove needless code
niklasad1 25bd997
Update ws-client/src/client.rs
niklasad1 8d9a5b1
fix: remove atomic flag; use `close_sender`
niklasad1 8907702
Merge remote-tracking branch 'origin/master' into na-fix-481
niklasad1 3109f43
Merge branch 'na-fix-481' of github.com:paritytech/jsonrpsee into na-…
niklasad1 c8bfd3a
remove terminate message; use close channel
niklasad1 a8523c2
remove faulty subscription closed error msg
niklasad1 db10297
fix tests
niklasad1 7980f77
fix grumbles
niklasad1 e4514ed
fix build
niklasad1 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 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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,6 +27,8 @@ | |
use std::future::Future; | ||
use std::net::SocketAddr; | ||
use std::pin::Pin; | ||
use std::sync::atomic::{AtomicBool, Ordering}; | ||
use std::sync::Arc; | ||
use std::task::{Context, Poll}; | ||
|
||
use crate::future::{FutureDriver, StopHandle, StopMonitor}; | ||
|
@@ -209,16 +211,19 @@ async fn background_task( | |
conn_id: ConnectionId, | ||
methods: Methods, | ||
max_request_body_size: u32, | ||
stop_monitor: StopMonitor, | ||
stop_server: StopMonitor, | ||
) -> Result<(), Error> { | ||
// And we can finally transition to a websocket background_task. | ||
let (mut sender, mut receiver) = server.into_builder().finish(); | ||
let (tx, mut rx) = mpsc::unbounded::<String>(); | ||
let stop_conn = Arc::new(AtomicBool::new(false)); | ||
|
||
let stop_server2 = stop_server.clone(); | ||
let stop_conn2 = stop_conn.clone(); | ||
niklasad1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
let stop_monitor2 = stop_monitor.clone(); | ||
// Send results back to the client. | ||
tokio::spawn(async move { | ||
while !stop_monitor2.shutdown_requested() { | ||
while !stop_server2.shutdown_requested() && !stop_conn2.load(Ordering::SeqCst) { | ||
niklasad1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
match rx.next().await { | ||
Some(response) => { | ||
log::debug!("send: {}", response); | ||
|
@@ -228,20 +233,24 @@ async fn background_task( | |
None => break, | ||
}; | ||
} | ||
|
||
drop(stop_monitor2); | ||
// terminate connection. | ||
let _ = sender.close().await; | ||
// NOTE(niklasad1): when the receiver is dropped no further requests or subscriptions | ||
// will be possible. | ||
}); | ||
|
||
// Buffer for incoming data. | ||
let mut data = Vec::with_capacity(100); | ||
let mut method_executors = FutureDriver::default(); | ||
|
||
while !stop_monitor.shutdown_requested() { | ||
while !stop_server.shutdown_requested() { | ||
data.clear(); | ||
|
||
method_executors.select_with(receiver.receive_data(&mut data)).await?; | ||
if let Err(e) = method_executors.select_with(receiver.receive_data(&mut data)).await { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. NOTE; this will kill a connection on any soketto::connection::Error, not just if the client terminated the connection In a follow-up PR I think we should try to do some graceful error handling |
||
log::error!("Could not receive WS data: {:?}; closing connection", e); | ||
stop_conn.store(true, Ordering::SeqCst); | ||
return Err(e.into()); | ||
} | ||
|
||
if data.len() > max_request_body_size as usize { | ||
log::warn!("Request is too big ({} bytes, max is {})", data.len(), max_request_body_size); | ||
|
@@ -295,9 +304,6 @@ async fn background_task( | |
// Drive all running methods to completion | ||
method_executors.await; | ||
|
||
// Drop the monitor for this task since we are shutting down | ||
drop(stop_monitor); | ||
|
||
Ok(()) | ||
} | ||
|
||
|
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.
This is a bit opaque unless one knows exactly what is going on.
Maybe we can do something like this?
It's a bit annoying that
SubscriptionClosedErr
has a private member (and that there's no way for the client to know what the subscription ID is) or we could have usedassert_matches
here for better readability...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.
Yepp, I think we could replace SubscriptionClosed(String) with a better type.
Perhaps with a
kind enum
, to distinguish why the subscription was closed the error message is quite useful atm