A failed publish job permanently blocks retrying the same package version

Offen
  • Stimmt etwas nicht?
#793 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Ein zugehöriger Pull Request wurde bereits gemerged.

  • #794 von @thomashoneyman — gemerged

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
backend-api-design

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
PureScript
Sterne
95
Forks
79
Ø Merge
16 Std. 13 Min.
Gemergte PRs (30 T.)
14

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus purescript/registry-dev

Alle Issues in purescript/registry-dev

Ähnliche Issues

Weitere Issues zu Backend & API Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.