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

Sync error "Processing a path that has already been done" #1353

Closed
jpmv27 opened this issue Mar 18, 2019 · 5 comments
Closed

Sync error "Processing a path that has already been done" #1353

jpmv27 opened this issue Mar 18, 2019 · 5 comments

Comments

@jpmv27
Copy link

jpmv27 commented Mar 18, 2019

Operating system

Windows 7 Home 32-bit

Application

Desktop 1.0.140

Description

Observing intermittent sync errors per the below. Error resolves itself on the next sync.

sync

This seems to happen if I am typing in a note at the moment that a scheduled sync happens.

@virtadpt
Copy link

It happens with 1.0.140 on MacOSX and the Linux 64-bit .appimage, too.

@jpmv27 jpmv27 changed the title Sync error Sync error "Processing a path that has already been done" Mar 18, 2019
@tessus
Copy link
Collaborator

tessus commented Mar 18, 2019

This is not a new issue. This always has happened in ceratain situations. This is not a bug.

@jpmv27
Copy link
Author

jpmv27 commented Mar 19, 2019

@tessus
The message says "error". If it's somehow "normal" or "expected", then the code should check for it and not display an error message.

@tessus
Copy link
Collaborator

tessus commented Mar 19, 2019

I didn't say that it's normal or expected. I said it's not a bug.
It is an error in the sense that the sync algorithm hit an edge case which results in an error. But it's not a bug. If you hit sync or wait for the next scheduled sync, the error is gone.

e.g. take a copy operation from one filesystem to another. The copy fails with an error, if there's not enough space on the target filesystem. This is also not a bug, but a valid error.

@tessus
Copy link
Collaborator

tessus commented Apr 21, 2019

Please also see Laurent's comment

@lock lock bot locked and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants