Output of restic version
restic 0.16.4 (v0.16.4-0-g3786536dc) compiled with go1.21.8 on linux/amd64
What backend/service did you use to store the repository?
local/any
Problem description / Steps to reproduce
restic seems to silently ignore problems with some environment variable parameters.
In my instance, the documentation wasn't clear that RESTIC_PACK_SIZE needed to be numeric only (and was in MB) and it silently ignored RESTIC_PACK_SIZE=64M and continued to use the default rather than issuing a warning or failing.
It does properly warn if the problem parameter is on the command line.
Expected behavior
I would expect restic to warn or fail if an environment variable it is using is not valid (as long as it is not being overridden on the command line).
Actual behavior
restic silently ignores problems with environment variables like RESTIC_PACK_SIZE.
Did restic help you today? Did it make you happy in any way?
Using it in a new situation, working pretty well!
Output of
restic versionrestic 0.16.4 (v0.16.4-0-g3786536dc) compiled with go1.21.8 on linux/amd64
What backend/service did you use to store the repository?
local/any
Problem description / Steps to reproduce
resticseems to silently ignore problems with some environment variable parameters.In my instance, the documentation wasn't clear that
RESTIC_PACK_SIZEneeded to be numeric only (and was in MB) and it silently ignoredRESTIC_PACK_SIZE=64Mand continued to use the default rather than issuing a warning or failing.It does properly warn if the problem parameter is on the command line.
Expected behavior
I would expect
resticto warn or fail if an environment variable it is using is not valid (as long as it is not being overridden on the command line).Actual behavior
restic silently ignores problems with environment variables like
RESTIC_PACK_SIZE.Did restic help you today? Did it make you happy in any way?
Using it in a new situation, working pretty well!