Repository navigation
fix(runtime-sdk): fix contextvars not being shared in WSGI streaming response #288
New issue
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
Open
ryanking13
wants to merge
2
commits into
main
Choose a base branch
from
gyeongjae/flask-stream
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
70 changes: 70 additions & 0 deletions
70
packages/runtime-sdk/tests/web-frameworks-test/flask-tests/src/test_stream_with_context.py
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| import asyncio | ||
|
|
||
| import js | ||
| import pytest | ||
| from flask import ( | ||
| Flask, | ||
| Response, | ||
| has_request_context, | ||
| request, | ||
| stream_with_context, | ||
| ) | ||
|
|
||
| from workers import wsgi | ||
|
|
||
| app = Flask(__name__) | ||
| # Request values whose stream_with_context generator has run its cleanup. | ||
| closed: list[str] = [] | ||
|
|
||
|
|
||
| @app.get("/stream") | ||
| def stream(): | ||
| @stream_with_context | ||
| def body(): | ||
| value = request.args["value"] | ||
| try: | ||
| yield "flask:" | ||
| yield request.args["value"] | ||
| finally: | ||
| closed.append(value) | ||
|
|
||
| return Response(body(), content_type="text/plain") | ||
|
|
||
|
|
||
| async def fetch(value): | ||
| req = js.Request.new(f"http://example.com/stream?value={value}") | ||
| return await wsgi.fetch(app, req, {}) | ||
|
|
||
|
|
||
| @pytest.fixture(autouse=True) | ||
| def clear_closed(): | ||
| closed.clear() | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_stream_with_context(): | ||
| response = await fetch("stream-body") | ||
| assert response.status == 200 | ||
| # The request context pushed while priming the body must stay in the | ||
| # response's own context instead of leaking into the caller's. | ||
| assert not has_request_context() | ||
| assert await response.text() == "flask:stream-body" | ||
| assert closed == ["stream-body"] | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_concurrent_stream_with_context(): | ||
| responses = await asyncio.gather(fetch("first"), fetch("second")) | ||
| bodies = await asyncio.gather(*(response.text() for response in responses)) | ||
| assert bodies == ["flask:first", "flask:second"] | ||
| assert sorted(closed) == ["first", "second"] | ||
|
|
||
|
|
||
| @pytest.mark.asyncio | ||
| async def test_cancelled_stream_with_context(): | ||
| response = await fetch("cancel") | ||
| reader = response.body.getReader() | ||
| first = await reader.read() | ||
| assert first.value.to_bytes() == b"flask:" | ||
| await reader.cancel() | ||
| assert closed == ["cancel"] |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So to clarify is this a workaround for stack switching being wrong? Or is what is happening the expected behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if the comment would include a position on this. I think this means that our stack switching is still wrong, since the context variables shouldn't change across a stack switch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well we are using stack switching here and there every time we need to run async functions in the synchronous context. However, it depends whether the context should be switched or not.
I don't think "our stack switching is still wrong" since some times it makes sense to use different context, but not always that is the case.
IMO, we should maintain the current behavior where the context changes during a stack switch; however, for cases where the context must be preserved across a stack switch, we should document an approach like the one in this PR to prevent future bugs.