-
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
Ensure that all Fabric-scoped commands respond with UNSUPPORTED_ACCESS if there is no accessing fabric #20811
Comments
Oh, and ideally this would be enforced in IM, but we don't have a way to annotate commands as fabric-scoped in XML right now. Maybe we should just add one and do this in IM, the same way we handle timed invoke. |
Example of current failure:
|
Assigning to @bzbarsky-apple to do the code-gen bits for the table once ZAP has the support (project-chip/zap#609) |
Cert Blocker Review: Moving this 1.1, given the current SDK is conformant with the spec, and we can live with the hardcoded version for now. |
…) (#21047) Fixes #20811 Co-authored-by: Boris Zbarsky <[email protected]>
Problem
We have some fabric-scoped commands (e.g. UpdateFabricLabel) that are not following the spec, which says:
and are returning some other responses instead.
Some of the test plans may in fact be expecting those other responses, hence the cert blocker bit....
Proposed Solution
Audit and fix. The relevant set of commands looks like the following (git grep run in the spec repo):
The text was updated successfully, but these errors were encountered: