Baldwinzc 486b51eb51

fix(scheduler): normalize once-schedule next_run_at to UTC (#4607) ...

The once branch of next_run_at returned the run time with the task's
local timezone offset attached, while the cron branch normalizes to UTC.
The value is persisted into scheduled_tasks.next_run_at, and SQLAlchemy's
SQLite dialect discards tzinfo on bind, so a once task declared in a
non-UTC timezone fires shifted by the whole offset (e.g. 8 hours late
for Asia/Shanghai, hours early for negative offsets - also bypassing the
min_once_delay_seconds guard). Postgres timestamptz normalizes on write,
which is why only SQLite deployments are affected.

Align the once branch with the cron branch by converting to UTC before
returning.

2026-07-31 17:27:51 +08:00

..

deerflow

fix(scheduler): normalize once-schedule next_run_at to UTC (#4607)

2026-07-31 17:27:51 +08:00

pyproject.toml

fix(sandbox): allow grep to search a single file (#4512)

2026-07-28 07:49:13 +08:00