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

no method named reset found for struct Pin<&mut Interval> in the current scope #5655

Closed
miro-hatch opened this issue Apr 25, 2023 · 3 comments · Fixed by #5657
Closed

no method named reset found for struct Pin<&mut Interval> in the current scope #5655

miro-hatch opened this issue Apr 25, 2023 · 3 comments · Fixed by #5657
Labels
A-tokio-stream Area: The tokio-stream crate C-bug Category: This is a bug.

Comments

@miro-hatch
Copy link

Version

tokio-stream v0.1.13

Platform

Linux 5.15.0-1031-gcp #38~20.04.1-Ubuntu

Description

Missing method after cargo update to 0.1.13:

Compiling tokio-stream v0.1.13
error[E0599]: no method named reset found for struct Pin<&mut Interval> in the current scope
--> /home/manager/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-stream-0.1.13/src/stream_ext/timeout_repeating.rs:39:33
|
39 | me.interval.reset();
| ^^^^^ help: there is a method with a similar name: set

@miro-hatch miro-hatch added A-tokio Area: The main tokio crate C-bug Category: This is a bug. labels Apr 25, 2023
@Darksonn Darksonn added A-tokio-stream Area: The tokio-stream crate and removed A-tokio Area: The main tokio crate labels Apr 25, 2023
@Darksonn
Copy link
Contributor

Thanks for reporting this. You need to use a newer version of Tokio. We will submit another release with the correct minimum Tokio version listed.

@dnut
Copy link

dnut commented Apr 25, 2023

I would also yank any versions of tokio-stream that have this issue because it prevents cargo from selecting versions properly. Some crates have a maximum version of tokio, and it's a pain to get any code that depends on them to compile with 0.1.13 available.

I solved it by putting this in my crate's Cargo.toml, but this really shouldn't be necessary, since I don't even depend on tokio-stream directly:

tokio-stream = "=0.1.12"

@Darksonn
Copy link
Contributor

This will be fixed in 0.1.14. See #5658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tokio-stream Area: The tokio-stream crate C-bug Category: This is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants