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

Task migration in docs 1.7.0-rc2 #42767

Closed
nielsls opened this issue Oct 22, 2021 · 2 comments
Closed

Task migration in docs 1.7.0-rc2 #42767

nielsls opened this issue Oct 22, 2021 · 2 comments
Labels
docs This change adds or pertains to documentation

Comments

@nielsls
Copy link

nielsls commented Oct 22, 2021

The NEWS file states that:

Tasks can now migrate among threads when they are re-scheduled. Previously, a Task would always run on whichever thread executed it first (#40715).

But the docs do not seem to be updated accordingly. They still say, that:

After a task starts running on a certain thread (e.g. via @Spawn), it will always be restarted on the same thread after blocking. In the future this limitation will be removed, and tasks will migrate between threads.

I guess the future is now?

@simeonschaub simeonschaub added the docs This change adds or pertains to documentation label Oct 23, 2021
@KristofferC
Copy link
Member

The part in the docs is at

* After a task starts running on a certain thread (e.g. via `@spawn`), it
will always be restarted on the same thread after blocking. In the future
this limitation will be removed, and tasks will migrate between threads.

@nielsls
Copy link
Author

nielsls commented Apr 4, 2022

Resolved by #43496

@nielsls nielsls closed this as completed Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

No branches or pull requests

3 participants