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
abort h2 frame handling on StreamClosedError #27789
abort h2 frame handling on StreamClosedError #27789
Conversation
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.
This looks very reasonable to me.
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.
From the failing unittests, please fix:
./wptserve/wptserve/server.py:490:9: F841 local variable 'e' is assigned to but never used
./wptserve/wptserve/server.py:528:9: F841 local variable 'e' is assigned to but never used
./wptserve/wptserve/server.py:531:12: E111 indentation is not a multiple of four
./wptserve/wptserve/server.py:532:12: E111 indentation is not a multiple of four
In terms of the actual change itself, I will rely on @ricea 's knowledge here as I know little of h2 or ws, so generally LGTM modulo fixing the lint failures.
workaround #2778 This does not fix the issue, but in practice, allows us to run ./wpt run websockets/
This looks very similar to #27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable.
This looks very similar to #27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable.
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 98d1490d106a7518dfe2c810f5b2032ca7d7eac1
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 98d1490d106a7518dfe2c810f5b2032ca7d7eac1
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 98d1490d106a7518dfe2c810f5b2032ca7d7eac1
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 4d0434914c9e18bb7c561fa93cc368fd2370df3d
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 4d0434914c9e18bb7c561fa93cc368fd2370df3d
…h2 data, a=testonly Automatic update from web-platform-tests Catch ProtocolError when trying to send h2 data This looks very similar to web-platform-tests/wpt#27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable. -- wpt-commits: fb5913ec08d888a05d3e21ba68106bdeb101138f wpt-pr: 43753 UltraBlame original commit: 4d0434914c9e18bb7c561fa93cc368fd2370df3d
This looks very similar to #27789 except we seem to be getting a ProtocolError rather than a StreamClosedError. Handling that by stopping trying to send more data seems pretty reasonable.
workaround #27786
This does not fix the issue, but in practice, allows us to run ./wpt run
websockets/