projects/datalad/bugs-done/unable to get from public S3 remote without clear reasoning whyyohhttp://git-annex.branchable.com/projects/datalad/bugs-done/unable_to_get_from_public_S3_remote_without_clear_reasoning_why/git-annexikiwiki2023-01-05T17:30:31Zcomment 1http://git-annex.branchable.com/projects/datalad/bugs-done/unable_to_get_from_public_S3_remote_without_clear_reasoning_why/comment_1_87983a598cacaa8800db4a01ec23ba1b/joey2023-01-05T17:30:31Z2020-01-23T18:59:53Z
<p>It kind of looks like this S3 remote is being used without login
credentials. That's not clear, because you could have environment variables
set or creds cached, or not.</p>
<p>Since it's "public: yes", it would fall back to the public url code path to
get the file when there are no creds.</p>
<p>There are a lot of ways that could fail. Eg, perhaps no publicurl has been
configured for the remote. But in that case (and many other cases),
an exception should be thrown and displayed.</p>
<p>I think I need to know how to reproduce this to get any further.</p>
comment 2http://git-annex.branchable.com/projects/datalad/bugs-done/unable_to_get_from_public_S3_remote_without_clear_reasoning_why/comment_2_b9e5b868dd5379de18ed77907d1b42a3/yarikoptic2023-01-05T17:30:31Z2020-02-27T15:52:10Z
<p>Not sure what you meant by "need to know how to reproduce this to get any further" since a full example was provided, and to reproduce "this" problem, commands could have been cut/paste'ed.
Now, with all the changes to git-annex, and that dataset (may be next time I would do some kind of fast-export on them or host a dedicated clone), it would indeed be hard if not impossible to reproduce, and I do not observe it with git annex <code>7.20200219+git135-g34d726cba-1~ndall+1</code> so I will mark it as done</p>
comment 3http://git-annex.branchable.com/projects/datalad/bugs-done/unable_to_get_from_public_S3_remote_without_clear_reasoning_why/comment_3_667c5b94580e2ca0305d4ed97c2e199f/joey2023-01-05T17:30:31Z2020-02-28T17:28:57Z
<p>passing public=yes to initremote does not make git-annex use anonymous http
to access a S3 remote, if you have S3 credentials in the environment. I
don't remember if I tried to repro it w/o S3 credentials or not, but either
way the bug is not clear about how git-annex was trying to access the
remote when it failed.</p>