The e2eMangledName was relative to the remote folder, repair it
authorKevin Ottens <kevin.ottens@nextcloud.com>
Mon, 1 Feb 2021 15:52:12 +0000 (16:52 +0100)
committerallexzander (Rebase PR Action) <allexzander@users.noreply.github.com>
Thu, 4 Feb 2021 11:16:48 +0000 (11:16 +0000)
commitdd83efb54317fbf299232275667c0afb996fc627
treeeb12b0de12bc8dabb600aae504df6ebd3b46cfd5
parent2c8fa40fb62901236769fe48c52d66bea91f842d
The e2eMangledName was relative to the remote folder, repair it

This got broken during the huge discovery refactoring. I wrongly passed
the mangled name as is out of discovery, but coming from listing jobs it
was fully qualified while the jobs at propagation time and the db expect
those paths to be relative to the remote folder.

Signed-off-by: Kevin Ottens <kevin.ottens@nextcloud.com>
src/libsync/discovery.cpp