mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-11-12 14:00:35 +00:00
remain from its review: - `stored_next_run_at` caught the ValueErrors a dropped zone or a newer cron parser raises, but a stored `schedule_spec` that is JSON null, a list or a string fails on `.get` with AttributeError. The launch-failure handler recomputes the schedule, so that escaped `run_once`'s claimed-task loop and skipped the rest of the batch. Catch it too; the task is paused with the reason like the other unusable schedules. - `run_once` dispatched its claimed batch with a bare loop, so any per-record raise in `dispatch_task` re-aborted the batch. Isolate each task's dispatch and keep claim-level store failures loud above the loop. Tests: `test_scheduler_poll_batch_isolation.py` (non-object specs, end-to-end pause, per-task isolation). Red on `91f20a7`, green at head. Refs #7998