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
as of 201f133, the 10th (random number, seems to favour 0 but occasionally will be any number 0-9) thread in cargo run --release -- 'http://localhost:7667' examples/simpleish/seatrial.ron times out if ControlFlow(GoTo(..)) has a max_times set (perhaps also if it doesn't, I haven't comprehensively tested yet). unsure yet whether this is an issue with the vial-based server app or with seatrial itself.
The text was updated successfully, but these errors were encountered:
did some digging on this this afternoon. so far I've ruled out sigaloid's fork of vial being the issue (upstream still repros), and also have confirmed that our call to std::thread::sleep doesn't somehow poison the threadpool or something (removing the sleep still repros the issue)
I have at least isolated this to the example server app: running the example sequence against an internal Dockwa app does not repro this issue, but against the example server, repros reliably
as of 201f133, the 10th (random number, seems to favour 0 but occasionally will be any number 0-9) thread in
cargo run --release -- 'http://localhost:7667' examples/simpleish/seatrial.ron
times out ifControlFlow(GoTo(..))
has amax_times
set (perhaps also if it doesn't, I haven't comprehensively tested yet). unsure yet whether this is an issue with the vial-based server app or with seatrial itself.The text was updated successfully, but these errors were encountered: