Opening an rclone remote now fails with an error that names the remote and the rclone config file vaultik read:
Remote missing: rclone remote not found in config: "dav" (config file "/path/rclone.conf", which does not exist). The ", which does not exist" part appears only when the file is missing.
When RCLONE_CONFIG is empty or /dev/null, rclone keeps its config in memory, and the error says "no config file".
The file path comes from rclone itself, so it is correct whether or not RCLONE_CONFIG is set. The failed-open test uses a remote of an unknown backend type, not a WebDAV server with a wrong password. Both errors go through the same code path, and the test needs no network.
Model: opus-5-5
closes https://git.eeqj.de/sneak/vaultik/issues/467
Opening an rclone remote now fails with an error that names the remote and the rclone config file vaultik read:
- Remote missing: `rclone remote not found in config: "dav" (config file "/path/rclone.conf", which does not exist)`. The ", which does not exist" part appears only when the file is missing.
- Remote fails to open: `opening rclone remote "dav" (config file "/path/rclone.conf"): read metadata failed: 401 Unauthorized`.
- When `RCLONE_CONFIG` is empty or `/dev/null`, rclone keeps its config in memory, and the error says "no config file".
The file path comes from rclone itself, so it is correct whether or not `RCLONE_CONFIG` is set. The failed-open test uses a remote of an unknown backend type, not a WebDAV server with a wrong password. Both errors go through the same code path, and the test needs no network.
Model: opus-5-5
clawbot
self-assigned this 2026-11-19 08:31:06 +01:00
A remote missing from the config and a remote that fails to open now
both name the remote and the rclone config file vaultik read, and say
when that file does not exist.
Model: opus-5-5
Both rclone setup errors now name the remote and the rclone config file and say when that file does not exist, with a test for each case.
Model: opus-5-5
Verdict: PASS
Head: cd86db74160d8c9e0d654bb4cf21ae2d397f521f
Both rclone setup errors now name the remote and the rclone config file and say when that file does not exist, with a test for each case.
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.
closes #467
Opening an rclone remote now fails with an error that names the remote and the rclone config file vaultik read:
rclone remote not found in config: "dav" (config file "/path/rclone.conf", which does not exist). The ", which does not exist" part appears only when the file is missing.opening rclone remote "dav" (config file "/path/rclone.conf"): read metadata failed: 401 Unauthorized.RCLONE_CONFIGis empty or/dev/null, rclone keeps its config in memory, and the error says "no config file".The file path comes from rclone itself, so it is correct whether or not
RCLONE_CONFIGis set. The failed-open test uses a remote of an unknown backend type, not a WebDAV server with a wrong password. Both errors go through the same code path, and the test needs no network.Model: opus-5-5
Verdict: PASS
Head:
cd86db7416Both rclone setup errors now name the remote and the rclone config file and say when that file does not exist, with a test for each case.
Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.