From a00ec1aaa5e31d50096da00e439c103a302a489b Mon Sep 17 00:00:00 2001 From: Matthieu Gallien Date: Tue, 22 Nov 2022 12:18:58 +0100 Subject: [PATCH] when renaming a virtual file, manage pin state for the target name will avoid trying to set a pin state for a file that has just been renamed by us Signed-off-by: Matthieu Gallien --- src/libsync/propagatorjobs.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/libsync/propagatorjobs.cpp b/src/libsync/propagatorjobs.cpp index 112f16e9f..5dc6a2430 100644 --- a/src/libsync/propagatorjobs.cpp +++ b/src/libsync/propagatorjobs.cpp @@ -270,9 +270,9 @@ void PropagateLocalRename::start() } auto &vfs = propagator()->syncOptions()._vfs; - auto pinState = vfs->pinState(_item->_originalFile); - if (!vfs->setPinState(_item->_originalFile, PinState::Inherited)) { - qCWarning(lcPropagateLocalRename) << "Could not set pin state of" << _item->_originalFile << "to inherited"; + auto pinState = vfs->pinState(_item->_renameTarget); + if (!vfs->setPinState(_item->_renameTarget, PinState::Inherited)) { + qCWarning(lcPropagateLocalRename) << "Could not set pin state of" << _item->_renameTarget << "to inherited"; } const auto oldFile = _item->_file; -- 2.30.2