fix handler signature to address websocket errors#3134
Merged
Conversation
mkultraWasHere
approved these changes
Feb 25, 2025
|
1 similar comment
|
This was referenced Feb 26, 2025
Closed
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
2 participants
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.
Description
Address websocket errors in #3121 caused by incorrect handler function signatures.
Update required websockets version to 15.0
Type of change
How Has This Been Tested?
Ran with response plugin to verify at least one websocket handler was triggered. Also confirmed error message stopped appearing on server startup.
Tested with Python 3.12.3 and websockets v15
Checklist: