Skip to content

Conversation

@rlubos
Copy link
Contributor

@rlubos rlubos commented Nov 8, 2025

Consecutive resource instance name should be encoded regardless of whether timestamp is present or not.

Fixes #99088

Consecutive resource instance name should be encoded regardless of
whether timestamp is present or not.

Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
@rlubos rlubos added this to the v4.3.0 milestone Nov 8, 2025
@rlubos rlubos added the bug The issue is a bug, or the PR is fixing a bug label Nov 8, 2025
@zephyrbot zephyrbot requested a review from SeppoTakalo November 8, 2025 11:14
@rlubos
Copy link
Contributor Author

rlubos commented Nov 8, 2025

FYI @walzsi, please see the linked issue. I wanted to avoid reverting your changes, I think the proposed fix should work fine with timestamped resource instances as well, at least your tests pass.

@rlubos rlubos requested a review from jukkar November 8, 2025 11:15
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 8, 2025

@walzsi
Copy link
Contributor

walzsi commented Nov 10, 2025

FYI @walzsi, please see the linked issue. I wanted to avoid reverting your changes, I think the proposed fix should work fine with timestamped resource instances as well, at least your tests pass.

Looks good, maybe the case with multiple resource instances should also be included into the testcase.

@jhedberg jhedberg merged commit 3e537db into zephyrproject-rtos:main Nov 12, 2025
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: LWM2M bug The issue is a bug, or the PR is fixing a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LWM2M: reading /3 using CBOR SENML generate invalid content

6 participants