-
Notifications
You must be signed in to change notification settings - Fork 408
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
Raise CodecExpection if 2 node has the same Id for the same parent #429
Labels
bsserver
Impact LWM2M bootstrap server
client
Impact LWM2M client
new feature
New feature from LWM2M specification
server
Impact LWM2M server
Comments
sbernard31
added
bsserver
Impact LWM2M bootstrap server
client
Impact LWM2M client
new feature
New feature from LWM2M specification
server
Impact LWM2M server
labels
Nov 9, 2017
sbernard31
added a commit
that referenced
this issue
May 30, 2018
sbernard31
added a commit
that referenced
this issue
May 30, 2018
sbernard31
added a commit
that referenced
this issue
May 30, 2018
sbernard31
added a commit
that referenced
this issue
May 30, 2018
sbernard31
added a commit
that referenced
this issue
Jun 7, 2018
sbernard31
added a commit
that referenced
this issue
Jun 7, 2018
sbernard31
added a commit
that referenced
this issue
Jun 7, 2018
sbernard31
added a commit
that referenced
this issue
Jun 7, 2018
sbernard31
added a commit
that referenced
this issue
Jun 7, 2018
It should be fixed in master since #511 is integrated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bsserver
Impact LWM2M bootstrap server
client
Impact LWM2M client
new feature
New feature from LWM2M specification
server
Impact LWM2M server
a TLV (or JSON) payload could contain identifier conflict : 2 (or more) nodes with the same id for the same parent.
It that case Leshan just keep the last one and throw out the others silently.
We should raise a
CodecException
instead.This issue was fixed for TLV at resource instance level : #426.
But we should check resource and instance level for TLV (and maybe JSON...)
The text was updated successfully, but these errors were encountered: