mirror of
https://github.com/nextcloud/desktop.git
synced 2024-12-16 19:04:43 +03:00
6d24bd0361
When recovering from a inalid move operation, we call avoidReadFromDbOnNextSync. This will remove the fileid from the db so we don't detect a move on the next sync. But we want the next sync to fetch the file id again, and this can only happen if we don't read them from the db and do the actual PROPFIND, this is done by avoidReadFromDbOnNextSync However, if there is propagation in that source directory later, it will overide the invalid etag with the real one and we will not uissue the PROPFIND to fetch the fileid. We must therefore also protect the future write to the DB when calling avoidReadFromDbOnNextSync |
||
|---|---|---|
| .. | ||
| ownCloud | ||
| testfiles | ||
| toremote1 | ||
| exclude.cfg | ||
| README | ||
| t1.cfg.in | ||
| t1.pl | ||
| t2.pl | ||
| t3.pl | ||
| t4.pl | ||
| t5.pl | ||
| t6.pl | ||
| t7.pl | ||
| testfiles.tar.xz | ||
t1 - an integration test script for csync syncing to ownCloud. Note: This test script uses perl HTTP::DAV. This package needs to be in version 0.46 at least. Many distros deliver older versions. A working version is part of the github checkout. Note: This test script uses perl HTTP::DAV. This package needs to be in version 0.46 at least. Many distros deliver older versions. Update than. t1 uses a perl WebDAV client lib to sync to an existing instance of ownCloud. For that, various files are copied around, synced and the results are tested through their existance, the filesize and the modification times. All tests are asserts, which means that the scripts stops if a test fails. How to call: First, configure the script. For that, create a file t1.cfg. There is t1.cfg.in as an example. Yeah, this test script is not secure, make sure to run it with a weak account and in a save environment. Second, unpack the test file collection with tar xf testfiles.tar.xz in the directory where the tarball can be found. To start the script, call ./t1.pl on the commandline. A lot of output is generated. If the script does not fail, everything works. Before it actually ends, it takes a four seconds break for you to interrupt with Ctrl-C. If you don't do that, it removes all its traces... If SSL should be used, SSL must be available to LWP connections. To disable host checking for crappy SSL certs, do export PERL_LWP_SSL_VERIFY_HOSTNAME=0 Have fun, Klaas Freitag <freitag@owncloud.com>