Skip to content

log level propagation from mirror.py to Command #3009

Open
@vladak

Description

@vladak

Describe the bug
As I was debugging a case where the incoming check hung mirror.py for some reason for a project with number of Mercurial repositories (might be a subject of another bug to be filed) I noticed that even though I specified log level as DEBUG, the functions inside the Command class did not log expected output - as if the log level was still set default.

To Reproduce
run opengrok-mirror with -l DEBUG on a project

Expected behavior
logging in the Command class used by mirror.py should follow the log level, no matter if batch logging (-b) is set.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions