-
Notifications
You must be signed in to change notification settings - Fork 124
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
Upgrade to tokio 0.3 #71
Comments
@Baev1 Thanks for reporting this. Unfortunately we currently have no capacity to update this crate. |
@flosse thank you for your reply! I will look into making a PR to help with this, but after looking into things a bit more, I will wait for the soon upcoming 1.0 release of tokio (said to come at the end of this month) as announced back in October in their blog, as to prevent having to make another PR soon afterwards again. |
great! |
Afterwards we need to bump the version number to v0.5. Many crates still require tokio 0.2.x which might cause dependency conflicts in a project? Not sure about this. But because of these potential conflicts we should prepare ourselves for the upgrade. You could start with tokio 0.3.x to determine the current gap. 1.0 was announced to released before the end of this year. |
I skimmed through the dependencies and it seems to me I can't with confidence say if this all means we can or can't upgrade tokio here, but yeah it is be likely that I first have to take a look at making a PR for tokio-serial to bump their tokio version. Also, unrelated, but I noticed that |
Has there been any progress on this? More popular crates have been updating to |
@llamicron I'm quite busy right now but feel free to continue with #72 😃 |
Hi!
Currently tokio is on version 0.3.6, while this crate only supports the 0.2 versions of tokio.
Using the 0.3 versions of tokio leads to a
thread 'tokio-runtime-worker' panicked at 'there is no reactor running, must be called from the context of Tokio runtime'
runtime error, when using the tcp client to connect to something.The text was updated successfully, but these errors were encountered: