-
Notifications
You must be signed in to change notification settings - Fork 10
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
Syncing from web to local onOneDrive for Business #21
Comments
That's weird because I use it every day and is working fine here... I'm wondering if can be something related with python3.7... Anyway, I will look a this. The number of " adding watcher for {file}" will depend on your configuration. You can see it on the |
So that's normal when in debug? Great! |
I could reproduce it here. What I've found is the program logs this error, but the file/directory is created/deleted... The program can take some time (depend of your configuration) to sync, so don't expect to delete a file remotely and see sync so fast. |
So it works but it errors? |
As far I could test here it's working okay but I will take a deep look and will remove any bugs. This piece was edited one year ago is likely to have a bug there.. |
Oh, okay. |
I've had a look at this again and it seems that this only occurs when I create a file with one name then (very) quickly rename it, then it spams the KeyError continuously. If it's not so quick it only does the KeyError once. |
So even with the KeyError the sync could be completed? |
I'm not really sure. I think for doing it once it uploads, but for multiple (with unpaired watch events) it doesn't. |
Deleting/creating an item from the web client results in the error below, failing the delete/create The value for KeyError varies within 1000-7000 (from what I've seen). Fine deleting / creating files on local and uploading. The initial sync worked, just later updates do not. This makes this program useless.
also should I be worried when --debug shows a large amount of adding watcher for {file}?
The text was updated successfully, but these errors were encountered: