Fix: Handle encoded CBOR message exceeding buffer size #152
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.
Currently the payload buffer for CBOR encoded messages has a size of 256 bytes. If the encoded cbor message is exceeding this max payload size then the whole message is discarded. This PR should fix this problem by encoding properties until the payload buffer is full and encoding the remaining properties on the next run of
CBOREncoder::encode
.