-
Notifications
You must be signed in to change notification settings - Fork 9
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
"dispatch dropped without returning error" #18
Comments
(Got pinged, so I'll just chime in, I don't know anything about this project in particular.) Reusing a client with a runtime that starts up and shuts down is indeed causing that panic. If you don't want to deal with async at all, you could consider replacing your usage with |
@seanmonstar Thanks for confirming (and for your work on your libraries)! And thank you @RoxasShadow et al for this library 🙂 . We're currently working around this by not reusing the same client. With this confirmation, I could look into switching this lib over to using |
Can't switch to |
I believe we're running into a manifestation of this panic in
hyper
: hyperium/hyper#2112See the following Rollbar payload:
We have an Actix app (the
actix::init_application
in the trace) that at the very start doesreport_panics!
, and then when an error occurs during any of the endpoint handlers we do:We aren't using
hyper
anywhere else, aside from indirectly throughrollbar-rs
, so from what I can gather from the above trace, therollbar.build_report()...send();
code panics withinhyper
with thedispatch dropped without returning error
message, and that panic is caught in the hook set up byreport_panics!
and then successfully sent to Rollbar.In the aforementioned
hyper
issue, @seanmonstar states (IIUC) that this panic can arise when thetokio
executer drops the background tasks spawned by thehyper
client before those tasks have managed to determine if the connection was closed, and that this can happen when the client is used from multiple executers.I see in
rollbar-rs/src/lib.rs
Lines 521 to 537 in b4ad68a
Maybe there's something about how the client is used in conjunction with
tokio
'scurrent_thread::Runtime
that's not safe when using the same rollbar client (which then in turn means reusing the samehyper
client)?The text was updated successfully, but these errors were encountered: