python / python/cpython

Deadlock in logging.config.dictConfig

Open
#84,551 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) stdlib
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 40371
Nosy @marcogiusti
Files
  • deadlock_logging.log: The thread tracebacks
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2020-04-23.07:19:46.520>
    labels = ['3.7', 'library']
    title = 'Deadlock in logging.config.dictConfig'
    updated_at = <Date 2020-04-23.07:19:46.520>
    user = 'https://github.com/marcogiusti'
    

    bugs.python.org fields:

    activity = <Date 2020-04-23.07:19:46.520>
    actor = 'mrc'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2020-04-23.07:19:46.520>
    creator = 'mrc'
    dependencies = []
    files = ['49088']
    hgrepos = []
    issue_num = 40371
    keywords = []
    message_count = 1.0
    messages = ['367085']
    nosy_count = 1.0
    nosy_names = ['mrc']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue40371'
    versions = ['Python 3.7']
    

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    Research direction

    Start by reading the attached deadlock_logging.log traceback and inspecting logging.config.dictConfig in the Python standard library. Reproduce the deadlock if possible, then trace the involved logging and configuration locks. Done means the reported deadlock is prevented and a regression test covers the scenario.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    backend
    Issue type
    Bug
    Difficulty
    4/5
    Estimated time
    3-5 days
    Activity status
    Stale
    Clarity
    Needs clarification
    Newbie friendliness
    25/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.