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

Update based on fixes made in the websockets/ws package #551

Closed

Conversation

henriquemps
Copy link

@henriquemps henriquemps commented Aug 4, 2021

Adjust based on fix made in websockets/ws. In this commit: websockets/ws@0aecf0c#diff-44c2c0628f273ea1ab6dbb7c1fa81a1765d8adf9fbdd083e2a3b93d8d1cb5f61

@oberstet
Copy link
Contributor

oberstet commented Aug 4, 2021

thanks for contributing! unfortunately, this hard codes the protocol to msgpack when the user specifies subprotocols. also, what is the issue being addressed with this change .. this #550 ?

@henriquemps
Copy link
Author

Exactly, this error. I thought it was interesting to keep the parameter optional and so I put a default value.

When the "protocol" is not specified, the error is displayed, precisely because the validation was changed.

Of course, I believe that at other points where a "join" is used will need to change, as the ws package is accepting "array" and not "string".

@om26er
Copy link
Contributor

om26er commented Nov 16, 2022

We currently limit the ws version to be < 8.0. We'll have to come up with a proper fix for it #569

@om26er om26er closed this Nov 16, 2022
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.

3 participants