samples: settings: handle failures #94898
Open
+8
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JarmouniA
reviewed
Aug 23, 2025
If we cannot initialize settings subsystem, it does not make much sense to do calls into it. This leads to uninitialized variables being printed and generally makes it hard to tell whether or not the sample runs with the given config. Signed-off-by: Dmitrii Sharshakov <[email protected]>
dsseng
force-pushed
the
settings-sample-err-handling
branch
from
931e3ea to
32b4670
Compare
JarmouniA
approved these changes
Aug 23, 2025
|
kartben
approved these changes
Aug 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we cannot initialize settings subsystem, it does not make
much sense to do calls into it. This leads to uninitialized
variables being printed and generally makes it hard to tell whether
or not the sample runs with the given config.
Signed-off-by: Dmitrii Sharshakov [email protected]