-
Notifications
You must be signed in to change notification settings - Fork 104
Fix "Event loop is closed" race in EventLoopThread.force_stop #727
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional follow-up, not for this PR: the read side is now safe, but the write side that creates the window is still
bellows/thread.py:29-31:Swapping those to publish
Nonebefore closing narrows the window in whichself.loopnames a closed loop:That doesn't remove the need for this
suppress— a caller can still snapshot the loop just beforeclose()runs — but it also protects the two other readers ofself.loopthat this PR doesn't touch:run_coroutine_threadsafe()(line 19) passesself.loopstraight toasyncio.run_coroutine_threadsafe, which raises the sameRuntimeErroron a closed loop, andstart()'s restart guard (line 35). It's safe forstart()either way, since aNoneloop already falls through to creating a new one.Entirely fine to leave for a separate change — the flake this PR targets is fixed as-is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zigpy-review-bot Create an issue or PR to follow up on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened #739 for this.
It does the swap suggested above —
loop, self.loop = self.loop, Nonebeforeloop.close()— soself.loopis eitherNoneor an open loop for every reader, not just the oneforce_stopguards. While writing it up, one extra benefit turned up that the original comment did not mention: the old trailingself.loop = Noneran afterclose(), so astart()racing the shutdown could have its freshly installed loop clobbered back toNoneby the exiting thread. The swap removes that write entirely.The
suppress(RuntimeError)this PR added stays — it is still reachable, and no ordering in_thread_maincan remove it.test_thread_clears_loop_before_closingpins the ordering itself (it records whatself.loopis at the momentclose()is called); it fails ondevand passes with the change. Full suite: 441 passed.