Name the setting and value when a size does not parse (closes #429) #452

Merged
clawbot merged 1 commits from issue-429-name-bad-size-setting into next 2026-11-11 06:42:46 +01:00
1 Commits
Author SHA1 Message Date
sneak c9f3667757 Name the setting and value when a size does not parse (closes #429)
check / check (push) Successful in 12m50s
A size setting such as chunk_size: banana failed with "invalid size
format: strconv.ParseFloat: parsing "": invalid syntax", naming neither
the setting nor the value. The size decoder now quotes the value, and
Parse checks every size setting after ${...} references are filled in,
so the error reads chunk_size: "banana" is not a size; use a number of
bytes or a unit such as 10MB. This covers chunk_size, blob_size_limit
and s3.part_size, and config set. A value too large for a size, such as
100EB or 99999999999999999999, fails as too large, naming the setting.

Model: opus-5-5
2026-11-11 05:13:27 +00:00