-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Allow null lists when writing access control cluster ACL entries #13089
Allow null lists when writing access control cluster ACL entries #13089
Conversation
When access control cluster is decoding TLV to write entries, if subjects or targets are explicitly null, treat them as empty lists.
Attn @harimau-qirex |
PR #13089: Size comparison from 8e40abc to d4d4099 Increases (3 builds for esp32, p6)
Full report (31 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Also, why wasn't this caught by yaml tests? Do we not have CI test coverage for this? We should. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving just so you're not blocked, but this should really have yaml tests that exercise this stuff...
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
PR #13089: Size comparison from 19f61eb to ef32aab Increases (1 build for p6)
Full report (30 builds for efr32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Just merged in master and confirmed this still works. Would like to get this in as it makes using the REPL easier, even though yes I will still continue to improve serialization to hopefully use more generated code. |
@mlepage-google I approved, but:
|
When access control cluster is decoding TLV to write entries, if subjects or targets are explicitly null, treat them as empty lists.
When access control cluster is decoding TLV to write entries, if subjects or targets are explicitly null, treat them as empty lists.
Problem
Can't omit subjects or targets in chip-repl, when writing access control cluster ACL entries,
because those fields are sent with explicit null value, and decode expects a value to be an array/list.
Change overview
When decoding subjects or targets, check for explicit null value and treat it as an empty array/list.
Testing
Tested in chip-repl.