Fix WebSocket BatchLimit Test Timeout Error on MacOS#16431
Closed
grandchildrice wants to merge 1 commit into
Closed
Fix WebSocket BatchLimit Test Timeout Error on MacOS#16431grandchildrice wants to merge 1 commit into
grandchildrice wants to merge 1 commit into
Conversation
Contributor
|
I have no capacity to check this right now, can you look @canepat ? |
Member
Yep, I'm on it |
Member
|
I've been able to reproduce the deadlock in and executing the test repeatedly: This is the output: which also contains an additional log added in |
Member
|
Replaced by #16829 |
AskAlexSharov
pushed a commit
that referenced
this pull request
Aug 27, 2025
NazariiDenha
pushed a commit
that referenced
this pull request
Oct 24, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
#16382
Cause
The WebSocket batch limit test was timing out on macOS because when the batch limit was exceeded, the server would close the connection abruptly without sending a proper WebSocket close frame. This caused the client to hang waiting for a response, leading to test timeouts.
Fix
Added proper WebSocket connection closing when batch limit is exceeded:
Test Execution Command:
go test -v ./rpc -run TestBatchLimit_WebSocket_ExceededNote
Since I didn't have a Mac OS environment at hand, I am conducting operational checks on the CI of the forked repository. If anyone has a Mac OS environment, I think it would be best to test it on your own machine.
https://github.com/grandchildrice/erigon/actions/runs/16712583476