Skip to content
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

Log level in subsection is not honored #15170

Closed
2 of 6 tasks
Elbandi opened this issue Mar 26, 2021 · 0 comments · Fixed by #15176
Closed
2 of 6 tasks

Log level in subsection is not honored #15170

Elbandi opened this issue Mar 26, 2021 · 0 comments · Fixed by #15176
Labels
type/enhancement An improvement of existing functionality
Milestone

Comments

@Elbandi
Copy link

Elbandi commented Mar 26, 2021

  • Gitea version (or commit ref): 1.13.6 (release)
  • Git version: 2.17.1
  • Operating system: Ubuntu bionic LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No : no api issue
  • Log gist:
    no

Description

If there is an empty LEVEL parameter in log.* section, the main log level is not honored.
This is the app.ini setttings:

[log]
ROOT_PATH =
; Either "console", "file", "conn", "smtp" or "database", default is "console"
; Use comma to separate multiple modes, e.g. "console, file"
MODE = console
; Either "Trace", "Debug", "Info", "Warn", "Error", "Critical", default is "Trace"
LEVEL = Trace

[log.console]
LEVEL =
STDERR = false

In this case only >INFO logs are displayed. because missing value is use the default info level. if no LEVEL in log.console, trace is active.

If this is a normal behavior, it sould be documented. and in the example config all sub log section have LEVEL, so the [log] LEVEL settings are ignored.

@6543 6543 added type/bug type/enhancement An improvement of existing functionality and removed type/bug labels Mar 28, 2021
@6543 6543 added this to the 1.15.0 milestone Mar 28, 2021
@go-gitea go-gitea locked and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants