-
-
Notifications
You must be signed in to change notification settings - Fork 872
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
Key not found: path when syncing from shared folders #209
Comments
If possible, can you re-run the failure using the following command:
and email this output to support@mynas.com.au for analysis |
It looks as though you are syncing a shared folder / shared path. Can you confirm? I have attempted to replicate using various shared folders & adding them into my OneDrive path under the root. Can you help / assist with some understanding of your scenario? |
Unable to replicate this using O365 Personal & Ubuntu 18.10 |
Hello and thank you for your quick and informative reply! Sorry that I'm replying that "late", but your responses came in in the middle of the night for me. So anyway, I am indeed syncing two folders that have been shared with me and that are owned by my wife. I didn't notice that, as I haven't accessed them for quite some time, but they are most probably the culprit, as they are the only ones that I can clearly state have no files in them whatsoever. So I'll send you the log output via mail right away. |
The joy's of being a world citizen :)
Received the email - will go through the provided log and see what it provides. |
@DerArchivar
|
Unfortunately, your change does not seem to fix the issue, as it still behaves the same.
Log of
If you again need the |
@DerArchivar |
@DerArchivar |
@DerArchivar |
@abraunegg I'm terribly sorry for the late reply! I was with my wife at her parents' house over the weekend and didn't have the laptop with me. Well, it again synced all the changes from OneDrive to the client that I had, but in the end, it failed with an error. But it's a new error, so that's progress!
Update: |
OK .. unsure why it is asserting where it is. I have updated the code to output some more diagnosis details. Can you rebuild the client (again .. sorry) and see what the code outputs? It will still assert - trying to work out why it is doing so. |
No problem! I'm a developer myself, just haven't read a line of D in my life, so I cannot assist you in debugging, unfortunately. I feel ya. ;) And I'm really grateful for your efforts! Did a clean rebuild once again and it resulted in (as far as I can see) almost the same result, even though apparently the line numbers of
|
Thanks - so essentially what is happening is the code is checking to see if the 'remote drive id' & 'remote id' exists in the local database - and if false, assert. Given this branch has fixed up a lot of the database issues, this function should be reworked. I have - for the moment - commented out the offending assert - can you rebuild and see how this goes? If this solves the issue, will do a complete function clean up. |
Ah, I see, overlooked that line. I'm just gonna shorten the verbose output to the most useful part:
Seems like that or similar assertions are being done in several locations. But it indeed seems like that is the way to go for resolving this. I don't know the full extent of the circumstances leading to this error, but just from my opinion: But I'm a (mostly) Java, C# and JavaScript guy, so maybe I'm just not enough into the behavior of D like languages. ;) |
Agree - the issue here is right now I am more 'maintaining' the original poor code rather than doing a wholesale re-write which is what it really needs - and that is a time thing at the moment. I have updated the code - see how that goes |
Would you believe that?
It is actually working now. Smoothly. You, good Sir, just made my life a lot easier and your support and incredibly fast responses and solutions are unbelievable. With the greatest appreciation, I want to thank you and confirm the fix to be working. Regarding the rewrite: I'm looking forward to this client (or your rewrite) becoming a stable application that can be distributed in binary form. Once that happens, I'll maybe take the time to build a cross platform GUI for it, just to give something back to this project. Again, thank you so much. You do a great job and it was and is a pleasure to work and be in contact with you! :) |
Glad it is all working now as it should have been.
I looked at the same thing - ended up using the Go version of 'drive' and packaging it up for use under MyNAS Storage Appliance (www.mynas.com.au) which I developed from scratch - lots of learning there as well! |
PR #211 merged |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
First of all, I'd like to thank you so much for taking over this project and fixing and improving it. I really do appreciate your efforts!
I was doing the initial synchronization with your latest version of onedrive when I got this error. It already downloaded most of the files. It could be, that it even already downloaded all the files, I can't tell for sure. It does look complete, though.
Anyway, whenever I do the
onedrive --synchronize --verbose
, the following error log returns as a result:I can provide the following detailed information:
onedrive --synchronize --verbose
items.sqlite3
results in same errorI hope someone can help me find a solution for this issue, as I'm pretty heavily relying on OneDrive. Thank you in advance!
Update:
As it still downloads all files that I newly add to my OneDrive remotely, it appears that it successfully downloaded everything.
See following updated log:
The text was updated successfully, but these errors were encountered: