mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-02-20 13:10:48 -04:00
parent 35915a30d5
commit 6e6a36fd5b
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2017-02-20T17:00:55Z"
content="""
I'd expect that the respone body is indeed not shown by --debug.
A timestamp bug seems as good a theory as anything. In either the S3
library git-annex is using, or the S3 emulation Google Cloud Storage is
using. Or perhaps google has different versions of the servers that behave
differently.
Over on [[tips/using_Google_Cloud_Storage]], @Dosenpfand
reports what looks like the same 400 when initializing a nearline remote.
Since this is using a S3 interoperability layer in Google Cloud Storage,
I'd not be surprised if there were bugs or limitations in it.
Using the native GCS API seems like an increasingly good idea,
and <https://github.com/bgilbert/gcsannex> implements that.
"""]]