This is both a general question about flags & errors in rclone, but also one on the --b2-version-at
General issue with flags & lack of errors
- In general, how can I tell if a flag is actually supported by the specific rclone subcommand + remote I'm trying to run?
- If a totally unknown flag like
--doesnotexistis included, then rclone fails immediately with an error... good, as it always should. - But it seems that with "known elsewhere" flags, they're (sometimes?) just silently ignored if the subcommand doesn't support them?
- I'm pretty sure I've run into this general issue multiple times in the past, but can't recall the exact issue each time.
- But I know that I often end up spending hours trying to figure out why something just silently doesn't work (no error, so hopefully I notice it manually)... and from there, trying to work out if it's even supported in some way at all or not.
Today's example:
-
works:
rclone ls --b2-version-at=2024-12-30T00:00:00Z b2remote:bucketname/dir
-
this don't work, but no error, it just lists everything:
rclone lsd --b2-version-at=2024-12-30T00:00:00Z b2remote:bucketname/dir- ...Same goes for other subcommands, it seems to only way to figure out which work is trial and error, and carefully inspecting the result?
-
Of course these shouldn't work at all, because I'm not even using a remote object storage, just the local FS, yet no error here either...
sss-rclone ls --b2-version-at=2024-12-30T00:00:00Z /tmp(note this isn't even using a b2 remote)sss-rclone ls --s3-versions /tmp
Version
rclone v1.68.2
- os/version: debian 10.13 (64 bit)
- os/kernel: 4.19.0-16-amd64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.3
- go/linking: static
- go/tags: none
Which cloud storage system are you using?
- Today's issue: Backblaze B2, but seems it's not specific to this