A failed publish job permanently blocks retrying the same package version
維護者通常 1 天內回覆
已經有一個關聯 PR 被合併了。
- #794 來自 @thomashoneyman —— 已合併
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
I attempted to publish [email protected].
The original publish failed because its location used a monorepo subdir:
- Job:
ea66babf-2a67-43c1-9810-1c7f52d95952 - Logs: https://www.purescript.org/registry-dev/#/jobs/ea66babf-2a67-43c1-9810-1c7f52d95952
- Original location:
katsujukou/puppy, subdirectorypuppy-runtime
I moved the package to a standalone repository and updated the manifest:
- New location: https://github.com/katsujukou/purescript-puppy-runtime
- Ref:
v0.2.0
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.
- 主要語言
- PureScript
- 星號
- 95
- 分支
- 79
- 平均合併
- 16 小時 13 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
purescript/registry-dev 的其他 Issue
-
難度 5/5 一週以上 新手友好度 22/100
purescript/registry-dev#804 · 9 則留言 ·
維護者通常 1 天內回覆
-
Implement search and versioned Prim docs for the new Pursuit可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#789 · 1 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉
purescript/registry-dev#750 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Deprecate creation of legacy package sets可能重新可做 @mikesol 於 68 天前認領，目前沒有進行中的 PR。 未關閉
purescript/registry-dev#745 · 5 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
ROCm/rocm-libraries#15866 ·
維護者通常 2 天內回覆
-
area: web
難度 2/5 1-3 小時 新手友好度 72/100
inabagumi/shinju-date#6823 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
-
ManageSieve proxy: a backend's NO/BYE greeting is skipped as a capability line and reported as EOF未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 82/100
dmtrKovalenko/odiff#191 ·