mirror of
https://github.com/rclone/rclone.git
synced 2024-12-22 23:22:08 +01:00
199d82969b
Before this change, bisync used the "canonical" Fs name in the filename for its
listing files, including any {hexstring} suffix. An unintended consequence of
this was that if a user added a backend-specific flag from the command line
(thus "overriding" the config), bisync would fail to find the listing files it
created during the prior run without this flag, due to the path now having a
{hexstring} suffix that wasn't there before (or vice versa, if the flag was
present when the session was established, and later removed.) This would
sometimes cause bisync to fail with a critical error (if no listing existed
with the alternate name), or worse -- it would sometimes cause bisync to use an
old, incorrect listing (if old listings with the alternate name DID still
exist, from before the user changed their flags.)
After this change, the issue is fixed by always normalizing the SessionName to
the non-canonical version (no {hexstring} suffix), regardless of the flags. To
avoid a breaking change, we first check if a suffixed listing exists. If so, we
rename it (and overwrite the non-suffixed version, if any.) If not, we carry on
with the non-suffixed version. (We should only find a suffixed version if
created prior to this commit.)
The result for the user is that the same pair of paths will always use the same
.lst filenames, with or without backend-specific flags.
|
||
|---|---|---|
| .. | ||
| bilib | ||
| testdata | ||
| bisync_test.go | ||
| checkfn.go | ||
| cmd.go | ||
| deltas.go | ||
| help.go | ||
| LICENSE.cjnaz | ||
| listing.go | ||
| log.go | ||
| march.go | ||
| operations.go | ||
| queue.go | ||
| rc.go | ||