Unchecked return value of I/O functions

Abierto
#60,152 19 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
c, python

Línea de trabajo

Start by reviewing issue15948__cursesmodule.patch and unchecked_return_values.patch, then inspect the dependency involving Modules/mmapmodule.c. Determine which unchecked I/O return values remain in scope and verify that each is handled consistently; done means the affected checks are covered and the relevant CPython tests pass.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

extension-modules type-bug
BPO 15948
Nosy @jcea, @vstinner, @tiran, @ezio-melotti, @socketpair, @felipecruz, @berkerpeksag, @serhiy-storchaka
Dependencies
  • bpo-23860: Windows: Failure to check return value from lseek() in Modules/mmapmodule.c
  • bpo-23878: Missing sanity checks for various C library function calls...
  • Files
  • issue15948__cursesmodule.patch
  • unchecked_return_values.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 2012-09-15.15:29:06.752>
    labels = ['type-bug']
    title = 'Unchecked return value of I/O functions'
    updated_at = <Date 2016-03-07.10:54:24.761>
    user = 'https://github.com/tiran'
    

    bugs.python.org fields:

    activity = <Date 2016-03-07.10:54:24.761>
    actor = 'socketpair'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2012-09-15.15:29:06.752>
    creator = 'christian.heimes'
    dependencies = ['23860', '23878']
    files = ['27692', '28253']
    hgrepos = []
    issue_num = 15948
    keywords = ['patch']
    message_count = 17.0
    messages = ['170521', '170540', '170541', '173662', '173663', '173664', '173668', '174089', '177140', '178577', '179584', '179586', '179597', '179598', '179602', '179603', '261294']
    nosy_count = 10.0
    nosy_names = ['jcea', 'vstinner', 'christian.heimes', 'ezio.melotti', 'socketpair', 'felipecruz', 'jcon', 'berker.peksag', 'serhiy.storchaka', 'mrshu']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue15948'
    versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']
    

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.