-
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
[ESP32] Removed Redundant VerifyOrReturn Statement from GetLogForIntent() in DiagnosticLogsProviderDelegate #36952
base: master
Are you sure you want to change the base?
Conversation
PR #36952: Size comparison from 1b4c56c to b3d7d7c Full report (19 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, nrfconnect, qpg, stm32, tizen)
|
b3d7d7c
to
2a0c268
Compare
PR #36952: Size comparison from 1b4c56c to 2a0c268 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
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.
Looks good, but a question about EndLogCollection. When called with a non-successful second argument, it returns failure in this file, right? Is that allowed? Expected? The API documentation for the new EndLogCollection overload does not say what the return value means when EndLogCollection is called with an error....
Problem
The VerifyOrReturn statement after the CollectLog() method caused an early return in case of an error, preventing EndLogCollection() from being called. This behavior is incorrect, as EndLogCollection() must be called in both success and failure scenarios.
Change Overview
Removed the VerifyOrReturn statement following the CollectLog() method.
Modified the code to ensure that EndLogCollection() is called regardless of the success or failure of CollectLog().