fix: don't assume new log_level setting was defaulted#831
Merged
jaredhendrickson13 merged 1 commit intomasterfrom Jan 19, 2026
Merged
fix: don't assume new log_level setting was defaulted#831jaredhendrickson13 merged 1 commit intomasterfrom
jaredhendrickson13 merged 1 commit intomasterfrom
Conversation
This was
linked to
issues
Jan 19, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes
log_levelwas not assigned its default as expected on some installs HTTP 500 Error on GET /api/v2/firewall/aliases - Undefined constant #829 Installing 2.7.0 results in "HTTP code 500" in API #830