fix: Accept Systemd time span syntax when decoding time.Duration fields besides Go native format #18

Merged

onlyati merged 3 commits from fix/systemd-duration-parsing into main

2026-09-14 19:35:26 +00:00

onlyati commented

2026-09-14 19:32:53 +00:00

Owner

Resolve #17

onlyati added 3 commits

2026-09-14 19:32:53 +00:00

fix: accept systemd time span syntax when decoding time.Duration fields 518cff14b8

setFieldValue delegated straight to time.ParseDuration, which rejects
common systemd.time(7) syntax such as a bare number of seconds ("30"),
the "min" unit, and space-separated compound spans ("1min 30s"). Add a
parseSystemdDuration helper that understands systemd's own unit
spellings and use it instead.

fix: keep accepting Go's native time.Duration syntax alongside systemd's 470d9716a6

parseSystemdDuration's own grammar could not parse concatenated
compound spans like "1h30m" since it splits components on whitespace.
Try time.ParseDuration first so plain and compound Go-style durations
still work, falling back to the systemd.time(7) parser only when Go's
parser rejects the value (bare seconds, "min"/"sec" spellings, or
space-separated compounds).

fix: Linting

ci/woodpecker/pr/pr_check Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

a31262def1

onlyati changed title from ~~fix/systemd-duration-parsing~~ to fix: Accept Systemd time span syntax when decoding time.Duration fields besides Go native format

2026-09-14 19:33:28 +00:00

onlyati merged commit 93427b77d5 into main

2026-09-14 19:35:26 +00:00

onlyati deleted branch fix/systemd-duration-parsing

2026-09-14 19:35:26 +00:00

onlyati referenced this pull request from a commit

2026-09-14 19:35:28 +00:00

fix: Accept Systemd time span syntax when decoding time.Duration fields besides Go native format (#18)