-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
Can't upload any files when using a nested path with --single-directory if folders already exist on OneDrive #1582
Comments
@plouj OK - a couple of things - by default, when running as a Docker container, The second issue is (and this is probably a compiler / Docker container item here) - is that, for whatever reason, the application is deciding to generate a fake OneDrive API response for the parent folder, thus, as this data is nonsensical, and only makes sense if The next issue appears to stem from the client 'thinking' that the upload location is a 'shared folder' ... but this is because the 'parent' is not known (see above) ... so just to confirm this thinking - can you confirm that the upload location for this data is or is not a OneDrive Personal Shared Folder? I suspect that it is not. This will help with trying to unpick what is going on here.
Currently the Docker image is built with 2.092.1 - and should be updated. I think for the first port of call here, given the oddity of this issue, is to get the Dockerfiles updated and have you rebuild your Docker Container from a PR, that is using the updated compiler. If you are then still seeing an issue, then dig deeper into the code. |
Please can you test the following PR:
Once your local 'onedrive' git repository is created, you will need to rebuild your Docker container as per your current process:
When running the updated Docker container, your version of the client should be If you can test & provide feedback that would be greatly appreciated. |
Thank you for such a quick response! Saw this during the new build:
I actually did have
I don't think it's a shared folder, but I honestly don't know and I don't know how to check. I've created this folder ( With the newer compiler, using
Without
However, if I shorten Perhaps I'm just not using this tool as intended. |
@plouj
Please can you generate a new verbose debug log (last time you also used --debug-https ... no need for that) - just --verbose --verbose when using the updated client / Docker container (and make sure no --dry-run) This will give an updated debug log file, ensuring that all the data should be in the correct places .. and give a clearer picture as to what is going on.
The only way to do this is via logging into OneDrive online via a browser, and looking at all of the folders. Once you send the updated debug log, I can add in more logging output to hone in whats happening. |
I think that's what confused me. This time, after running
Perhaps because now the needed folders are in the local dabatase? If I clear the local database (re-create all of
|
@plouj
OK .. then this is a bug ... If you can provide a full debug output that would be great. I will also try and replicate the issue locally in the meantime. |
@plouj Will have to update the PR to generate more debug output to analyse what is going on. Edit: Running again, error is displayed ..... able to reproduce now. |
@plouj When running the updated client / Docker container, the client version should be: |
Looks like you fixed it as I don't get 400 errors with |
@plouj |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Report Details
I'm unable to upload any of my files and the error in all/most cases appears to be:
Application and Operating System Details:
docker build . -t local-onedrive -f contrib/docker/Dockerfile
The mount was created with:
I think the actual files on the remote machine resides on a zfs partitition.
I run
onedrive
with Docker like this:The OneDrive folder is not shared with any other systems or platforms at the same time.
Full debug log sent to support@mynas.com.au as
onedrive-plouj-debug-http.log
Output for a small sub-directory
The text was updated successfully, but these errors were encountered: