-
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
Address testing feedback from opcert callbacks, and re-commissioning #22369
Conversation
@chrisdecenzo For what it's worth, I think the right approach here at this stage to reduce risk in terms of the DeviceCommissioner changes might be for whatever consumers want the
While it might be good if the SDK provided more built-in support for doing this check, I think it's worth thinking a bit about how exactly that should work in a way that does not hurt the common commissioning case and does not change the default commissioning flow from the one that has been widely tested. (For example, maybe the Fabrics read should only happen in the actual error case when we get the |
All PRs require an issue to be accepted, please link an issue or mention it in the body using #<issue_id> |
I created #22525 to track work for making the already-on-fabric check happen by default (with a few suggestions for how best to do it). |
Co-authored-by: Restyled.io <[email protected]>
All PRs require an issue to be accepted, please link an issue or mention it in the body using #<issue_id> |
Fixes #22419 |
All PRs require an issue to be accepted, please link an issue or mention it in the body using #<issue_id> |
Fixes #22419 |
All PRs require an issue to be accepted, please link an issue or mention it in the body using #<issue_id> |
@@ -1997,7 +2055,8 @@ void DeviceCommissioner::PerformCommissioningStep(DeviceProxy * proxy, Commissio | |||
app::InteractionModelEngine * engine = app::InteractionModelEngine::GetInstance(); | |||
app::ReadPrepareParams readParams(proxy->GetSecureSession().Value()); | |||
|
|||
app::AttributePathParams readPaths[8]; | |||
// NOTE: this array cannot have more than 9 entries, since 9 is what the spec requires as a minimum on servers |
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.
This seems off: this says the spec requires a minimum but we use 9 as the maximum.
This needs revision.
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.
"client cannot send more than 9 since spec mandates 9 as minimum on the server side"
…roject-chip#22369) * Draft: address testing feedback from new opcert callbacks * temporary workaround to isolate a memory corruption * add check for existing fabric during commissioning, handle correctly on content app platform * address comments * address comments * address comments * Restyled by clang-format (project-chip#22524) Co-authored-by: Restyled.io <[email protected]> * address comments Co-authored-by: restyled-io[bot] <32688539+restyled-io[bot]@users.noreply.github.com> Co-authored-by: Restyled.io <[email protected]>
…roject-chip#22369) * Draft: address testing feedback from new opcert callbacks * temporary workaround to isolate a memory corruption * add check for existing fabric during commissioning, handle correctly on content app platform * address comments * address comments * address comments * Restyled by clang-format (project-chip#22524) Co-authored-by: Restyled.io <[email protected]> * address comments Co-authored-by: restyled-io[bot] <32688539+restyled-io[bot]@users.noreply.github.com> Co-authored-by: Restyled.io <[email protected]>
Problem
Change overview
Testing