molecule-ai[bot] 9be99059dd fix(scheduler): use context.Background() for post-fire UPDATE (F1089) (#1244) ... The post-fire UPDATE after s.proxy.ProxyA2ARequest() was using fireCtx, which derives from the outer ctx passed into fireSchedule(). If that ctx is cancelled — HTTP timeout, graceful shutdown, or any upstream deadline — ExecContext returns context.Canceled and the UPDATE is silently skipped, leaving next_run_at stale and causing the schedule to re-fire on the next tick. Fix: create a dedicated updateCtx from context.Background() with a 5s deadline, independent of the outer ctx hierarchy. Also improved the error log to include schedule name for easier debugging. Complements PR #1241 (fix/f1089-scheduler-ctx-fix-main) which fixes the goroutine-panic path in tick() — this fix covers the wider case of normal-return + ctx-cancelled after the proxy call. F1089 | Severity: HIGH+security Co-authored-by: Molecule AI Infra Lead <infra-lead@agents.moleculesai.app> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-04-21 03:07:26 +00:00
..
scheduler_test.go	test: trigger CI with file change	2026-04-21 00:48:52 +00:00
scheduler.go	fix(scheduler): use context.Background() for post-fire UPDATE (F1089) (#1244)	2026-04-21 03:07:26 +00:00