Conversation
Member
|
Besides being AI generated, which is against our policy, this introduces extreme inefficiency due to pushing and popping the context on every loop. |
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
2 participants
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.
What changed
stream_with_contextnow pushes the captured context only while advancing or closing the wrapped iterator. This prevents an abandoned stream finalized on another thread from leaving the worker thread with a stale application context.Added a regression test covering a cross-thread stream finalization and a subsequent request on the same worker.
Testing
uv run --project C:/oss-flask pytest C:/oss-flask/tests -q(492 passed)Fixes #6123