-
Notifications
You must be signed in to change notification settings - Fork 920
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
update to tokio 1.0 #1246
update to tokio 1.0 #1246
Conversation
Unrelated question: Is there any reason that you do not use tokio's multi-threaded runtime? |
I don't think this works, it's going to miss the reactor. Running it locally I get:
|
Tokio 0.2 and 0.3 are not backward compatible. Hyper still depends on tokio 0.2. They completed the 0.3 upgrade on their dev branch but haven't released a new version yet. Because we depend on Hyper, we have to wait till they release a new version, or use the |
Ah I thought it had been updated. Let's wait until hyper gets released then |
I updated tokio to 1.0.1 and hyper to 0.14.1. The issue now is that hyper-staticfile seems to be unmaintained and is still using hyper 0.13 which is causing compatibility issues. @Keats I could also write the file server directly with You might also consider using warp instead of hyper directly, which would simplify things a lot |
Which one would be the simplest without adding many new dependencies? |
The simplest would probably be to just write the file server manually. It would only require enabling the |
Let's go with that then if it's not too much work |
I wrote a simple custom file server and successfully tested it locally. This should conclude the Tokio 1.0 migration. The |
Thanks it works well! I'll merge it when reqwest is updated to avoid having multiple tokio versions |
Thanks! |
(I messed up an didn't notice the PR was on |
Not by me: #1246 Can't be arsed to figure out the issue I had with cherry-picking the commit and submodules. Originally merged on master by mistake
I updated the tokio version to
0.3.4
and updated to the newruntime::Builder
api. The updated runtime is equivalent to the current single-threaded runtime.Resolves #1240