diff options
author | 2017-02-20 13:10:48 -0400 | |
---|---|---|
committer | 2017-02-20 13:10:48 -0400 | |
commit | 5098ea33463338e440587df692edd11650c54171 (patch) | |
tree | 27ff5aaf8faca8478c4e6f4a1545428191059b23 /doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__ | |
parent | 8bc1198391a9368747a121ece164d7c3687a961a (diff) |
comment
Diffstat (limited to 'doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__')
-rw-r--r-- | doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment b/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment new file mode 100644 index 000000000..9b3bc5535 --- /dev/null +++ b/doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment @@ -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. +"""]] |