-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
[rfxcom] Convert unsigned byte to int properly #10830
Conversation
Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
ed2b47a
to
1fe3fb8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great thanks
Hey Martin, nice to see you're still on the project :) Do I need to do anything about the failing tests in another binding? I've got a few rfxcom changes queued and coming your way :) |
I only focus a bit on HEOS and RFXCom PR's and sometimes a small PR, I'm very busy with work and live in general :-)
I triggered a rebuild, let's see how it goes. |
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
…enhab#10830) Without this, any message over 127 bytes reports a negative length and fails the message start test, which puts the code out of sync with the rfxcom leading to lots of errors, and eventually, complete loss of connection. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
Without this, any message over 127 bytes reports a negative length and
fails the message start test, which puts the code out of sync with the
rfxcom leading to lots of errors, and eventually, complete loss of
connection.
Signed-off-by: James Hewitt james.hewitt@uk.ibm.com