Mapper: a project's saved log was reduced to one entry, possibly by a log write before the log had loaded
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 34/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, react
调研方向
Start in oclmap MapProject.jsx, reading fetchAndSetProject, projectLog and postProjectLogs and checking where projectLogsLoadedRef is set and read. Reproduce by delaying the logs/ response and taking a logged action before it returns. The fix also touches oclapi2 MapProjectLogsView.create. Done when a logged action taken before the load never removes saved project or row log entries, and its own entry survives the load.
由索引模型根据 Issue 内容生成。
描述
On staging on 2026-11-02 (Mapper 1.0.44), after AutoMatch and decisions, a project that was reopened and downloaded as CSV about a second later had only the downloaded entry in its saved log. Seen once; a rerun kept its entries. Found by the weekly staging run (OpenConceptLab/ocl_online#445).
Suspected cause, from reading the code; not reproduced. Opening a project loads logs/ in the background, but projectLog() doesn't wait for it: it POSTs the whole log as it has it so far, and the API replaces what's stored. The same POST carries the row logs, so they would be lost too.
Acceptance criteria
- Reproduce it by delaying the
logs/response and taking a logged action, or show the cause is something else. - A logged action taken before
logs/has loaded never removes saved project or row log entries. - That action's own entry is kept once the log has loaded.
Components: oclmap MapProject.jsx (fetchAndSetProject, projectLog, postProjectLogs; projectLogsLoadedRef already tracks the load) and oclapi2 MapProjectLogsView.create. Two ways to fix it: hold log writes until the load finishes, or have the API append.
- 主要语言
- 没有语言数据
- 星标
- 4
- 派生
- 2
- 平均合并
- 2 小时 12 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenConceptLab/ocl_issues 的其他 Issue
-
component/fhir type/bug
难度 2/5 1-3 小时 新手友好度 82/100
OpenConceptLab/ocl_issues#3026 ·
-
component/api decision/human-review signal/needs-access signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 72/100
OpenConceptLab/ocl_issues#3012 · 2 条评论 ·
-
component/design-system decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/docs
难度 2/5 半天 新手友好度 70/100
OpenConceptLab/ocl_issues#2983 · 1 条评论 ·
-
component/mapper decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 78/100
OpenConceptLab/ocl_issues#2966 · 2 条评论 ·
-
component/mapper component/web decision/human-review signal/low-risk signal/needs-human signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 76/100
OpenConceptLab/ocl_issues#2920 · 1 条评论 ·
查看 OpenConceptLab/ocl_issues 的全部 Issue
相似的 Issue
-
needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
coder/claudecode.nvim#587 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
digitalbazaar/http-client#60 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
fivetran/dbt_recurly#55 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
topmonks/hlidac-shopu#3687 ·
维护者通常 1 天内回复
-
bug lane: fast
难度 2/5 1-3 小时 新手友好度 76/100
unicef/adt-studio#1109 ·
维护者通常 2 天内回复