Skip to content

Requeue a job inline when its status write-back fails (#1106) - #1208

Closed
rollroyces wants to merge 5 commits into
deeplethe:devfrom
rollroyces:fix/jobs-write-back-fallback
Closed

rollroyces wants to merge 5 commits into
deeplethe:devfrom
rollroyces:fix/jobs-write-back-fallback

Conversation

@rollroyces

@rollroyces rollroyces commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Closing this PR — its base is the local fork's c9760a1, but upstream/dev is now at 25fa9f4 (rc9 + ~20 commits beyond). jobs.rs in upstream has picked up #932 / #926 / #876 etc. since then, and re-running cargo check against the new tree is the only honest way to confirm the change still applies cleanly.

A v2 of this PR is being opened from a fresh branch off current upstream/dev, with the same 1-file, 45-line change reapplied.

rollroyces and others added 5 commits September 14, 2026 09:14
deeplethe#610 提案的第一刀。一个来源可以在 config 里写 "precision": "instant",
连接器就把 created_at / updated_at 写成完整 RFC 3339(与 deeplethe#351 后
change_line 用的同一形式),下游 facts.valid_from_precision 跟着变成
"second"。缺省仍是 day,旧来源的形状不变。

四件事:

- Source::precision() 读 config.precision,缺省 day,typo 不翻转
- time_text::world 接受 Some("instant"),输出与无精度路径一致但语义
  不同——给抽取器的精度字段是 second,不是 day
- github_issues::render_with 接 precision 参数,render() 保持 day 精度
  作为旧别名
- ingest_sources::sync_github_issues 把 source.precision() 传给 render_with

测试:721 个全过,3 个新加(time_text 的 instant 路径与跨午夜回归,
models 的 precision 默认与 typo 政策,github_issues 的 instant 精度
端到端——含注释/历史/抬头三个时间点)。

设计稿:.roadmap-proposals/instant-precision.md
留待维护者回复的 5 个问题:默认、迁移、typo 政策、doc_time 单独、
JQL 游标。

Signed-off-by: rollroyces <rollroyces@users.noreply.github.com>
fork's default branch is dev; main never gets pushed to here. without
this, the CI workflow never fires and the branch-protection status
checks on PRs to dev will never report

Signed-off-by: rollroyces <rollroyces@users.noreply.github.com>
single-owner fork: every subsystem maps to the only human with push
access. Branch protection now requires code-owner review, so the
file is meaningful even though self-review doesn't actually block.

Subsystems mapped: core data models, ingest connectors (github/jira/
notion/webdav), query_engine/* (PG/MySQL/Trino/Snowflake/Databricks),
extract pipeline, store + migrations, reason/search/llm, API + auth,
web frontend, docs + roadmap-proposals, build/CI/meta.

Default rule (*  @rollroyces) catches anything not explicitly listed
so a new subsystem inherits review without needing a follow-up edit.

Signed-off-by: rollroyces <rollroyces@users.noreply.github.com>
Signed-off-by: Royce Lam <roycelam@umich.edu>
@WaylandYang

Copy link
Copy Markdown
Contributor

感谢重新整理,也感谢上一条里把各项状态说得这么清楚。

这一条我们先关闭:#1106 已由 #1137 修复并合入 dev,做法是在同一个 worker 任务里重试状态写入,不再运行 handler;重新入队会让已完成的抽取再算一遍。另外这条分支仍带着 fork dev 上的四个提交(CODEOWNERS、CI 触发、时间精度、一次合并),所以与 dev 冲突。

再次感谢。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants