GNU bug report logs -
#38428
issues.guix.gnu.org gives 500 server error for some old issues
Previous Next
Reported by: Nome Grey <greynome72 <at> gmail.com>
Date: Fri, 29 Nov 2019 17:17:01 UTC
Severity: normal
Done: Ricardo Wurmus <rekado <at> elephly.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38428 in the body.
You can then email your comments to 38428 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#38428
; Package
guix
.
(Fri, 29 Nov 2019 17:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Nome Grey <greynome72 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 29 Nov 2019 17:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I'm trying to access https://issues.guix.gnu.org/issue/26608 and
https://issues.guix.gnu.org/issue/32022, which I found from google, and
both of them are just giving 500.
[Message part 2 (text/html, inline)]
Reply sent
to
Ricardo Wurmus <rekado <at> elephly.net>
:
You have taken responsibility.
(Sun, 01 Dec 2019 08:47:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Nome Grey <greynome72 <at> gmail.com>
:
bug acknowledged by developer.
(Sun, 01 Dec 2019 08:47:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 38428-done <at> debbugs.gnu.org (full text, mbox):
Hi Nome Grey,
> I'm trying to access https://issues.guix.gnu.org/issue/26608 and
> https://issues.guix.gnu.org/issue/32022, which I found from google, and
> both of them are just giving 500.
this is now fixed.
Unfortunately, Mumi (the software behind issues.guix.gnu.org) is still
rather slow and due to a regression had to be slowed down a little more…
I hope to work on this soon.
Thanks for your bug report!
~~ Ricardo
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38428
; Package
guix
.
(Tue, 03 Dec 2019 15:50:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 38428 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Just to note it somewhere, the 500 errors are back.
On Sun, Dec 1, 2019, 12:47 AM GNU bug Tracking System <help-debbugs <at> gnu.org>
wrote:
> Your bug report
>
> #38428: issues.guix.gnu.org gives 500 server error for some old issues
>
> which was filed against the guix package, has been closed.
>
> The explanation is attached below, along with your original report.
> If you require more details, please reply to 38428 <at> debbugs.gnu.org.
>
> --
> 38428: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38428
> GNU Bug Tracking System
> Contact help-debbugs <at> gnu.org with problems
>
>
>
> ---------- Forwarded message ----------
> From: Ricardo Wurmus <rekado <at> elephly.net>
> To: greynome72 <at> gmail.com
> Cc: 38428-done <at> debbugs.gnu.org
> Bcc:
> Date: Sun, 01 Dec 2019 09:46:16 +0100
> Subject: Re: bug#38428: issues.guix.gnu.org gives 500 server error for
> some old issues
>
> Hi Nome Grey,
>
> > I'm trying to access https://issues.guix.gnu.org/issue/26608 and
> > https://issues.guix.gnu.org/issue/32022, which I found from google, and
> > both of them are just giving 500.
>
> this is now fixed.
>
> Unfortunately, Mumi (the software behind issues.guix.gnu.org) is still
> rather slow and due to a regression had to be slowed down a little more…
> I hope to work on this soon.
>
> Thanks for your bug report!
>
> ~~ Ricardo
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Nome Grey <greynome72 <at> gmail.com>
> To: bug-guix <at> gnu.org
> Cc:
> Bcc:
> Date: Fri, 29 Nov 2019 08:57:17 -0800
> Subject: issues.guix.gnu.org gives 500 server error for some old issues
> I'm trying to access https://issues.guix.gnu.org/issue/26608 and
> https://issues.guix.gnu.org/issue/32022, which I found from google, and
> both of them are just giving 500.
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38428
; Package
guix
.
(Tue, 03 Dec 2019 16:24:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 38428 <at> debbugs.gnu.org (full text, mbox):
Nome Grey <greynome72 <at> gmail.com> writes:
> Just to note it somewhere, the 500 errors are back.
I can’t reproduce this, but I do see that there are quite a lot of
connections that make it difficult for the server to serve all requests.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38428
; Package
guix
.
(Tue, 03 Dec 2019 17:49:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 38428 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Error gone for me, too, now.
On Tue, Dec 3, 2019, 8:23 AM Ricardo Wurmus <rekado <at> elephly.net> wrote:
>
> Nome Grey <greynome72 <at> gmail.com> writes:
>
> > Just to note it somewhere, the 500 errors are back.
>
> I can’t reproduce this, but I do see that there are quite a lot of
> connections that make it difficult for the server to serve all requests.
>
>
[Message part 2 (text/html, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 01 Jan 2020 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 172 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.