A failed publish job permanently blocks retrying the same package version

Ouverte
  • Quelque chose ne va pas ?
#793 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Une pull request liée a déjà été fusionnée.

  • #794 par @thomashoneyman — fusionnée

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Domaine
backend-api-design

Piste de recherche

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.

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

Description

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.

Langage dominant
PureScript
Étoiles
95
Forks
79
Merge moyen
16 h 13 min
PR mergées (30 j)
14

Préparer son environnement

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

Toutes les issues de purescript/registry-dev

Issues similaires

Plus d'issues Backend & API Design

Recevez les nouvelles issues par e-mail

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