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

websocket: set websocket readyState on fail #3507

Merged
merged 1 commit into from
Aug 25, 2024

Conversation

KhafraDev
Copy link
Member

Fixes #3506

This relates to...

Rationale

Changes

Features

Bug Fixes

Breaking Changes and Deprecations

Status

Fixes nodejs#3506

set websocket readyState on fail

Fixes nodejs#3506
Copy link
Contributor

@Uzlopak Uzlopak left a comment

Choose a reason for hiding this comment

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

not a big brainer to review. :D

@Uzlopak Uzlopak changed the title set websocket readyState on fail fix: set websocket readyState on fail Aug 25, 2024
@Uzlopak Uzlopak changed the title fix: set websocket readyState on fail websocket: set websocket readyState on fail Aug 25, 2024
@KhafraDev
Copy link
Member Author

Failing tests are due to v20.7.0 buffer bugs. I'm surprised the autobahn suite didn't cover this though.

@KhafraDev KhafraDev merged commit e96178f into nodejs:main Aug 25, 2024
32 of 33 checks passed
@KhafraDev KhafraDev deleted the set-ws-readystate-on-fail branch August 25, 2024 18:04
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.

WebSocket - Opening a connection to a non-existent server fire a error but keeps CONNECTING state indefinitely
2 participants