Wrong PROPFIND when adding a new sync folder pair

[labkode]

When adding a new sync folder pair I copy and paste the path I want to sync however the sync client will issue a PROPFIND to a parent node which I don't have access and it fails.

I only have access to the given path and not to the whole parent nodes.

Can we avoid the sync client to trigger such PROPFIND and only do it on the node that is given (/eos/user/e/xxx/Picture/BMW) ?

The client is the CERNBox branded client, the problem happens since at least version 2.4.3.

[ogoffart]

The problem here is that the client does request as one type in order to open the tree.
The warning is valid: it could not open the tree because of one 403 error.

Should we just not show the warning? Or should there be another wording?

@michaelstingl what's your opinion ?

[labkode]

@ogoffart after pasting the path the propfind to parent should not happen. I understand that if you browse the tree yes, you need to discover the paths (which you don't have access).

So, this message should not be there in the first place.

[ogoffart]

When you paste a path, it will still try to open the tree to select the pasted path in the UI.

[labkode]

yes, however the tree is opened in the UI even though you don't have the permissions.

In the example:

/eos/user/e/xxx/Picture/BMW

the sync client only triggers one PROPFIND that fails with 403 to /eos/user/e/xxx/Picture, and not to the other parent directories (/eos, /eos/user, /eos/user/e/, /eos/user/e/xxx/).

[ogoffart]

I think it probably does, but only show one warning.

[labkode]

@ogoffart you're right, it does. Can we make the sync client trigger the propfind only for the last element of the path ?

[TheOneRing]

@labkode I guess on a normal setup we would want to display the whole tree.
I guess a better solution would be to have a less prominent error, mark the folder in the tree red and provide the error in the tooltip.
Only display the error that prominent on the final folder.

[jnweiger]

@iHerrmann77 tried to reproduce, got a crash, fbbf6656-f09a-4151-8309-7c3f7b3b7294

Hmm.