You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PICS tool reporting "Duplicate dependency item found, only the first item will be evaluated".
Is this some kind of problem in the supplied PICS file? If so, is there a feedback mechanism from the pics tool maintainers to the folks generating the PICS XML that could help ID these?
But beyond that, if you just go into the tool and load ex. only the network commissioning test cluster plan, then select ONLY the thread feature (not CNET.S, and not MCORE.COM.THR because it's not loaded), then validate the PICS, it only shows warnings and no errors.
Steps to reproduce the behavior
Load Network Commissioning Cluster Test Plan.xml into the pics tool
select only CNET.S.F01
validate PICS
see no error
Expected behavior
No response
Log files
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
It is a warning because CNET.S is optional and was not selected: so selection of this dependent element is ambiguous at best (to which I agree it could be an error in this case).
Describe the bug
PICS tool reporting "Duplicate dependency item found, only the first item will be evaluated".
Is this some kind of problem in the supplied PICS file? If so, is there a feedback mechanism from the pics tool maintainers to the folks generating the PICS XML that could help ID these?
But beyond that, if you just go into the tool and load ex. only the network commissioning test cluster plan, then select ONLY the thread feature (not CNET.S, and not MCORE.COM.THR because it's not loaded), then validate the PICS, it only shows warnings and no errors.
Steps to reproduce the behavior
Expected behavior
No response
Log files
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: