Fix Asyncio Bug #246
Open
Fix Asyncio Bug #246
Conversation
This file contains 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
…d uvicorn config.
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.
Fixing
asyncio.Queuecreation and usage by decoupling app, queues, and uvicorn config. This fixes issue #244.Creating
from_userandto_deviceoutside the main coroutine event loop creates futures in another event loop. With this fix the 01OS responds better and with voice using local models.Tested on Debian 11 with Python versions 3.9.19 and 3.11.9
Resources in regard to this fix:
https://stackoverflow.com/questions/53724665/using-queues-results-in-asyncio-exception-got-future-future-pending-attached
fastapi-users/fastapi-users#663 (reply in thread)
tiangolo/fastapi#3854 (comment)
tiangolo/fastapi#6566