Found by the acceptance test (#418), testing rclone destinations on next at d747dde.
Steps to reproduce
With storage_url: rclone://dav/backups, set RCLONE_CONFIG to a path that does not exist and run vaultik snapshot list.
Point the WebDAV remote dav at a server with a wrong password and run vaultik snapshot list.
What happened
Missing config file: rclone remote not found in config: dav. This is the same message as for a remote missing from a file that exists, and it does not name the file vaultik read.
Wrong password: creating rclone filesystem: read metadata failed: 401 Unauthorized: 401 Unauthorized. It names neither the remote nor the rclone config file.
What should happen
Each error names the remote and the rclone config file vaultik read, and says when that file does not exist.
Model: opus-5-5
Found by the acceptance test (https://git.eeqj.de/sneak/vaultik/issues/418), testing rclone destinations on `next` at `d747dde`.
**Steps to reproduce**
- With `storage_url: rclone://dav/backups`, set `RCLONE_CONFIG` to a path that does not exist and run `vaultik snapshot list`.
- Point the WebDAV remote `dav` at a server with a wrong password and run `vaultik snapshot list`.
**What happened**
- Missing config file: `rclone remote not found in config: dav`. This is the same message as for a remote missing from a file that exists, and it does not name the file vaultik read.
- Wrong password: `creating rclone filesystem: read metadata failed: 401 Unauthorized: 401 Unauthorized`. It names neither the remote nor the rclone config file.
**What should happen**
Each error names the remote and the rclone config file vaultik read, and says when that file does not exist.
Model: opus-5-5
clawbot
self-assigned this 2026-11-19 08:03:27 +01:00
Built in #471 (branch issue-467-rclone-error-names-config-file). Both rclone setup errors now name the remote and the rclone config file, and say when that file does not exist.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/vaultik/pulls/471 (branch `issue-467-rclone-error-names-config-file`). Both rclone setup errors now name the remote and the rclone config file, and say when that file does not exist.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found by the acceptance test (#418), testing rclone destinations on
nextatd747dde.Steps to reproduce
storage_url: rclone://dav/backups, setRCLONE_CONFIGto a path that does not exist and runvaultik snapshot list.davat a server with a wrong password and runvaultik snapshot list.What happened
rclone remote not found in config: dav. This is the same message as for a remote missing from a file that exists, and it does not name the file vaultik read.creating rclone filesystem: read metadata failed: 401 Unauthorized: 401 Unauthorized. It names neither the remote nor the rclone config file.What should happen
Each error names the remote and the rclone config file vaultik read, and says when that file does not exist.
Model: opus-5-5
Built in #471 (branch
issue-467-rclone-error-names-config-file). Both rclone setup errors now name the remote and the rclone config file, and say when that file does not exist.Model: opus-5-5