Fixed #16815: Avoids potential error when settings table is empty #16865
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
Updates the Kernel to use the null-safe operator when accessing the alerts_enabled setting. This prevents a potential error if the settings object is null.
snipe
changed the title
Member
|
Awesome, ty! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds a null safe operator to
app/Console/Kernal.php.I was having the same issue as #16815 on a fresh install of Snipe-IT using docker.
The schedule is trying to access
alerts_enabledfrom theSettingmodel but on a fresh install it doesn't exist yet.