Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silently skips directories with invalid names, doesn't report error #3991

Closed
vasyugan opened this issue Nov 20, 2021 · 2 comments
Closed

Silently skips directories with invalid names, doesn't report error #3991

vasyugan opened this issue Nov 20, 2021 · 2 comments

Comments

@vasyugan
Copy link

This is related to #464. Today, I spent a long time trying to understand why a neighbour's Nextcloud desktop client failed to download and sync certain shared directories.

After a while I understood that the reason was the : in their names. I would have saved quite a bit of time and effort, if the client had alerted me to the reason. Even after deleting and re-creating the folder synchronisation, there was no alert. So it was completely by accident that I remembered that I had seen instances in the past, where the desktop client had actually reported an error.

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Expected behaviour

The desktop client should report the reason why the directories are not synced.

Actual behaviour

Directories are skipped , no error is reported.

Steps to reproduce

  1. Have a directory with : in the name on the server.
  2. force re-sync of the folder.

Client configuration

Client version: 3.3.6

Operating system:
Windows 10

OS language:

German

@vasyugan vasyugan added the bug label Nov 20, 2021
@claell
Copy link

claell commented Nov 24, 2021

Marking as duplicate of #464. Please add your comments there. If relevant, they might be included in the description there as well.

@claell
Copy link

claell commented Nov 24, 2021

Duplicate of #464

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants