From 6e6a36fd5b6c213dd2db6978a0e41511f6c1fbd8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 20 Feb 2017 13:10:48 -0400 Subject: [PATCH] comment --- ..._3853bebdfcb7dac647edefd6f55ba8d5._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/Nearline_bucket_stopped_working___40__can__39__t_even_HEAD_files__41__/comment_4_3853bebdfcb7dac647edefd6f55ba8d5._comment 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 0000000000..9b3bc55354 --- /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 implements that. +"""]]