-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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_handshake
invalid function signature
#2272
Comments
@cnicodeme Can you add a PR for this, and I can get a patch released this weekend. |
Let me know if that works :) |
Awesome thanks. I'll take a look at why it's failing tomorrow 😎 I appreciate you calling this out and fixing it. |
You are welcome! That was an easy one to fix ;) (But I don't know why it refuses my PR, maybe some wrong code formatting) |
That could be. I'm on my phone so it's hard to see. Maybe line length? We run black on the code base so that might help. If you run |
Nope. Looks like mypy
@ashleysommer Maybe related to what you said you were seeing? |
* Replacing assignation by typing for `websocket_handshake` Related to #2272 * Fix some type hinting issues * Cleanup websocket handchake response concat * Optimize concat encoding Co-authored-by: Adam Hopkins <[email protected]>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is incorrect, please respond with an update. Thank you for your contributions. |
…2273) * Replacing assignation by typing for `websocket_handshake` Related to sanic-org#2272 * Fix some type hinting issues * Cleanup websocket handchake response concat * Optimize concat encoding Co-authored-by: Adam Hopkins <[email protected]>
Describe the bug
The function
websocket_handshake
located in sanic.server.protocols.websocket_protocol has an invalid signature in Sanic 21.9.2 (at least)Code snippet
Current code is:
Expected behavior
Code should be:
=> Typing should be set with ":", not "=" ;)
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: