python / python/cpython

BaseProxy cache should be cleaned when Manager client is reconnected

未关闭
#78,947 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

3.7 (EOL) stdlib topic-multiprocessing type-bug
主要语言
Python
星标
77.2k
派生
36k
PR 合并指标
PR 指标待抓取

描述

BPO 34766
Nosy @pitrou, @applio, @wynfred
PRs
  • python/cpython#9476
  • 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 2018-09-21.15:48:45.085>
    labels = ['3.7', 'type-bug', 'library']
    title = 'BaseProxy cache should be cleaned when Manager client is reconnected'
    updated_at = <Date 2019-05-06.19:54:38.686>
    user = 'https://github.com/wynfred'
    

    bugs.python.org fields:

    activity = <Date 2019-05-06.19:54:38.686>
    actor = 'wynfred'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2018-09-21.15:48:45.085>
    creator = 'wynfred'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 34766
    keywords = ['patch']
    message_count = 5.0
    messages = ['326388', '329480', '331765', '333896', '341631']
    nosy_count = 3.0
    nosy_names = ['pitrou', 'davin', 'wynfred']
    pr_nums = ['9476']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue34766'
    versions = ['Python 2.7', 'Python 3.6', 'Python 3.7']
    

    贡献指南

    打开贡献指南

    从这里开始

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

    调研方向

    从 issue 中提到的 BaseProxy 和 Manager 客户端重连路径开始,然后查看现有的 PR #9476 以了解之前的上下文。当 Manager 客户端重新连接时清理 BaseProxy 缓存,并通过审查期间确定的相关回归覆盖来验证该行为,即表示完成。

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

    评估

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

    把新 issue 发到你的邮箱

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