From: "Ludovic Courtès" <ludo@gnu.org>
To: 38411@debbugs.gnu.org
Subject: bug#38411: HTTP pipelining of narinfo requests broken for https://ci.guix.gnu.org
Date: Thu, 28 Nov 2019 11:29:08 +0100 [thread overview]
Message-ID: <87a78gxpjf.fsf@gnu.org> (raw)
In-Reply-To: <87r21sxqxb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 28 Nov 2019 10:59:12 +0100")
AFAICS everything is working fine with this config:
--8<---------------cut here---------------start------------->8---
root@berlin ~/maintenance/hydra# guix describe
Generation 45 Nov 28 2019 11:02:51 (current)
guix 18a5575
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 18a5575ec530f0e7a2e27f2aa3b5addf20da0f87
root@berlin ~/maintenance/hydra# git log |head
commit 9fdb990982006a4d0ddb68aa71351cc76ef50cdc
Author: Ludovic Courtès <ludo@gnu.org>
Date: Thu Nov 28 11:23:29 2019 +0100
nginx: berlin: Use nginx 1.17.4.
* hydra/nginx/berlin.scm (nginx-1.17.4): New variable.
(%nginx-configuration)[nginx]: New field.
--8<---------------cut here---------------end--------------->8---
Please let me know if you encounter any issues!
I’ll leave it at that for now, but we’ll have to pay attention to that
in future upgrades. (Ideally we’d report a bug to nginx but that’s
tricky enough that this alone would take much more time than I can
allocate to it.)
Ludo’.
next prev parent reply other threads:[~2019-11-28 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 9:22 bug#38411: HTTP pipelining of narinfo requests broken for https://ci.guix.gnu.org Ludovic Courtès
2019-11-28 9:59 ` Ludovic Courtès
2019-11-28 10:18 ` Ludovic Courtès
2019-11-28 10:29 ` Ludovic Courtès [this message]
2019-11-28 10:04 ` Ludovic Courtès
2019-12-25 16:50 ` Gábor Boskovits
[not found] ` <handler.38411.D38411.157729267617189.notifdone@debbugs.gnu.org>
2019-12-26 18:14 ` bug#38411: closed (HTTP pipelining of narinfo requests broken for https://ci.guix.gnu.org) Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a78gxpjf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38411@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).