task runs on wasm but on native, task is scheduled but never runs

[bananaturtlesandwich]

Bevy version: 0.16.1

OS: Windows 10

What you did

This is a bit of a weird one because I could have sworn it used to work and it still works on wasm. I'm spawning a future on the IoTaskPool like so (the future is a bsky api request and compat allows tokio compatibility):

bevy::tasks::IoTaskPool::get().spawn(Compat::new(
    CLIENT.service.app.bsky.actor.get_profile(
        get_profile::ParametersData {
            actor: actor.clone(),
        }
        .into(),
    ),
))

I then have a separate system running which polls the task in the Update Schedule

    match ask.task.as_mut().and_then(|task| bevy::tasks::block_on(
      bevy::tasks::futures_lite::future::poll_once(task)
    )) {
        Some(Ok(profile)) => ...
        Some(Err(e)) => ...
        None => return,
    }
    ask.task = None;

What went wrong

this is working perfectly on wasm! however on native builds the task never finishes. If I debug print the task then I get

Task(
    Task {
        header: Header {
            scheduled: true,
            running: false,
            completed: false,
            closed: false,
            awaiter: false,
            task: true,
            ref_count: 2,
            metadata: (),
        },
    },
)

which I think means it's been scheduled but never gets run which is very bizarre.
Unsure on what could be happening here

[hymm]

I would expect this to work. Do you have a minimal reproduction or the code shared somewhere?

[bananaturtlesandwich]

I would expect this to work. Do you have a minimal reproduction or the code shared somewhere?

@hymm i've stripped it of everything but the asking state here

[hymm]

I tried running it on windows, but got a tokio error.

there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

One thing I noticed is that you have the webgl2 feature enabled unconditionally, which might cause problems.

[bananaturtlesandwich]

I tried running it on windows, but got a tokio error.

there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

One thing I noticed is that you have the webgl2 feature enabled unconditionally, which might cause problems.

weird the compat struct should make it not the case - I'm also running on windows
what would webgl2 change on a native build?