A failed publish job permanently blocks retrying the same package version

Abierto
  • ¿Algo no está bien?
#793 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #794 de @thomashoneyman — fusionado

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend-api-design

Línea de trabajo

Start with the duplicate publish-job check in app/src/App/Server/Router.purs, around lines 82–89, and trace how job status and publish payload are used. The report identifies failed completed jobs as blocking retries, but leaves open whether they should be requeued, excluded from duplicate detection, or compared by payload; clarify the intended behavior before making a change. Done means a corrected publish can be processed and the unrelated historical issue reference is addressed if in scope.

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

Descripción

I attempted to publish [email protected].

The original publish failed because its location used a monorepo subdir:

I moved the package to a standalone repository and updated the manifest:

The standalone repository's main branch and v0.2.0 tag both point to the corrected package.

However, retrying spago publish -p puppy-runtime returns the original failed job and prints its old logs. The corrected location is never processed.

The API appears to identify duplicate publish jobs only by package name and version, including completed failed jobs:

https://github.com/purescript/registry-dev/blob/master/app/src/App/Server/Router.purs#L82-L89

Could the failed job be removed or requeued so that [email protected] can be published from the corrected location?

More generally, should completed failed jobs be excluded from duplicate detection, or should a changed payload be allowed to create a new job?

One additional detail: the failure message says “See issue #16”, but registry-dev issue #16 is closed and concerns a different historical topic.

Lenguaje dominante
PureScript
Estrellas
95
Forks
79
Merge medio
16 h 13 min
PR fusionados (30 d)
14

Preparar el entorno

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 purescript/registry-dev

Todos los issues de purescript/registry-dev

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.