-
Notifications
You must be signed in to change notification settings - Fork 8
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
Uploader does not upload #8
Comments
With the -listonly flag, DVUploader only tells you what it would do, but does not proceed with uploads. Also - FWIW: v1.1.0 won't do direct S3 uploads against Dataverse v4.20 - you can use DVUploader v1.0.9 for that. Otherwise (and I see you don't use the -directupload flag) I think v1.1.0 should still be compatible with Dataverse 4.20. |
ah oops, sorry that was a mistake in copying it out. I of course tested it without the flag. Regarding the FWIW: not sure what that means - how do I figure out my DataVerse Server Version? And should I try the v1.0.9 or -directupload flag? |
The version is shown at the bottom right - https://darus.uni-stuttgart.de shows v4.20. (There's also an api /api/info/version I think) To debug what's going wrong - can you send the log file from the run without the -listonly flag? DVUploader currently writes most things to the console and log file, but the log file is more complete. |
I'm confused, because now it seems to work, at least a single file I successfully uploaded. |
ok. on a new dataset on the server: Now I get an error back - I did upload some files successfully without the "recurse" flag. Logfile is a good hint, because here I find:
|
Hmm - it may be having trouble with * as the path. When Dataverse added support for tracking folder paths, logic was added to DVUploader to map the local path to a folder path. The substring call that's failing is part of that. Testing was probably always done against a subfolder (e.g. with 'test' on the command line to get files in the ./test directory relative to where the uploader is being called from). |
nice! that's exactly it. (cd .. & * -> folder_name worked) |
I tried using the upload to share a dataset with subfolders.
While the tool connects to server & detects what is there and what needs to be uploaded, it simply does not upload things.
This is the log (API removed)
(Cut out some files - by now I uploaded it using the zip trick, but it is annoying and I prefer something else).
The text was updated successfully, but these errors were encountered: