suzmii
ff42fff61c
Project CI / Repository checks (pull_request) Successful in 3m18s
Project CI / Frontend tests (pull_request) Successful in 4m3s
Project CI / Backend tests (pull_request) Successful in 7m25s
Project CI / Native shell tests (pull_request) Successful in 19m35s
按评审意见把写锁等待挪出 runtime worker 并收紧 wait_exhausted 记账
- agc_write_file 写路径改经 bridge_write_file_in_blocking_pool 走 tokio::task::spawn_blocking：有界等待是同步轮询（最多约 10 秒），直接在 async handler 里跑会占住 tokio worker，争用窗口内同一轮并行写多个文件时会波及共享同一 runtime 的只读端点与 UI 命令
- 新增用例用默认 current_thread runtime 加心跳任务锁住该性质；把 handler 临时改回同步直调时该用例按预期失败，确认有区分度
- project.write_lock.wait_exhausted 与终态改判一起改为只在真的等过（max_attempts > 1）时发生：hydrate 的单次试探不再写 waitedMs 近似 0 的“耗尽”日志
- 技术方案、decision-log、pitfalls 同步这两条，并补“同步有界等待不能直接跑在 async handler 里”的排障经验
2026-09-10 21:38:48 +08:00
..
2026-07-12 19:32:11 +08:00
2026-07-17 21:03:15 +08:00
2026-09-03 20:02:48 +08:00
2026-06-23 21:02:13 +08:00
2026-08-31 14:10:44 +08:00
2026-08-08 11:11:25 +08:00
2026-08-21 15:33:02 +08:00
2026-09-01 16:28:34 +08:00
2026-08-08 15:10:16 +08:00
2026-09-03 20:02:48 +08:00
2026-07-15 22:14:52 +08:00
2026-09-03 10:02:05 +08:00
2026-09-01 16:28:34 +08:00
2026-09-03 15:33:26 +08:00
2026-09-01 16:28:34 +08:00
2026-08-07 18:03:30 +08:00
2026-09-01 16:28:34 +08:00
2026-09-03 11:38:40 +08:00
2026-09-01 16:28:34 +08:00
2026-06-11 22:33:05 +08:00
2026-09-09 12:00:10 +08:00
2026-09-03 10:36:43 +08:00
2026-09-07 15:17:21 +08:00
2026-09-03 14:24:40 +08:00
2026-09-10 21:38:48 +08:00
2026-09-08 22:04:37 +08:00
2026-09-08 22:01:29 +08:00
2026-09-01 16:28:34 +08:00
2026-09-08 22:01:29 +08:00
2026-09-08 22:01:29 +08:00
2026-09-06 00:36:31 +08:00
2026-08-25 15:41:55 +08:00
2026-09-04 16:30:43 +08:00
2026-08-20 19:07:25 +08:00
2026-08-12 14:46:24 +08:00
2026-09-01 16:28:34 +08:00
2026-06-14 19:34:44 +08:00
2026-09-10 20:12:28 +08:00
2026-09-08 13:25:24 +00:00
2026-09-08 10:43:38 +00:00
2026-09-01 16:28:34 +08:00
2026-06-14 19:34:44 +08:00
2026-09-03 19:36:18 +08:00
2026-09-08 11:56:36 +08:00
2026-09-01 20:13:48 +08:00