Skip to content

Feat/configurable restic command timeout - #38

Merged
MarcSchuhTNG merged 1 commit into
mainfrom
feat/configurable-restic-command-timeout
Jul 21, 2026
Merged

Feat/configurable restic command timeout#38
MarcSchuhTNG merged 1 commit into
mainfrom
feat/configurable-restic-command-timeout

Conversation

@MarcSchuhTNG

Copy link
Copy Markdown
Collaborator

No description provided.

@MarcSchuhTNG
MarcSchuhTNG requested a review from MarcSchuh as a code owner July 21, 2026 10:33
… timeout

The restic command timeout was hardcoded to 3600s in ResticClient, so large
backups were aborted after one hour. Add a `command_timeout` option that
defaults to None (no timeout) and is only enforced when set in the YAML.
- restic_client: resolve per-command timeout from a configured value
  (None = run without timeout); report the effective timeout in errors
- config_manager: add validated `command_timeout` field (positive int or null)
  and wire it through BackupScript into ResticClient
- config.example.yaml: fully document and group all supported options,
  including the new `command_timeout`
- versioning: use pyproject.toml as the single source of truth and derive
  `__version__` via importlib.metadata (drop hardcoded 0.1.0 / 2.0.0)
- add .cursor rule requiring a version bump on every change
- bump version to 0.5.1
@MarcSchuhTNG
MarcSchuhTNG force-pushed the feat/configurable-restic-command-timeout branch from 34a0ffc to 6529464 Compare July 21, 2026 10:34
@MarcSchuhTNG
MarcSchuhTNG merged commit d0a58c6 into main Jul 21, 2026
6 checks passed
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