Skip to content

Log level in subsection is not honored #15170

Closed
@Elbandi

Description

@Elbandi
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/enhancementAn improvement of existing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions