!Send Future fails Miri check

[coder137]

Version
1.38.1 and 1.39.2

Platform
Ubuntu, Windows and Mac
https://github.com/coder137/ticked-async-executor/actions/runs/10259175195

Description
Creating TickedAsyncExecutor to advance local async tasks only when the executor is ticked.
Repo reference: https://github.com/coder137/ticked-async-executor

The tokio test(s) fail only when future provided is !Send and join! macro is used.

Replication

Passing test when Send future is used:

Branch: https://github.com/coder137/ticked-async-executor/tree/tokio_test
Test: https://github.com/coder137/ticked-async-executor/blob/tokio_test/tests/tokio_tests.rs
CI: https://github.com/coder137/ticked-async-executor/actions/runs/10259106870

Failing test when !Send future is used:

Branch: https://github.com/coder137/ticked-async-executor/blob/tokio_test_spawn_local
Test: https://github.com/coder137/ticked-async-executor/blob/tokio_test_spawn_local/tests/tokio_tests.rs
CI: https://github.com/coder137/ticked-async-executor/actions/runs/10259175195

Failing info/logs

= help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information

0_build (ubuntu-latest).txt

[Darksonn]

Does this still happen with #6744? It's in the master branch, but not yet a release.

[coder137]

Miri still fails,
Is this a false positive, or is using join! fundamentally unsound?

Upgraded the tokio rev tag to use #6744

Test Patch: coder137/ticked-async-executor@6cc5e9d#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542
CI/CD: https://github.com/coder137/ticked-async-executor/actions/runs/10274884563

[Darksonn]

Like what #6744 did, I recommend filing an issue with miri.

[Darksonn]

I'll close this for not being an issue in Tokio, but I'll be keeping an eye on the other thread.