hlx6: Require target revision precondition for atomic version fidelity
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- git, javascript
调研方向
The payload names no source files, tests or entry points, so there is no obvious first file to open. The issue is a child of tracking issue #323 and depends on a separate delivery/ordering design (item 1) and on fixing project permissions. Done would mean specified revision fidelity, ordering, retry and duplicate handling, with tests for rapid and reordered edits. Confirm the design with the maintainers before starting.
由索引模型根据 Issue 内容生成。
描述
Remaining follow-up after #336
#336 shipped best-effort VERSION verification in v1.16.1: capture the immutable DA snapshot, compare target content before creating a version, and verify the returned saved version afterwards. Missing snapshots, content mismatches and unexpected locations are explicit failures with recovery evidence. Unknown mutation outcomes are not blindly retried.
Unresolved limitation
The target VERSION endpoint does not accept a caller revision precondition. A concurrent target edit between the preflight GET and VERSION POST can therefore create an incorrect historical version. Postflight verification can detect the mismatch but cannot prevent or undo it. Raw content transformations can also cause conservative verification failures.
Remaining work
- Coordinate target API support in adobe/helix-api-service for conditional version creation tied to the revision/content verified by the caller.
- Wire the supported precondition into DA and explicitly handle precondition failures without blindly repeating an uncertain version creation.
- Test an edit between preflight verification and VERSION creation: no incorrect historical snapshot should be created or reported as successful.
- Define comparison semantics for transformed HTML and retain existing diagnostic/recovery evidence.
This is a forward-looking correctness follow-up, not a request to replay historical failures. The user reported manual cleanup completed on 2026-11-05; that does not resolve this concurrency limitation. Original investigation and scope decisions remain in #323 and its history.
- 主要语言
- JavaScript
- 星标
- 6
- 派生
- 18
- 平均合并
- 9 小时 30 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
adobe/da-admin 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
相似的 Issue
-
Administration: required plugin configuration field stays invalid after restoring its saved value未关闭needs-triage Platform(Default)
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
nearform/ag-grid-url-sync#314 · 1 个 reaction ·
维护者通常 1 天内回复
-
chore
难度 2/5 1-3 小时 新手友好度 74/100
idean3885/claude-ops-agent#910 ·
维护者通常 1 天内回复
-
S: triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
oskarrough/agent-ide#29 · 1 条评论 ·
维护者通常 1 天内回复