fix: fastapi lifespan management with multiple apps at once #241
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
* introduce streamsync.serve.lifespan to gather lifespan of different streamsync application
FabienArcellier
changed the title
|
Incredible work with solid tests 💯 |
This pull request was closed.
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.
When streamsync is run by a FastAPI application as a subapplication, its kernel does not start. FastAPI ignores the lifespan associated with a sub-application. It fix #213 & #186.
The documentation Multiple apps at once is currently broken.
This PR provides a helper
streamsync.serve.lifespanfor the FastAPI application that scans apps mounted in FastAPI and identifies which are streamsync instances. The kernel of each application is started.