Fixed parsing of incomming packages when using rtde protocol v1 #114
Conversation
This file contains 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
|
Please rebase onto current master so we have a succeeding pipeline. |
The received rtde packages should be parsed slightly different whether we use protocol v1 or v2.
urmahp
force-pushed
the
setup_outputs_protocolv1
branch
from
a2611c6
to
243ff7e
Compare
|
Should I squash the commits to one commit? |
We do that when merging. We usually use the "squash and merge" strategy. |
fmauch
approved these changes
Sep 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The received rtde packages should be parsed slightly different whether we use protocol v1 or v2.
This will fix issue #113