fix: use persistent event loop in file watcher to prevent crashes on Windows#77
Open
haosenwang1018 wants to merge 1 commit intozilliztech:mainfrom
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #75
On Windows,
asyncio.run()creates and then closes a ProactorEventLoop on each call. After the first file change is processed, the closed loop causes httpcore's connection cleanup to fail withRuntimeError: Event loop is closedon subsequent file changes.This fix replaces
asyncio.run()with a persistent event loop (asyncio.new_event_loop()) that stays open across watcher callbacks, preventing the loop-closed error on repeat file modifications.