Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"supplied instant is later than self" #215

Closed
Kampfkarren opened this issue Jul 14, 2019 · 4 comments
Closed

"supplied instant is later than self" #215

Kampfkarren opened this issue Jul 14, 2019 · 4 comments
Labels
status: needs repro We need more information on how to reproduce this issue. type: bug Something happens that shouldn't happen

Comments

@Kampfkarren
Copy link
Member

I just had a Rojo server running in the background for a longtime (no longer than 12 hours?) without even anything syncing when I noticed this panic:

thread 'tokio-runtime-worker-1' panicked at 'supplied instant is later than self', src/libcore/option.rs:1034:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
thread 'thread 'tokio-runtime-worker-0tokio-runtime-worker-3' panicked at '' panicked at 'supplied instant is later than selfsupplied instant is later than self', ', src/libcore/option.rssrc/libcore/option.rs::10341034::55

The server continued to run.
@LPGhatguy LPGhatguy added type: bug Something happens that shouldn't happen status: external An external project is the cause of this labels Jul 15, 2019
@LPGhatguy
Copy link
Contributor

I'm going to bet this is a Tokio bug!

@Kampfkarren
Copy link
Member Author

I can start using RUST_BACKTRACE from now on to see if that's right.

@Kampfkarren
Copy link
Member Author

I've left Rojo on for several nights in a row, but have yet to experience this again, strange.

@LPGhatguy LPGhatguy mentioned this issue Aug 27, 2019
Merged
@LPGhatguy LPGhatguy added status: needs repro We need more information on how to reproduce this issue. and removed status: external An external project is the cause of this labels Aug 27, 2019
@LPGhatguy
Copy link
Contributor

Since we never found a repro, I'm going to close this.

We'll migrate to a newer version of Tokio eventually, which might help resolve any future weirdness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: needs repro We need more information on how to reproduce this issue. type: bug Something happens that shouldn't happen
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LPGhatguy @Kampfkarren