-
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
fix: use mSystemState if systemState not passed in params #37451
base: master
Are you sure you want to change the base?
Conversation
PR #37451: Size comparison from 1348a8a to 45b53ae Full report (72 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
@j0tunn could you describe in the summary under what conditions we want to allow params to not initialize msystemstate? I am trying to determine if this "use mSystemState" is generally something desirable as it adds a dependency chain of "this works if and only if mSystemState was initialized before" so the API seems to be slightly more coupled. I would generally lean towards "enforce params must always contain a system state" however unsure what the actual use case is here. |
@andy31415 scenario I'm trying to implement is to split commissioner initialization into two phases:
The reason to do so is the necessity to retry Commissioner initialization is performed via DeviceControllerFactory::SetupCommissioner and So this PR just expands the API: you can pass |
Fallback to use current system state in case of calling
InitControllerNOCChain
without systemState parameter after controller initialization.Now program will crash. After this fix it will try to use initialized controller system state, or caller will get concrete error.
Testing
Manual testing