Import: re-check an unknown import outcome once Studio can read the job again
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the unknown-outcome handling described in src/features/instance/databases/DESIGN.md and the import flow it covers, then see where get_job polling ends in the outcome. The open decisions are when a recheck runs (dialog or table open, or a background check) and how a recheck that finds no job keeps the outcome unknown. Done means a later successful read can replace unknown with completed or failed, and a miss never turns unknown into a failure. Confirm the cluster caveat with the maintainers before building it.
由索引模型根据 Issue 内容生成。
描述
What happens
After #1955, an import that Studio stops following ends as Outcome unknown. That covers five failed get_job polls in a row, the 10-minute deadline, and a job the polled node doesn't have. Studio says the import may still be running or may have finished, and points to the table and the Jobs tab.
One case in there is a real failure that Studio reports as unknown. The job reaches ERROR on the server between Studio's last good poll and the five failed ones. Studio never reads the ERROR, so it can't call the import failed. That part is by design: Studio can't report an outcome it never observed. #1955 records it in src/features/instance/databases/DESIGN.md.
Possible improvement
Once Studio can reach the instance again, it could check that job once more and replace the unknown outcome with the real one. It would say that the import completed, or that it failed with the job's message. That could happen the next time the import dialog or table is opened, or on a slow background check while the page stays open.
The catch: get_job reads only the node it reaches, because hdb_job doesn't replicate. So on a cluster, a recheck can miss the job just as the original polls did. A recheck that doesn't find the job should leave the outcome unknown, never turn it into a failure.
Low priority. The current outcome is honest, and the user is already told to check the table before importing again.
Review-Deferral: 1ebd2884610ec52c severity=nit category=correctness
Raised by the cross-model review of #1955 (#1939).
🤖 Generated by Anthropic Claude Code (Claude Opus 5.5); posted via @dawsontoth.
- 主要语言
- TypeScript
- 星标
- 5
- 派生
- 4
- 平均合并
- 1 天 12 小时
- 30 天内合并 PR
- 65
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HarperFast/studio 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
HarperFast/studio#2070 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
HarperFast/studio#2067 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
HarperFast/studio#2053 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
HarperFast/studio#2026 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
HarperFast/studio#2021 ·
维护者通常 1 天内回复
查看 HarperFast/studio 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 67/100
outline/outline#14529 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 86/100
g1331/phantom-circuit#93 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
compiler
难度 2/5 1-3 小时 新手友好度 74/100
HerringtonDarkholme/hd-lang#1699 ·
维护者通常 1 天内回复