Closed stebo85 closed 2 months ago
Many thanks for your detailed issue! Upon a first try in a fresh virtual environment, I wasn't able to reproduce this problem (thanks much for the reproducer!):
(osf) adina@muninn in /tmp
❱ datalad create test
create(ok): /tmp/test (dataset)
(osf) adina@muninn in /tmp
❱ cd test
(osf) adina@muninn in /tmp/test on git:master
❱ touch test
(osf) adina@muninn in /tmp/test on git:master
❱ datalad osf-credentials
osf_credentials(ok): [authenticated as Adina Svenja Wagner <adina.wagner@t-online.de>]
(osf) adina@muninn in /tmp/test on git:master
❱ datalad save -m "added new files"
add(ok): test (file)
save(ok): . (dataset)
action summary:
add (ok: 1)
save (ok: 1)
(osf) adina@muninn in /tmp/test on git:master
❱ datalad create-sibling-osf --title best-study-ever-test -s osf
create-sibling-osf(ok): https://osf.io/bhkvq/
[INFO ] Configure additional publication dependency on "osf-storage"
configure-sibling(ok): . (sibling)
(osf) adina@muninn in /tmp/test on git:master
❱ datalad push --to osf
copy(ok): test (file) [to osf-storage...]
publish(ok): . (dataset) [refs/heads/master->osf:refs/heads/master [new branch]]
publish(ok): . (dataset) [refs/heads/git-annex->osf:refs/heads/git-annex [new branch]]
action summary:
copy (ok: 1)
publish (ok: 2)
(osf) adina@muninn in /tmp/test on git:master
I wonder if its the specific git-annex version that's the culprit - I wont get to it in the next hour, but I will later today try toying with different annex versions.
Yes, I think it’s related to the git annex version because it was working with the standard git annex version in Ubuntu 22.04 and datalad 0.7 from memory - but datalad 1.0 wasn’t compatible with that git annex version anymore, so after upgrading the git annex version using the new git annex version from neurodebian this problem appeared.
Thank you
Steffen
--
W: https://mri.sbollmann.nethttps://mri.sbollmann.net/ | W: https://www.neurodesk.orghttps://www.neurodesk.org/ | T: https://twitter.com/sbollmann_MRI | G: https://github.com/stebo85
Book meeting: https://calendly.com/s-bollmann/meeting
From: Adina Wagner @.> Sent: Friday, September 13, 2024 5:21:05 PM To: datalad/datalad @.> Cc: Steffen Bollmann @.>; Author @.> Subject: Re: [datalad/datalad] Datalad OSF sibling not working (Issue datalad/datalad-osf#202)
Many thanks for your detailed issue! Upon a first try in a fresh virtual environment, I wasn't able to reproduce this problem (thanks much for the reproducer!):
(osf) @. in /tmp ❱ datalad create test create(ok): /tmp/test (dataset) (osf) @. in /tmp ❱ cd test (osf) @. in /tmp/test on git:master ❱ touch test (osf) @. in /tmp/test on git:master ❱ datalad osf-credentials osf_credentials(ok): [authenticated as Adina Svenja Wagner @.>] (osf) @. in /tmp/test on git:master ❱ datalad save -m "added new files" add(ok): test (file) save(ok): . (dataset) action summary: add (ok: 1) save (ok: 1) (osf) @. in /tmp/test on git:master ❱ datalad create-sibling-osf --title best-study-ever-test -s osf create-sibling-osf(ok): https://osf.io/bhkvq/ [INFO ] Configure additional publication dependency on "osf-storage" configure-sibling(ok): . (sibling) (osf) @. in /tmp/test on git:master ❱ datalad push --to osf copy(ok): test (file) [to osf-storage...] publish(ok): . (dataset) [refs/heads/master->osf:refs/heads/master [new branch]] publish(ok): . (dataset) [refs/heads/git-annex->osf:refs/heads/git-annex [new branch]] action summary: copy (ok: 1) publish (ok: 2) (osf) @.*** in /tmp/test on git:master
I wonder if its the specific git-annex version that's the culprit - I wont get to it in the next hour, but I will later today try toying with different annex versions.
— Reply to this email directly, view it on GitHubhttps://github.com/datalad/datalad-osf/issues/202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6V2W35W4L5DVQRUXHRTBTZWKG6DAVCNFSM6AAAAABOEUIMHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGIYTIMBZGU. You are receiving this because you authored the thread.Message ID: @.***>
hey, I got it - can you check if you have the datalad-next
extension configured to be "loaded"? Its a bug from our side, though, for some reason we haven't included it in the docs... and at the moment, it is still a necessary step.
I'll transfer this issue to datalad-osf, and add it to the docs.
try running:
git config --global --add datalad.extensions.load next
and then retry push
wonderful - that worked perfectly now :)
What is the problem?
datalad push --to osf
fails with:What steps will reproduce the problem?
DataLad information
Additional context
No response
Have you had any success using DataLad before?
yes, the same workflow worked a few months ago :)