-
Notifications
You must be signed in to change notification settings - Fork 12
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
cloning a previously created repo on osf failing with exitcode 128 #205
Comments
This sounds just like #202 - do you have the next extension configured to be loaded? If not, please do |
Thanks for responding, @adswa. Sorry, I did not mention that before. I did configure the extension and that did not cut it. I'll give this another go and keep you updated. |
Can you post the output of datalad wtf and git config --list? |
Hey, just a quick ping on this issue. Do you still see the problem, and if so, could you provide more information? |
I keep running into the very same issue. I installed Whatever OSF repo I try to clone, I keep getting this error:
|
hey @Gilles86, thanks for chiming in! I looked at https://osf.io/grqv8, which looks like the project you are cloning - it does not look like a DataLad dataset, or am I missing something? If it is just a regularly created OSF project, then there is no way of cloning it with datalad-osf |
Ah, sorry about that. I'm afraid this stuff is a bit above my pay grade. So if you upload a datalad dataset like this you cannot see the original filenames, etc. in the OSF Files web interface? It's always this sea of MD5 hashes? In any case, I try to clone the repo of the original issue opener I get the same issue
The same happens when I try this with a private repository of my own that I created using |
Hello, I created a project on osf using datalad in the past and trying to clone the repo with
datalad clone osf://2xmau elife-data
throws the following error. I am unsure what step I am skipping.I'd appreciate any tips/suggestions.
The text was updated successfully, but these errors were encountered: