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.

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

Closed
CalliEve opened this issue Dec 15, 2020 · 7 comments · Fixed by #76 or #78
Closed

Upgrade to tokio 0.3 #71

CalliEve opened this issue Dec 15, 2020 · 7 comments · Fixed by #76 or #78

Comments

@CalliEve
Copy link

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.

@flosse
Copy link
Member

flosse commented Dec 21, 2020

@Baev1 Thanks for reporting this. Unfortunately we currently have no capacity to update this crate.
So feel free to open a PR ;-)

@flosse flosse modified the milestones: v0.4.0, v0.5.0 Dec 21, 2020
@CalliEve
Copy link
Author

@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.

@flosse
Copy link
Member

flosse commented Dec 21, 2020

I will look into making a PR to help with this,

great!
And don't hesitate to ask for help :)

@uklotzde
Copy link
Member

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.

@CalliEve
Copy link
Author

I skimmed through the dependencies and it seems to me tokio-serial will be a blocker for this, as it also uses tokio 0.2. In addition tokio-serial uses mio-serial, which depends on mio 0.6, while afaik tokio 0.3 uses mio 0.7 and I am not sure if that would then in turn block tokio-serial from using tokio 0.3 or not.

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 net2 is deprecated in favour of socket2.

@llamicron
Copy link

Has there been any progress on this? More popular crates have been updating to tokio 1.0 or at least tokio 0.3, which makes integration with this difficult. Is this still on the roadmap?

@flosse
Copy link
Member

flosse commented Mar 4, 2021

@llamicron I'm quite busy right now but feel free to continue with #72 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants