| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…st_context_propogation to apply this methodology
…nstead. DRY implementation
|
Done with all updates and ready for a review. |
Sorry, something went wrong.
|
Related: #1728 (v2 test client improvements) |
Sorry, something went wrong.
|
Thanks for the PR. This has since landed via #2765. Closing this as part of a wider backlog cleanup following the v2 launch. If it's still relevant, feel free to reopen. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This implements fixes to the StreamingASGITransport to properly handle SSE streaming and disconnect signaling. The key changes were:
Motivation and Context
Partially resolves #857
How Has This Been Tested?
Since I updated the testing methodology I made sure to run the test in batches of 30 (to check for race conditions). Using the command:
passed=0; failed=0; for i in {1..30}; do echo "=== Run $i/30 ===" && uv run --resolution="$RESOLUTION" pytest "$FILE_PATH" -q && passed=$((passed+1)) || failed=$((failed+1)); done; echo "==== SUMMARY: $passed passed, $failed failed out of 30 runs ===="
for the following resolutions and files:
All tests passed:
Breaking Changes
None. StreamingASGITransport is only meant for testing. The only change I made to SseServerTransport was to properly clean up sse_stream_reader which is best practice and doesn't break functionality. The modified tests all function as expected.
Types of changes
Checklist
Additional context