We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It appears that the recent changes in the CLI to automatically create main workspace and user provokes issues with asyncpg (and probably aiomysql).
asyncpg
The problem is that before running uvicorn, we are running functions to create main workspace and user, which open connections to the DB.
uvicorn
After that, when Uvicorn runs, it setups a new event loop ; but the database connections objects are still the same and thus provokes errors.
This is due to our lack of isolation of our main engine and workspace engine manager.
The text was updated successfully, but these errors were encountered:
Fixed is currently implemented and make sure we don't break isolation for DB connections.
Sorry, something went wrong.
ef31bb5
Bump version 0.17.3 → 0.17.4
7d57fdb
Bug fixes --------- * Fix #90: improve DB connections isolation to avoid issues when running server from CLI. Thanks @gooseman1721 for raising this 🙏
frankie567
No branches or pull requests
Discussed in https://github.com/orgs/fief-dev/discussions/89
It appears that the recent changes in the CLI to automatically create main workspace and user provokes issues with
asyncpg
(and probably aiomysql).The problem is that before running
uvicorn
, we are running functions to create main workspace and user, which open connections to the DB.After that, when Uvicorn runs, it setups a new event loop ; but the database connections objects are still the same and thus provokes errors.
This is due to our lack of isolation of our main engine and workspace engine manager.
The text was updated successfully, but these errors were encountered: