Skip to content
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

fix(ext/websocket): do not continue reading if socket rid closes #21849

Merged
merged 4 commits into from
Mar 9, 2024

Conversation

littledivy
Copy link
Member

@littledivy littledivy commented Jan 8, 2024

Fixes #21379

@littledivy littledivy requested a review from mmastrac January 8, 2024 12:44
Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a test for this change? Let's say a server forcefully closes the connection after exchanging 3 messages.

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Discussed offline, we have no way to create a precise unit test for it, because we'd need to expose these ops to the user code (which we don't want to do).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fresh Web Server dies with "Bad resource ID" in Dev Mode
2 participants