python / python/cpython

IO streams locking can be broken after fork() with threads

未關閉
#84,579 9 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

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

描述

BPO 40399
Nosy @pitrou, @Delgan
Files
  • bug.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 2020-04-26.16:58:22.058>
    labels = ['3.8', 'type-bug', 'library', '3.9']
    title = 'IO streams locking can be broken after fork() with threads'
    updated_at = <Date 2020-04-29.16:43:20.805>
    user = 'https://github.com/Delgan'
    

    bugs.python.org fields:

    activity = <Date 2020-04-29.16:43:20.805>
    actor = 'pitrou'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2020-04-26.16:58:22.058>
    creator = 'Delgan'
    dependencies = []
    files = ['49094']
    hgrepos = []
    issue_num = 40399
    keywords = []
    message_count = 8.0
    messages = ['367317', '367509', '367510', '367516', '367522', '367525', '367674', '367675']
    nosy_count = 2.0
    nosy_names = ['pitrou', 'Delgan']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue40399'
    versions = ['Python 3.8', 'Python 3.9']
    

    Linked PRs
    • gh-128591

    貢獻指南

    開啟貢獻指南

    從這裡開始

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

    研究方向

    先檢查上傳的 bug.py 重現程式和連結的 PR gh-128591,接著追蹤 fork() 與執行緒相關的 CPython IO 串流行為。確認回報的鎖定失敗,並根據 PR 的目前狀態判斷還剩下什麼;完成的標準是該重現不再失敗,且具備適當的回歸測試涵蓋率。

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

    評估

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

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

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