Coverage uploads report repository deactivated, but settings show it as active
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions
- Área
- devtools
Línea de trabajo
Start by comparing the repository’s General settings page with the upload-service response for libmir/mir-stat; the issue does not identify Codecov source files or tests. Reproduce or trace the deactivation state across those two paths, then confirm that an active repository accepts uploads or that a deactivated one exposes a way to reactivate it.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Coverage uploads for libmir/mir-stat are being rejected because Codecov reports that the repository is deactivated. However, the repository’s General settings page offers a Deactivate option, with no Activate option.
Could you check whether the repository’s activation state is inconsistent between the settings UI and the upload service?
Error
The original GitHub Actions logs from November 11, 2026 contain:
Upload queued for processing failed: {"message":"This repository is deactivated. To resume uploading to it, please activate the repository in the Codecov UI: https://app.codecov.io/github/libmir/mir-stat/config/general"}
The upload action then exits with code 1.
Affected repository and run
- Repository: https://github.com/libmir/mir-stat
- Codecov settings: https://app.codecov.io/github/libmir/mir-stat/config/general
- Pull request: https://github.com/libmir/mir-stat/pull/273
- Workflow run: https://github.com/libmir/mir-stat/actions/runs/43109420912
- Original failed upload step: https://github.com/libmir/mir-stat/actions/runs/43109420912/job/130821262079#step:16:1
- Failed rerun example: https://github.com/libmir/mir-stat/actions/runs/43109420912/job/130896667538
What we checked
- Tests and coverage-report generation passed.
- Coverage uploads failed across Linux and Windows jobs.
- The settings page appears to show the repository as active.
- Rerunning the failed jobs did not resolve the upload failures. We have confirmed failures at the upload steps, but have not yet verified the detailed error text from the latest attempt.
Expected behavior
An active repository should accept coverage uploads. If it is actually deactivated, the settings page should accurately show that state and provide a way to reactivate it.
Please advise whether this requires a correction on Codecov’s side or an additional configuration change.
AI-Assisted-By: Codex (GPT-6 Astra Medium)
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 52
- Forks
- 25
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de codecov/feedback
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePosiblemente ocupada @ChiptenIsCool la tomó hace 16 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Docs Waiting for: Product Owner
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
-
Dificultad 4/5 1-2 días Aptitud para principiantes 42/100
Todos los issues de codecov/feedback
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
daniel-ospina/tortoise#14235 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
5hyuns/maya-workflow-kit-for-blender#439 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue priority:p2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
mobeloper/better-oss#29 ·
-
extension help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
nightgauge/nightgauge#3480 ·
Los mantenedores suelen responder en 1 día