Fix ModbusSerialServer super().__init__ Parameter Order #1870
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In the constructor for
ModbusSerialServer, the call tosuper().__init__flipped the"request_tracer"and"response_manipulator"parameters. Passing arequest_traceras normal resulted in a"cannot unpack non-iterable NoneType object"error when a request was recieved.To reproduce the same bug, replace the TCP server with a serial server in the
server_hook.pyexample.Fixed by reversing the two parameters in the function call. Also added labels to try and prevent further ordering issues if parameters are changed in the future.