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 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#789 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭
purescript/registry-dev#750 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Deprecate creation of legacy package sets可能重新可做 @mikesol 于 67 天前认领，目前没有进行中的 PR。 未关闭
purescript/registry-dev#745 · 5 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
难度 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 天内回复
-
Mend: dependency security vulnerability
难度 2/5 1-3 小时 新手友好度 65/100
-
Mend: dependency security vulnerability
难度 2/5 1-3 小时 新手友好度 62/100
ManageIQ/manageiq-pods#1476 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
prime-radiant-inc/evener#6366 ·
维护者通常 1 天内回复