fix: handle missing event loop in close() during interpreter shutdown#208
Open
haosenwang1018 wants to merge 1 commit intoHKUDS:mainfrom
Open
fix: handle missing event loop in close() during interpreter shutdown#208haosenwang1018 wants to merge 1 commit intoHKUDS:mainfrom
haosenwang1018 wants to merge 1 commit intoHKUDS:mainfrom
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
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 #135
When the
atexithandler callsclose(), the default event loop policy may already be torn down during interpreter shutdown, causingasyncio.run()to raiseRuntimeError: There is no current event loop in thread 'MainThread'.This fix adds a fallback: if
asyncio.run()fails, we manually create a new event loop withasyncio.new_event_loop()and run the finalization there. This ensures storages are properly finalized regardless of when the cleanup runs.