python / python/cpython

subprocess.communicate with timeout 0 and already terminated process generates TimeoutExpired on Linux

未关闭
#73,658 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

stdlib topic-subprocess type-bug
主要语言
Python
星标
77.2k
派生
36k
平均合并
1 天 9 小时
30 天内合并 PR
558

描述

BPO 29472
Nosy @Griffon26, @spoorcc
Files
  • test.py: A minimal example that shows the problem
  • 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 2017-02-07.11:57:14.624>
    labels = ['type-bug', 'library']
    title = 'subprocess.communicate with timeout 0 and already terminated process generates TimeoutExpired on Linux'
    updated_at = <Date 2017-02-07.12:36:53.465>
    user = 'https://github.com/Griffon26'
    

    bugs.python.org fields:

    activity = <Date 2017-02-07.12:36:53.465>
    actor = 'spoorcc'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2017-02-07.11:57:14.624>
    creator = 'Griffon26'
    dependencies = []
    files = ['46557']
    hgrepos = []
    issue_num = 29472
    keywords = []
    message_count = 1.0
    messages = ['287230']
    nosy_count = 2.0
    nosy_names = ['Griffon26', 'spoorcc']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue29472'
    versions = ['Python 3.6']
    

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue,再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库,在一个分支上完成修改。
    4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

    调研方向

    首先在 Linux 上运行 test.py 中的最小复现,并检查 subprocess.communicate 如何处理已终止进程的 timeout=0。完成的标准是此情况不再引发 TimeoutExpired,同时保留对尚未终止进程的预期 timeout 行为。

    由索引模型根据 Issue 内容生成。

    评估

    技术栈
    python
    领域
    operating-systems
    Issue 类型
    缺陷
    难度
    3/5
    预计耗时
    1-2 天
    活跃度
    停滞
    描述清晰度
    基本清楚
    新手友好度
    35/100

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。