-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Bump tokio MSRV to 1.63 #5887
Bump tokio MSRV to 1.63 #5887
Conversation
Also cleanup `build.rs` and remove dependency `autocfg`. Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Co-authored-by: Alice Ryhl <aliceryhl@google.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Replace `tokio_wasi` with `target_os = "wasi"` and replace latter with `cfg_is_wasm_not_wasi!` or `all(target_family = "wasm", not(target_os = "wasi"))`. Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
CI spuriously failed due to same error as #5885 (comment)
|
Please file a bug for the CI failure. |
I've opened issue #5888 for this. |
Co-authored-by: Taiki Endo <te316e89@gmail.com> Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Co-authored-by: Taiki Endo <te316e89@gmail.com>
By replacing `any(target_arch = "wasm32", target_arch = "wasm64")` with `target_family = "wasm"`. Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
@@ -107,8 +104,8 @@ mio = { version = "0.8.6", optional = true, default-features = false } | |||
num_cpus = { version = "1.8.0", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this not be replaced by std::thread::available_parallelism
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, this is outside the scope of this PR.
This PR is for bumping MSRV for tokio only, you can open another PR/issue/discussion for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
available_parallelism was stabilized with an incomplete implementation, and it is expected to cause regressions (e.g., OOM) in Rust 1.63 and smaller that doesn't have cgroupv1 support (rust-lang/rust#97925).
So I think we need to stick to num_cpus until MSRV becomes 1.64+.
Is there anything need to do for this PR to merge? Or are we just waiting for others' review? |
Thank you very much for the review! |
Does Tokio have a regular release cadence where we can plan on this being in a release soon? This feature is critical to a project I'm working on. |
No, we do not have a regular cadence for releases, but we were planning on making one soon. If you wish to speed up the process, then you can help us by submitting a PR that prepares the release. See #5650 for an example. |
@Darksonn what is the criteria for what goes into the changelog and what should the next version bump be? |
The next version number should be 1.30.0. As for what is included, well:
I will review your PR, so if anything is missing or should be omitted, I will let you know. |
@Darksonn is there a particular commit the next version should be PR'd against or just master/HEAD? |
The master branch is fine. |
Looking over your list of changelog requirements it seems I would need a very intimate familiarity with the code base and the API to determine what is and isn't a changed behavior. If you're using SEMVER and bumping the minor I assume there are only additive API changes and nothing breaking. |
Just categorize them according to how they look to you at a first glance. There's no need to be worried about getting it wrong—I will review the PR and tell you what things to change, if any. I know that you're not familiar with the codebase. |
You may assume that there are no breaking changes. |
Also
build.rs
autocfg
.socket2
to v0.5.3Motivation
Bumping tokio MSRV to 1.63 will make all features required available and thus removing the need for
build.rs
.It will also make
{Mutex, Notify, OnceCell, RwLock, Semaphore}::const_new
available by default and also make it possible for{Mutex, Notify, OnceCell, RwLock, Semaphore}::new
to be usable in const context (#5885).Solution
Bump tokio MSRV to 1.63