-
Notifications
You must be signed in to change notification settings - Fork 27
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
conflicts = "overwrite"
not working
#126
Comments
I think this is similar to #121 |
Thanks @timriffe. @cimentadaj is right, this is a long-standing bug. I should have a fix for you to test by next week. |
BTW, a workaround is to upload the files to the root of the project (ie, not within a directory) or create a Component called Data and upload to that instead. |
Thanks @cimentadaj and @aaronwolen , since there's already code (beyond my
reach) that depends on the data sitting in that folder, I think I'll wait
for the fix. Thanks for looking into this both!
…On Tue, Aug 11, 2020 at 6:11 PM Aaron Wolen ***@***.***> wrote:
BTW, a workaround is to upload the files to the root of the project (ie,
not within a directory) *or* create a Component
<https://help.osf.io/hc/en-us/articles/360019737614-Create-Components>
called *Data* and upload to that instead.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG43G6ESR2TZ6FXSQ7KRGLSAFUT3ANCNFSM4OJDQ5SQ>
.
|
Should be fixed now. Feel free to re-open if you're still having issues. |
Thank you, yes it seems to work. Just an observation, if I give a vector of files to upload I get this warning from
When I loop over the files then I do not get that warning. Anyway, this issue is solved, thanks it's a big help! |
Sounds like a bug. Thanks for reporting! |
Hi,
I'm unable to overwrite files in my OSF repo https://osf.io/mpwjq/, can I get a tip on what to change in the code?
What other details would be helpful to provide to troubleshoot this?
Many thanks,
Tim
The text was updated successfully, but these errors were encountered: