create can leave a page that nothing on disk names
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in cmd/create/create.go at reserveOne, then trace CreatePage, os.WriteFile, persistToManifest, and failKeepingPage. Compare the recovery and failure paths and confirm the chosen behavior with maintainers; done means a failed reservation cannot leave an unrecorded page, or provides an exact actionable recovery record.
由索引模型根据 Issue 内容生成。
描述
create can leave a page in Confluence that nothing on disk names.
In the reserve phase, reserveOne (cmd/create/create.go) calls CreatePage and only then records the new page_id. It records it in one of two places: the file's frontmatter (os.WriteFile) or a pages: entry in markfluence.yaml (persistToManifest). If that write fails, the page already exists. Examples are a read-only .md file, a read-only markfluence.yaml, or a manifest write that gives up after its one retry.
failKeepingPage keeps the id and URL in the command's result, so the run's own output is the only record. A second create makes a second page, because nothing says the first one exists. update cannot pick it up either, because nothing names the page.
This is the one case in create's partial-failure story that update cannot recover from. The other two recover:
- A network failure during publish leaves a stub whose id is already on disk, so
updatefinishes it. - An unreadable attachment fails the same way, after the id is on disk.
Options:
- Check that the destination is writable before
CreatePage. This is cheap, but it races: the check can pass and the write can still fail. - Write first, create second. Reserve a placeholder on disk, create the page, then fill in the id. A failure then leaves a local marker instead of a remote orphan.
- Make the failure loud and actionable. For example, print the exact frontmatter line or manifest entry to add by hand, and give it an exit code a script can recognize.
- 主要语言
- Go
- 星标
- 4
- 派生
- 1
- 平均合并
- 1 小时 35 分钟
- 30 天内合并 PR
- 39
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
mozilla/markfluence 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
mozilla/markfluence#216 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 76/100
mozilla/markfluence#214 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
mozilla/markfluence#213 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 48/100
mozilla/markfluence#210 ·
维护者通常 1 天内回复
-
documentation
难度 5/5 一周以上 新手友好度 25/100
mozilla/markfluence#209 ·
维护者通常 1 天内回复
查看 mozilla/markfluence 的全部 Issue
相似的 Issue
-
documentation priority:p1
难度 2/5 1-3 小时 新手友好度 78/100
yeixio/toskar-core#697 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
keyxmakerx/Chronicle#1532 ·
维护者通常 1 天内回复
-
The acquisition fixture's search path skips the argument table production enforces (regression from #285)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
Judgment-Pack/judgment-pack-gateway#293 ·
维护者通常 1 天内回复
-
bug desktop v3 windows
难度 2/5 1-3 小时 新手友好度 65/100
esengine/DeepSeek-Reasonix#13697 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue help wanted
难度 1/5 1 小时以内 新手友好度 95/100
eugenioenko/ttt#959 ·
维护者通常 1 天内回复