-
Notifications
You must be signed in to change notification settings - Fork 39
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
Not all tasks scheduled with Executor
are run
#171
Comments
It looks like in both cases, removing |
Ah, so if |
I believe this should be overall more correct. Previously, if the callback taken by `process_events` scheduled a task, `process_events` could exit with the readiness of `self.ping` cleared, but `notified` set to `true`. In which case, future calls to `schedule` would not wake the event source. Fixes Smithay#171.
I believe this should be overall more correct. Previously, if the callback taken by `process_events` scheduled a task, `process_events` could exit with the readiness of `self.ping` cleared, but `notified` set to `true`. In which case, future calls to `schedule` would not wake the event source. Fixes #171.
Not sure exactly what's going on, but some code I have trying to use calloops
Executor
doesn't always end up running the scheduled tasks. Adding a print to the start of theasync {
block shows it never starts. Using a different executor doesn't have this problem.Here's a minimal case where I see an issue like this. It's not really reflective of exactly what I was doing where I ran into this, but it's an interesting case, where
"Baz"
surely should be printed, but isn't:The text was updated successfully, but these errors were encountered: