Message.get_filename produces exception if the RFC2231 encoding is ill-formed

Ouverte
#61,571 8 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
backend

Piste de recherche

Start with the Message.get_filename behavior described in issue 17369 and review the attached collapse_rfc2231_value.patch and rfc2231_issue17369_in_progress.patch. Reproduce the failure using an ill-formed RFC2231 value and inspect the existing email handling around it. Done means the malformed value no longer produces an exception, with regression coverage for that case.

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

Description

stdlib topic-email type-bug
BPO 17369
Nosy @warsaw, @vstinner, @bitdancer, @karlcow
Files
  • collapse_rfc2231_value.patch
  • rfc2231_issue17369_in_progress.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 2013-03-06.22:25:40.309>
    labels = ['type-bug', 'expert-email']
    title = 'Message.get_filename produces exception if the RFC2231 encoding is ill-formed'
    updated_at = <Date 2019-07-29.11:49:58.757>
    user = 'https://github.com/bitdancer'
    

    bugs.python.org fields:

    activity = <Date 2019-07-29.11:49:58.757>
    actor = 'vstinner'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['email']
    creation = <Date 2013-03-06.22:25:40.309>
    creator = 'r.david.murray'
    dependencies = []
    files = ['29344', '29781']
    hgrepos = []
    issue_num = 17369
    keywords = ['patch']
    message_count = 8.0
    messages = ['183619', '183630', '183631', '183704', '186585', '210538', '210539', '348639']
    nosy_count = 6.0
    nosy_names = ['barry', 'vstinner', 'r.david.murray', 'karlcow', 'python-dev', 'Ankur.Ankan']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue17369'
    versions = []
    

    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.