fix: decouple reading the serialport from handling the data #5737
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.
fixes: #5024
It seems that serialport v10 on Windows behaves differently than on Linux and older serialport versions on Windows - possibly lagging the event loop or something similar. After the upgrade, the state machine was sometimes still in the old state and hasn't progressed yet. This caused some message tests to use the old state and fail / consider the message unsolicited/unexpected.
After delaying the data handling using
setImmediate
, I can no longer reproduce the issue - so I hope this is actually fixed now.