-
Notifications
You must be signed in to change notification settings - Fork 670
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
[QA] Renamed folder never propagates to windows client, when one file was locked #8766
Comments
jnweiger
changed the title
[QA] Renamed folder never propagats to windows client, when one file is locked
[QA] Renamed folder never propagates to windows client, when one file is locked
Jun 21, 2021
jnweiger
changed the title
[QA] Renamed folder never propagates to windows client, when one file is locked
[QA] Renamed folder never propagates to windows client, when one file was locked
Jun 21, 2021
Without doing a Force-sync-now: Force-sync-now or client restart is required. |
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
TheOneRing
added a commit
that referenced
this issue
Jun 22, 2021
Fixed in a9a9d07 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seen while testing #8763 with 2.8.3.4442
The client does not re-check the permissions. The error message remains visible.
Expected behaviour: As soon as the lock is gone, the client does the rename and the error message disappears.
Workaround: force sync now.
The text was updated successfully, but these errors were encountered: