Skip to content

Fix: bwlimit/retries YAML and config keys were silently ignored (v3.11.1) - #5

Merged
Asimatasert merged 1 commit into
masterfrom
fix/yaml-transfer-options
Jul 16, 2026
Merged

Fix: bwlimit/retries YAML and config keys were silently ignored (v3.11.1)#5
Asimatasert merged 1 commit into
masterfrom
fix/yaml-transfer-options

Conversation

@Asimatasert

Copy link
Copy Markdown
Owner

Summary

--bwlimit and --retries existed only as CLI flags — a bwlimit/retries key in a jobs YAML or a config file was silently ignored (same gap class as the compress_where/from_stale mapping fixed in 3.10.0). Now mapped in the batch YAML runner, config loader and job serializer.

Testing

  • ./build.sh --check green
  • YAML mapping proven end-to-end: bwlimit: bogus in a jobs YAML is rejected by the child's strict validation ("Invalid --bwlimit"), i.e. the key now reaches the job argv
  • Underlying --bwlimit/--retries behavior unchanged (validated + used by scp/pv since 3.9.0)

Both flags existed only on the CLI — a bwlimit or retries key in a jobs
YAML or config file was silently ignored (same class of gap as the
compress_where/from_stale mapping fixed in 3.10.0). Now wired into the
batch YAML runner, the config loader and the job serializer; values pass
through the existing strict validation. Version 3.11.1.
@Asimatasert
Asimatasert merged commit dfc7faf into master Jul 16, 2026
2 checks passed
@Asimatasert
Asimatasert deleted the fix/yaml-transfer-options branch July 16, 2026 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant