bisync: fix --no-slow-hash settings on path2

Before this change, if path2 had slow hashes, and --no-slow-hash or --slow-hash-sync-only
was in use, bisync was erroneously setting path1's hashtype to 'none' instead of
path2's. This change fixes the issue.

See https://forum.rclone.org/t/hashtype-mismatch-with-slow-hash-sync-only-in-onedrive-local-bisync/52138/2?u=nielash
This commit is contained in:
nielash
2025-08-21 10:10:04 -04:00
committed by Nick Craig-Wood
parent 6e0e76af9d
commit 12bded980b
2 changed files with 2 additions and 1 deletions

View File

@@ -1816,6 +1816,7 @@ about _Unison_ and synchronization in general.
## Changelog
### `v1.71`
* Fixed an issue causing hash type to be set incorrectly if `path2` had slow hashes and `--no-slow-hash` or `--slow-hash-sync-only` was in use.
* Fixed an issue causing errors when running concurrent bisync runs through the `rc`.
### `v1.69.1`