-
Notifications
You must be signed in to change notification settings - Fork 72
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
Handle zero-length SYSEX messages #159
Conversation
Thanks, this is looking good. Just curious: Is there any reasonable use case where this happens? Or did you find this just based on a bug in the client library? |
De mémoire et en ayant jeté un oeil rapide, sauf erreur ce cas n'est pas possible. La fonction n'est appelée que lorqu'un message sysex complet est déjà dans le tampon. |
The actual issue was originally found via some fuzzing experiments I was doing. But I was envisioning an API like I had quick look through the other implementations, and the .NET IoT implementation does contain a similar
If the bytes _(J'ai dû recourir à Google Translate pour répondre, désolé si c'est difficile à comprendre), Si les octets |
There appears to be a compatibility issue with the ESP IDK 3.0. I need to look into that first. |
@mchesser Can you please rebase your PR? That should now fix the build. |
7ed06ad
to
acee726
Compare
Check that the `storedInputData` buffer is not empty before reading the command ID from the buffer. Fixes: firmata#151
acee726
to
96c7ed1
Compare
Rebased. |
Thanks again. Merged. |
Simple fix for #151. Check that the
storedInputData
buffer is not empty before reading the command ID from the buffer.