This repository has been archived by the owner on Apr 2, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Sometimes the worker will panic with "specified instant was later than self" #7
Comments
@dylanede Have you debugged this further? I'm thinking of using stdlib promises that this panic will only occur if line 170 It looks like I'm going to use this and try to provoke the panic. I'm not entirely sure what to do if I prove the above as the problem but there are some obvious choices. |
I'm going to look at this some now. |
Ok, it looks like there should be a guard there to prevent going negative... should be a simple fix. |
This should be fixed by c933447. Sorry for the delay. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The trace points to
tokio-timer/src/worker.rs
Line 170 in c944a24
This only happens very occasionally, but it's enough to be a serious problem for a company internal tool I'm in the process of writing. This tool implements a protocol on top of UDP, and it uses
Sleep
s to wait between resending packets while waiting for ACKs. The time being slept for is 500ms, and there may be many sleeps happening at once.Other than this problem, futures-rs and the tokio ecosystem have been great to work with!
Full trace for the thread is
The text was updated successfully, but these errors were encountered: