-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Remove no-longer-used MTRDevice logic for truncating data version lists #34183
base: master
Are you sure you want to change the base?
Remove no-longer-used MTRDevice logic for truncating data version lists #34183
Conversation
After project-chip#34111, ReadClient handles this logic itself, so the attempted truncation in MTRDevice was now dead code.
PR #34183: Size comparison from ee0d96e to 493c5f8 Full report (27 builds for bl602, bl702, bl702l, cc32xx, linux, mbed, nrfconnect, nxp, qpg, stm32, tizen)
|
PR #34183: Size comparison from ee0d96e to aa4097a Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
@@ -403,6 +403,7 @@ CHIP_ERROR ReadClient::BuildDataVersionFilterList(DataVersionFilterIBs::Builder | |||
const Span<DataVersionFilter> & aDataVersionFilters, | |||
bool & aEncodedDataVersionList) | |||
{ | |||
ChipLogProgress(DataManagement, "Attempting to encode %lu data version filters", static_cast<unsigned long>(aDataVersionFilters.size())); |
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.
We could move this to the end so in either case we get one log statement saying how many we encoded
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.
The "we didn't encode everything" log statement logs how many were chopped off. Not that this is not trivially derivable from "how many we encoded" and "how many we were asked to encode", since we skip encoding the ones that don't match our request paths.....
After #34111, ReadClient handles this logic itself, so the attempted truncation in MTRDevice was now dead code.
REVIEW NOTE: A whitespace-ignoring diff might be simpler to review.