You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm absolutely positive I'm doing this wrong; I have a rotor_http::client::Persistent<P, S> machine, which wraps rotor_http::client::Parser<P, S>.
If I use a Notifier to wake up my fsm while a request is active, I get a panic in the Parser and everything blows up. The source of the panic is this line in the Parser wrapper:
So if I shouldn't be waking up my fsm while it's already busy, how can I avoid calling wakeup in code that doesn't know what that machine is up to? I would've thought you could just ignore wakeup on a busy machine, because it's already awake?
The text was updated successfully, but these errors were encountered:
I'm absolutely positive I'm doing this wrong; I have a
rotor_http::client::Persistent<P, S>
machine, which wrapsrotor_http::client::Parser<P, S>
.If I use a
Notifier
to wake up my fsm while a request is active, I get a panic in theParser
and everything blows up. The source of the panic is this line in theParser
wrapper:https://github.com/tailhook/rotor-http/blob/master/src/client/parser.rs#L576
So if I shouldn't be waking up my fsm while it's already busy, how can I avoid calling
wakeup
in code that doesn't know what that machine is up to? I would've thought you could just ignorewakeup
on a busy machine, because it's already awake?The text was updated successfully, but these errors were encountered: