-
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
[Group] Remove TODO #15650
[Group] Remove TODO #15650
Conversation
@@ -42,10 +42,11 @@ CHIP_ERROR ClusterBase::Associate(DeviceProxy * device, EndpointId endpoint) | |||
return err; | |||
} | |||
|
|||
/** | |||
* To be used in a test context where a SecureSession is already present | |||
*/ | |||
CHIP_ERROR ClusterBase::AssociateWithGroup(DeviceProxy * device, GroupId groupId) |
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.
So this function cannot be used outside of a YAML context? What's the plan to enable this in chip-tool?
If I'm reading the current logic correctly, it requires mDevice
to always have a valid secure session ahead of time to permit using it in a group setting, which is an odd pre-requisite.
This is all because mDevice is starting out pointing to a unicast destination - why can't it start out pointing to a groupcast destination instead?
PR #15650: Size comparison from 7421db3 to b374d91 Increases above 0.2%:
Increases (1 build for nrfconnect)
Full report (31 builds for cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
@@ -42,10 +42,11 @@ CHIP_ERROR ClusterBase::Associate(DeviceProxy * device, EndpointId endpoint) | |||
return err; | |||
} | |||
|
|||
/** | |||
* To be used in a test context where a SecureSession is already present | |||
*/ | |||
CHIP_ERROR ClusterBase::AssociateWithGroup(DeviceProxy * device, GroupId groupId) |
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.
It seems like the right fix should be to change AssociateWithGroup to take the args relevant to a group and not take a DeviceProxy at all.... We should not be creating separate APIs/codepaths for tests vs non-tests if we can avoid it.
Closing for now |
Problem
fix #11850
Change overview
Removed TODO since changes are not needed.
Testing
Not Tested, comments only.