kolaenteandTink 68ac9eaa99 fix(migration): judge an abandoned claim by a heartbeat, not by start time ...

The claim timeout was measured from started_at, so a long import either
kept a dead claim for a day (the old 24h default) or had its slot taken
over while still running. A running migration now refreshes heartbeat_at
at a tenth of the timeout, clamped to 1s..30s, and a claim only counts as
stale once its last beat is older than the timeout. Rows that never beat
fall back to started_at. The default timeout drops to 5m accordingly.

Also bind the stale cutoff in the configured timezone: xorm writes times in
the engine's zone but binds query args as-is, which broke the comparison on
SQLite.

2026-09-15 16:59:37 +02:00

..

config_test.go

feat(config): default per-category log levels to log.level

2026-09-06 21:35:20 +02:00

config.go

fix(migration): judge an abandoned claim by a heartbeat, not by start time

2026-09-15 16:59:37 +02:00