[PR #10971/1ee187c0 backport][3.12] Fix WebSocketResponse.prepared
not correctly reflect the WebSocket's prepared state
#10983
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.
This is a backport of PR #10971 as merged into master (1ee187c).
This PR fixes an issue where the
WebSocketResponse.prepared
property did not correctly reflect the WebSocket's prepared state, particularly during timeout scenarios.Previously, the
prepared
property inherited fromStreamResponse
only checked for_payload_writer
, but in WebSocket timeout scenarios, the_writer
could be set while_payload_writer
remainedNone
, leading to incorrect state reporting.Changes
prepared
property toWebSocketResponse
that checks for_writer
instead of relying on the parent class's_payload_writer
checkprepare()
method to prevent double preparation when_writer
is already setfixes #6009