-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[chip-tool] make discover commissionables return a list of all discovered devices instead of only one
#41545
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
base: master
Are you sure you want to change the base?
[chip-tool] make discover commissionables return a list of all discovered devices instead of only one
#41545
Conversation
|
PR #41545: Size comparison from c1f377d to d6003fe Full report (37 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, nxp, psoc6, qpg, realtek, stm32, telink)
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #41545 +/- ##
=======================================
Coverage 51.04% 51.04%
=======================================
Files 1384 1386 +2
Lines 100937 100956 +19
Branches 13059 13061 +2
=======================================
+ Hits 51521 51534 +13
- Misses 49416 49422 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
discover commissionables return a list of all discovered devices instead of only one
discover commissionables return a list of all discovered devices instead of only onediscover commissionables return a list of all discovered devices instead of only one
| LogErrorOnFailure(RemoteDataModelLogger::LogDiscoveredNodeData(nodeData)); | ||
|
|
||
| if (mDiscoverOnce.ValueOr(true)) | ||
| if (mDiscoverOnce.ValueOr(false)) |
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 is documented as defaulting to true, no?
As in, the documented behavior matches the implemented behavior. I am not sure where "Documentation of chip-tool mentions that it should mention all discovered commissionables" comes from. If it's from some sort of out-of-band documentation, that just means that documentation is wrong...
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.
- Yaa it is documented that it "defaults as true" in the Code, but here for example it mentions 'all matter commissionables':
connectedhomeip/docs/development_controllers/chip-tool/chip_tool_guide.md
Lines 892 to 896 in a343518
To discover all Matter commissionables available in the operation area, run the following command: ``` $ ./chip-tool discover commissionables
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.
Do you need it to be defaulted as True? as it seems incoherent with the even the name of the command commissionableS
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's possible the guide was written before this option was introduced; the dangers of out-of-band documentation. Like #25223 (thank you for finding that) explains, the option defaults to true to match the Python harness behavior, so that YAML and Python tests behave the same wrt discovery.
Summary
discover commissionablescommand only diplays one discovery result and then exitsTesting
CI Testing