Files
dokku/tests/unit
Jose Diaz-Gonzalez bf2cfe1886 fix: hash scheduler-k3s cron-id label to fit Kubernetes' 63-byte cap
The `dokku.com/cron-id` label could exceed Kubernetes' 63-byte cap because the cron ID is `base36(appName === command === schedule)`, which expands roughly 1.5x per byte. The label is now keyed `dokku.com/cron-hash` and holds the `sha1` hex digest of the cron-id, a fixed 40-character value that always fits the cap. The same hex digest is mirrored into the `dokku.com/cron-hash` annotation, and the original base36 cron-id stays in the `dokku.com/cron-id` annotation that `cron:list` reads when surfacing user-facing IDs. Per-task lookups stay server-side via label selectors, so `cron:set --maintenance` and the forbid/replace concurrency checks on `dokku run --cron-id` keep working without any in-memory filtering.
2026-05-24 16:52:22 -04:00
..
2026-05-24 16:06:02 -04:00
2026-05-04 13:16:28 -04:00
2026-05-10 21:42:35 -04:00
2017-02-24 12:41:12 -03:00
2024-03-13 07:47:54 -04:00
2024-03-13 07:47:54 -04:00
2024-01-19 03:51:21 -05:00
2024-02-27 14:19:53 -05:00
2024-02-25 15:54:31 -05:00
2025-11-18 17:06:30 -05:00
2025-11-09 20:21:10 -05:00