extern/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2024-12-03 22:12:02 +01:00
Code Issues Packages Projects Releases Wiki Activity
57624629d6
rclone/cmd/bisync/testdata/test_extended_char_paths/golden/test.log

118 lines
7.2 KiB
Plaintext
Raw Normal View History

bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
(01) : test extended-char-paths
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(02) : fix-names {path1/}測試_Русский_{spc}_{spc}_ě_áñ/
(03) : fix-names {path2/}測試_Русский_{spc}_{spc}_ě_áñ/
(04) : fix-names {path1/}測試_Русский_{spc}_{spc}_ě_áñ/測試_check{spc}file
(05) : fix-names {path2/}測試_Русский_{spc}_{spc}_ě_áñ/測試_check{spc}file
(06) : fix-names {path1/}測試_Русский_{spc}_{spc}_ě_áñ/filename_contains_ě_.txt
(07) : fix-names {path2/}測試_Русский_{spc}_{spc}_ě_áñ/filename_contains_ě_.txt
(08) : fix-names {path1/}測試_check{spc}file
(09) : fix-names {path2/}測試_check{spc}file
(10) : fix-names {path1/}測試_Русский_{spc}_{spc}_ě_áñ/測試_check{spc}file
(11) : fix-names {path2/}測試_Русский_{spc}_{spc}_ě_áñ/測試_check{spc}file
(12) : test resync subdirs with extended chars
(13) : bisync subdir=測試_Русский_{spc}_{spc}_ě_áñ resync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}測試_Русский_ _ _ě_áñ/" with Path2 "{path2/}測試_Русский_ _ _ě_áñ/"
INFO : Copying unique Path2 files to Path1
bisync: optimize --resync performance -- partially addresses #5681 Before this change, --resync was handled in three steps, and needed to do a lot of unnecessary work to implement its own --ignore-existing logic, which also caused problems with unicode normalization, in addition to being pretty slow. After this change, it is refactored to produce the same result much more efficiently, by reducing the three steps to two and letting ci.IgnoreExisting do the work instead of reinventing the wheel. The behavior and sync order remain unchanged for now -- just faster (but see the ongoing lively discussions about potential future changes in #5681!)
2023-11-06 16:34:47 +01:00
INFO : - Path2 Resync is copying UNIQUE files to - Path1
INFO : - Path1 Resync is copying UNIQUE OR DIFFERING files to - Path2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Resync updating listings
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(14) : copy-listings resync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(15) : test place new files with extended chars on each side
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(16) : touch-glob 2001-01-02 {datadir/} file1.txt
(17) : copy-as {datadir/}file1.txt {path1/}測試_Русский_{spc}_{spc}_ě_áñ 測試_file1p1
(18) : copy-as {datadir/}file1.txt {path2/}測試_Русский_{spc}_{spc}_ě_áñ 測試_file1p2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(19) : test normal sync of subdirs with extended chars
(20) : bisync subdir=測試_Русский_{spc}_{spc}_ě_áñ
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}測試_Русский_ _ _ě_áñ/" with Path2 "{path2/}測試_Русский_ _ _ě_áñ/"
bisync: generate listings concurrently with march -- fixes #7332 Before this change, bisync needed to build a full listing for Path1, then a full listing for Path2, then compare them -- and each of those tasks needed to finish before the next one could start. In addition to being slow and inefficient, it also caused real problems if a file changed between the time bisync checked it on Path1 and the time it checked the corresponding file on Path2. This change solves these problems by listing both paths concurrently, using the same March infrastructure that check and sync use to traverse two directories in lock-step, optimized by Go's robust concurrency support. Listings should now be much faster, and any given path is now checked nearly-instantaneously on both sides, minimizing room for error. Further discussion: https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors
2023-10-07 12:33:43 +02:00
INFO : Building Path1 and Path2 listings
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1 checking for diffs
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : - Path1 File is new - 測試_file1p1
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1: 1 changes: 1 new, 0 newer, 0 older, 0 deleted
INFO : Path2 checking for diffs
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : - Path2 File is new - 測試_file1p2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path2: 1 changes: 1 new, 0 newer, 0 older, 0 deleted
INFO : Applying changes
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : - Path1 Queue copy to Path2 - {path2/}測試_Русский_ _ _ě_áñ/測試_file1p1
INFO : - Path2 Queue copy to Path1 - {path1/}測試_Русский_ _ _ě_áñ/測試_file1p2
INFO : - Path2 Do queued copies to - Path1
INFO : - Path1 Do queued copies to - Path2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Updating listings
INFO : Validating listings for Path1 "{path1/}測試_Русский_ _ _ě_áñ/" vs Path2 "{path2/}測試_Русский_ _ _ě_áñ/"
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(21) : move-listings normal-sync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(22) : test check-filename with extended chars. check should fail.
(23) : bisync resync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
INFO : Copying unique Path2 files to Path1
bisync: optimize --resync performance -- partially addresses #5681 Before this change, --resync was handled in three steps, and needed to do a lot of unnecessary work to implement its own --ignore-existing logic, which also caused problems with unicode normalization, in addition to being pretty slow. After this change, it is refactored to produce the same result much more efficiently, by reducing the three steps to two and letting ci.IgnoreExisting do the work instead of reinventing the wheel. The behavior and sync order remain unchanged for now -- just faster (but see the ongoing lively discussions about potential future changes in #5681!)
2023-11-06 16:34:47 +01:00
INFO : - Path2 Resync is copying UNIQUE files to - Path1
INFO : - Path1 Resync is copying UNIQUE OR DIFFERING files to - Path2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Resync updating listings
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(24) : delete-file {path1/}測試_Русский_{spc}_{spc}_ě_áñ/測試_check{spc}file
(25) : bisync check-access check-filename=測試_check{spc}file
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
bisync: generate listings concurrently with march -- fixes #7332 Before this change, bisync needed to build a full listing for Path1, then a full listing for Path2, then compare them -- and each of those tasks needed to finish before the next one could start. In addition to being slow and inefficient, it also caused real problems if a file changed between the time bisync checked it on Path1 and the time it checked the corresponding file on Path2. This change solves these problems by listing both paths concurrently, using the same March infrastructure that check and sync use to traverse two directories in lock-step, optimized by Go's robust concurrency support. Listings should now be much faster, and any given path is now checked nearly-instantaneously on both sides, minimizing room for error. Further discussion: https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors
2023-10-07 12:33:43 +02:00
INFO : Building Path1 and Path2 listings
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1 checking for diffs
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : - Path1 File was deleted - 測試_Русский_ _ _ě_áñ/測試_check file
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1: 1 changes: 0 new, 0 newer, 0 older, 1 deleted
INFO : Path2 checking for diffs
INFO : Checking access health
ERROR : Access test failed: Path1 count 1, Path2 count 2 - 測試_check file
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
ERROR : -  Access test failed: Path2 file not found in Path1 - 測試_Русский_ _ _ě_áñ/測試_check file
ERROR : Bisync critical error: check file check failed
ERROR : Bisync aborted. Must run --resync to recover.
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
Bisync error: bisync aborted
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(26) : copy-listings check-access-fail
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(27) : test check-filename with extended chars. check should pass.
(28) : bisync resync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
INFO : Copying unique Path2 files to Path1
bisync: optimize --resync performance -- partially addresses #5681 Before this change, --resync was handled in three steps, and needed to do a lot of unnecessary work to implement its own --ignore-existing logic, which also caused problems with unicode normalization, in addition to being pretty slow. After this change, it is refactored to produce the same result much more efficiently, by reducing the three steps to two and letting ci.IgnoreExisting do the work instead of reinventing the wheel. The behavior and sync order remain unchanged for now -- just faster (but see the ongoing lively discussions about potential future changes in #5681!)
2023-11-06 16:34:47 +01:00
INFO : - Path2 Resync is copying UNIQUE files to - Path1
INFO : - Path1 Resync is copying UNIQUE OR DIFFERING files to - Path2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Resync updating listings
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(29) : bisync check-access check-filename=測試_check{spc}file
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
bisync: generate listings concurrently with march -- fixes #7332 Before this change, bisync needed to build a full listing for Path1, then a full listing for Path2, then compare them -- and each of those tasks needed to finish before the next one could start. In addition to being slow and inefficient, it also caused real problems if a file changed between the time bisync checked it on Path1 and the time it checked the corresponding file on Path2. This change solves these problems by listing both paths concurrently, using the same March infrastructure that check and sync use to traverse two directories in lock-step, optimized by Go's robust concurrency support. Listings should now be much faster, and any given path is now checked nearly-instantaneously on both sides, minimizing room for error. Further discussion: https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors
2023-10-07 12:33:43 +02:00
INFO : Building Path1 and Path2 listings
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1 checking for diffs
INFO : Path2 checking for diffs
INFO : Checking access health
INFO : Found 2 matching "測試_check file" files on both paths
INFO : No changes found
INFO : Updating listings
INFO : Validating listings for Path1 "{path1/}" vs Path2 "{path2/}"
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(30) : move-listings check-access-pass
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(31) : test filters-file path with extended chars - masks /fileZ.txt
(32) : copy-file {datadir/}測試_filtersfile.txt {workdir/}
(33) : bisync filters-file={workdir/}測試_filtersfile.txt resync
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
INFO : Using filters file {workdir/}測試_filtersfile.txt
INFO : Storing filters file hash to {workdir/}測試_filtersfile.txt.md5
INFO : Copying unique Path2 files to Path1
bisync: optimize --resync performance -- partially addresses #5681 Before this change, --resync was handled in three steps, and needed to do a lot of unnecessary work to implement its own --ignore-existing logic, which also caused problems with unicode normalization, in addition to being pretty slow. After this change, it is refactored to produce the same result much more efficiently, by reducing the three steps to two and letting ci.IgnoreExisting do the work instead of reinventing the wheel. The behavior and sync order remain unchanged for now -- just faster (but see the ongoing lively discussions about potential future changes in #5681!)
2023-11-06 16:34:47 +01:00
INFO : - Path2 Resync is copying UNIQUE files to - Path1
INFO : - Path1 Resync is copying UNIQUE OR DIFFERING files to - Path2
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Resync updating listings
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
bisync: account for differences in backend features on integration tests - see #5679 Before this change, integration tests often could not be run on backends with differing features from the local system that goldenized them. In particular, differences in modtime precision, checksum support, and encoding would cause false positives. After this change, the tests more accurately account for the features of the backend being tested, which allows us to see true positives more clearly, and more meaningfully assess whether a backend is supported.
2023-11-17 18:14:38 +01:00
(34) : copy-as {datadir/}file1.txt {path1/} fileZ.txt
(35) : bisync filters-file={workdir/}測試_filtersfile.txt
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Synching Path1 "{path1/}" with Path2 "{path2/}"
INFO : Using filters file {workdir/}測試_filtersfile.txt
bisync: generate listings concurrently with march -- fixes #7332 Before this change, bisync needed to build a full listing for Path1, then a full listing for Path2, then compare them -- and each of those tasks needed to finish before the next one could start. In addition to being slow and inefficient, it also caused real problems if a file changed between the time bisync checked it on Path1 and the time it checked the corresponding file on Path2. This change solves these problems by listing both paths concurrently, using the same March infrastructure that check and sync use to traverse two directories in lock-step, optimized by Go's robust concurrency support. Listings should now be much faster, and any given path is now checked nearly-instantaneously on both sides, minimizing room for error. Further discussion: https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors
2023-10-07 12:33:43 +02:00
INFO : Building Path1 and Path2 listings
bisync: test scenarios #5164 Co-authored-by: Chris Nelson <stuff@cjnaz.com>
2021-04-01 12:21:23 +02:00
INFO : Path1 checking for diffs
INFO : Path2 checking for diffs
INFO : No changes found
INFO : Updating listings
INFO : Validating listings for Path1 "{path1/}" vs Path2 "{path2/}"
bisync: introduce terminal colors This introduces a few basic color codings to make the terminal output more readable (and more fun). Rclone's standard --color flag is supported. (AUTO|NEVER|ALWAYS) Only a few lines have colors right now -- more will probably be added in future versions.
2023-11-06 12:59:41 +01:00
INFO : Bisync successful
Reference in New Issue Copy Permalink