Improve reporting of broken stdout pipe during interpreter shutdown

Ouverte
#55,589 16 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
python
Domaine
operating-systems

Piste de recherche

Start by reviewing python-sigint_and_epipe_straces.txt and flush_stdout_at_shutdown.patch, the historical evidence and proposed change attached to this issue. Determine the current interpreter-shutdown behavior for a broken stdout pipe and define improved reporting before validating the result with an appropriate regression test.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

topic-IO type-bug
BPO 11380
Nosy @terryjreedy, @ncoghlan, @pitrou, @rbtcollins, @florentx, @vadmium
Files
  • python-sigint_and_epipe_straces.txt: strace of issue in 3.2.2, 3.1.2, and 2.5.2
  • flush_stdout_at_shutdown.patch
    		•

    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 2011-03-03.01:32:45.546>
labels = ['type-bug', 'expert-IO']
title = 'Improve reporting of broken stdout pipe during interpreter shutdown'
updated_at = <Date 2018-06-16.10:13:08.003>
user = 'https://bugs.python.org/ulidtko'

    bugs.python.org fields:

    activity = <Date 2018-06-16.10:13:08.003>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2011-03-03.01:32:45.546>
creator = 'ulidtko'
dependencies = []
files = ['24517', '31853']
hgrepos = []
issue_num = 11380
keywords = ['patch']
message_count = 16.0
messages = ['129930', '130083', '153320', '198316', '198332', '198338', '198339', '198345', '198347', '198349', '213109', '248574', '248579', '248625', '248626', '319729']
nosy_count = 11.0
nosy_names = ['terry.reedy', 'ncoghlan', 'pitrou', 'rbcollins', 'zzzeek', 'flox', 'ulidtko', 'martin.panter', 'Jeremy.Fishman', 'daumiller', 'Christopher.Heiny']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11380'
versions = ['Python 2.7']

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.