Performance History
Latest Results
test: cover waiter=None branch in finish_response message tail replay
goingforstudying-ctrl:fix/websocket-upgrade-hang
59 minutes ago
test: add mock parser to ensure code coverage for message tail preservation
The previous test did not set handler._parser, so the finish_response
method skipped the message tail handling entirely. Add a mock parser
that returns empty messages but preserves the tail, ensuring the
modified line (self._message_tail = tail) is actually executed and
covered by tests.
goingforstudying-ctrl:fix/websocket-upgrade-hang
4 hours ago
test(web_protocol): revert to mock parser in empty-tail test
The previous commit replaced the mock parser with a real partial message
tail (b'GET /second HTT') and wrong assertions. The real parser consumes
partial data internally and returns ([], False, b''), so the test failed
with AssertionError: assert b'' == b'GET /second HTT'.
Revert to the mock-based approach so we control feed_data's return value
and can reliably test the empty-messages branch in finish_response.
goingforstudying-ctrl:fix/websocket-upgrade-hang
4 hours ago
fix: preserve message tail in finish_response when parser returns empty
The previous code cleared _message_tail unconditionally after feeding
it to the parser. When the parser returns an empty messages list but
a non-empty tail (partial/incomplete data), the tail was lost.
Save the parser-returned tail back to _message_tail so incomplete
messages are preserved for the next iteration.
goingforstudying-ctrl:fix/websocket-upgrade-hang
4 hours ago
fix: restore _request_count increment in data_received for normal requests
The previous commit removed self._request_count += 1 from data_received
and only added it in finish_response for message tail replay. This broke
normal request counting, causing test_raw_server_logs_invalid_method to
fail because _request_count stayed 0 and BadHttpMethod was logged at
exception level instead of debug.
Keep the increment in data_received for all normal messages, and also
keep it in finish_response for tail replay messages.
goingforstudying-ctrl:fix/websocket-upgrade-hang
6 hours ago
fix: restore _request_count increment in data_received for normal requests
The previous commit removed self._request_count += 1 from data_received
and only added it in finish_response for message tail replay. This broke
normal request counting, causing test_raw_server_logs_invalid_method to
fail because _request_count stayed 0 and BadHttpMethod was logged at
exception level instead of debug.
Keep the increment in data_received for all normal messages, and also
keep it in finish_response for tail replay messages.
goingforstudying-ctrl:fix/websocket-upgrade-hang
6 hours ago
Latest Branches
0%
1 hour ago
7dafc36
goingforstudying-ctrl:fix/websocket-upgrade-hang
-1%
[PR #12787/4eb35886 backport][3.15] fix(connector): resolve race condition in TCPConnector.close()#12793
8 hours ago
3bf490f
patchback/backports/3.15/4eb358863b3797af1e5a6712b02a01f4a7fe985d/pr-12787
0%
[PR #12787/4eb35886 backport][3.14] fix(connector): resolve race condition in TCPConnector.close()#12792
8 hours ago
d13aed5
patchback/backports/3.14/4eb358863b3797af1e5a6712b02a01f4a7fe985d/pr-12787