python / python/cpython

Broken Pipe in Server of Manager in multiprocessing when finalizing, sometimes

未關閉
#88,780 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

3.9 (EOL) stdlib topic-multiprocessing type-bug
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

BPO 44614
Nosy @markshannon, @mutax
Files
  • race2.py
  • 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 2021-07-12.22:07:45.419>
    labels = ['type-bug', 'library', '3.9']
    title = 'Broken Pipe in Server of Manager in multiprocessing when finalizing, sometimes'
    updated_at = <Date 2021-07-13.13:25:37.945>
    user = 'https://github.com/mutax'
    

    bugs.python.org fields:

    activity = <Date 2021-07-13.13:25:37.945>
    actor = 'Mark.Shannon'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2021-07-12.22:07:45.419>
    creator = 'mutax'
    dependencies = []
    files = ['50145']
    hgrepos = []
    issue_num = 44614
    keywords = ['patch']
    message_count = 1.0
    messages = ['397358']
    nosy_count = 2.0
    nosy_names = ['Mark.Shannon', 'mutax']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue44614'
    versions = ['Python 3.9']
    

    貢獻指南

    開啟貢獻指南

    從這裡開始

    1. 先讀完整個 Issue,再讀專案的貢獻指南。
    2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
    3. Fork 儲存庫,在一個分支上完成修改。
    4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

    研究方向

    從上傳的重現檔案 race2.py 開始,在 finalization 期間針對 multiprocessing Manager server 執行它,以觀察間歇性的 BrokenPipeError。追蹤 Manager server 的 finalization 路徑,並找出關閉或使用 pipe 的條件;完成標準是重現程式在 finalization 期間不再回報 broken pipe。

    由索引模型根據 Issue 內容生成。

    評估

    技術堆疊
    python
    領域
    distributed-systems
    Issue 類型
    缺陷
    難度
    4/5
    預估耗時
    3-5 天
    活躍度
    停滯
    描述清晰度
    需要釐清
    新手友好度
    25/100

    把新 issue 寄到你的電子郵件信箱

    精選適合新手參與的 GitHub issue 摘要。