tokio: Poll op error

Version List the versions of all tokio crates you are using. The easiest way to get this information is using cargo tree subcommand:

????????? console-subscriber v0.1.0 (https://github.com/tokio-rs/console?branch=main#31704326)
???   ????????? console-api v0.1.0 (https://github.com/tokio-rs/console?branch=main#31704326)
???   ???   ???   ???   ????????? tokio v1.13.0
???   ???   ???   ???   ???   ????????? tokio-macros v1.5.1 (proc-macro)
???   ???   ???   ???   ????????? tokio-util v0.6.9
???   ???   ???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ???   ????????? tokio-io-timeout v1.1.1
???   ???   ???   ???       ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio-stream v0.1.8
???   ???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio-util v0.6.9 (*)
???   ???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ???   ????????? tokio-stream v0.1.8 (*)
???   ???   ???   ???   ????????? tokio-util v0.6.9 (*)
???   ????????? tokio v1.13.0 (*)
???   ????????? tokio-stream v0.1.8 (*)
???   ???   ????????? tokio v1.13.0 (*)
???   ???   ????????? tokio-rustls v0.22.0
???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio-rustls v0.22.0 (*)
???   ???   ????????? tokio v1.13.0 (*)
???   ???   ????????? tokio-rustls v0.22.0 (*)
???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio v1.13.0 (*)
???   ???   ???   ????????? tokio-rustls v0.22.0 (*)
???   ???   ????????? tokio-stream v0.1.8 (*)
????????? tokio v1.13.0 (*)

Platform The output of uname -a (UNIX), or version and 32 or 64-bit (Windows)

Windows 64-bit

Description Enter your issue details here. One way to structure the description:

[short summary of the bug]

I tried this code: N/A (Can’t find out where it is coming from)

[code sample that causes the bug]

I expected to see this happen: Shouldn’t log an error

Instead, this happened: Logs this error: https://sourceb.in/wwCmo0qpY7

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 26 (26 by maintainers)

Most upvoted comments

In the discord, the lines src/time/driver/sleep.rs:368 and src/time/driver/sleep.rs:379 were cited as the source of the prints.

Darksonn on Oct 31, 2021

@Milo123459 What you can do as a workaround is:

#[tokio::main]
async fn main() {
    tokio::spawn(async move {
          console_subscriber::init();
          tokio::time::sleep(tokio::time::Duration::from_secs(4)).await; 
    })
}

zaharidichev on Nov 22, 2021

Yes, the issue has been identified. Basically, the problem is that these tasks have been spawned before the console subscriber has been initialized. Will submit a fix in a day or two. The problem is that there is not an elegant fist apart from ignoring the error and dropping these events without printing annoying messages

zaharidichev on Nov 14, 2021

will take a look very shortly

zaharidichev on Nov 2, 2021