fix: implement self-healing fallback parser for buffer size misalignment#3
Merged
Conversation
When the ZK device returns CMD_PREPARE_DATA with a size at offset 0 but with trailing garbage bytes (making the payload length >= 5), the parser incorrectly shifts and reads the size at offset 1. This causes the size parsing to fail with "Buffered response size exceeds maximum". We implement a robust, self-healing parser that tries offset 1 first (standard), and automatically falls back to offset 0 if the parsed size at offset 1 is invalid (exceeds MAX_RESPONSE_SIZE) while offset 0 is valid. Added integration test `test_prepare_buffer_offset_misalignment_tcp` to verify this behavior.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
fix: implement self-healing fallback parser for buffer size misalignment
When the ZK device returns CMD_PREPARE_DATA with a size at offset 0 but with trailing garbage bytes (making the payload length >= 5), the parser incorrectly shifts and reads the size at offset 1. This causes the size parsing to fail with "Buffered response size exceeds maximum".
We implement a robust, self-healing parser that tries offset 1 first (standard), and automatically falls back to offset 0 if the parsed size at offset 1 is invalid (exceeds MAX_RESPONSE_SIZE) while offset 0 is valid. Added integration test
test_prepare_buffer_offset_misalignment_tcpto verify this behavior.