should avoid triggering implicit hydration from within the desktop
client
triggering an implicit hydration on our own is strictly forbidden as
that is causing issues like deadlock and failed hydration attempts
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
SyncJournalFileRecord record;
if (_item->_instruction != CSYNC_INSTRUCTION_CONFLICT && FileSystem::fileExists(localFilePath)
&& (propagator()->_journal->getFileRecord(_item->_file, &record) && record.isValid())
- && (record._modtime == _item->_modtime && record._etag != _item->_etag)) {
+ && (record._modtime == _item->_modtime && record._etag != _item->_etag)
+ && _item->_type == ItemTypeFile) {
const auto computeChecksum = new ComputeChecksum(this);
computeChecksum->setChecksumType(checksumType);
connect(computeChecksum, &ComputeChecksum::done, this, &PropagateDownloadFile::localFileContentChecksumComputed);