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
Switch over to tokio-0.2 (and drop preview versions of futures?) #160
Comments
Currently blocked on tokio-rs/tokio#1848 . There are workarounds but it seems easier to fix tokio first. |
WIP at branch |
Looking at |
That should not be a problem, the example I'm trying is |
Backtrace shows that the error happens in Backtrace
Is this a tokio bug? |
In the PR I use tokio-0.2.2 in all crates, but the error above persists. |
I don't get the error if I replace the line let mut runtime = tokio::runtime::Builder::new().build().unwrap(); with let mut runtime = tokio::runtime::Builder::new().enable_time().enable_io().build().unwrap(); or let mut runtime = tokio::runtime::Runtime::new().unwrap(); in echo.rs. It seems like the timer and io stuff isn't enabled by default with the Builder, but is actually required for tiny to work. Seems best to just create the |
That's it, thanks @FreeFull ! I wasn't even aware that I can enable/disable features when initializing the runtime.. |
Currently waiting for tokio-rs/tokio#1971 to be merged. |
Thinking about this more, if we want |
I think tokio-0.2.1 supports features we need so we should switch over to it and drop the git versions. That should make development easier as we'll be able to use the documentation on crates.io etc. Similarly we should also drop futures-preview and futures-utils-preview and use futures and futures-utils.
The text was updated successfully, but these errors were encountered: