Are the bug tracker and meta-tracker down for anyone else, or is it just me? Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Mon, Aug 2, 2010 at 6:17 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Are the bug tracker and meta-tracker down for anyone else, or is it just me?
It is down for me as well. It appears to be accepting the connection and then just doesn't return any content. -- David blog: http://www.traceback.org twitter: http://twitter.com/dstanek
Down for me as well. Initially I though it was shield by "Great Firewall" since I'm from China. On Tue, Aug 3, 2010 at 9:29 AM, David Stanek <dstanek@dstanek.com> wrote:
On Mon, Aug 2, 2010 at 6:17 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Are the bug tracker and meta-tracker down for anyone else, or is it just me?
It is down for me as well. It appears to be accepting the connection and then just doesn't return any content.
-- David blog: http://www.traceback.org twitter: http://twitter.com/dstanek _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ysj.ray%2Bpython-dev%40gma...
-- Ray Allen Best wishes!
There's no new issue posted this morning. I tried to post an issue, and an error occurred on submit. So... -- Florent 2010/8/3 Fred Drake <fdrake@acm.org>
On Tue, Aug 3, 2010 at 1:01 AM, Ray Allen <ysj.ray@gmail.com> wrote:
Is the tracker OK now?
It's working for me.
-Fred
-- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein _______________________________________________
Apparently you are not the only one experiencing it. On #python-dev we get such notifications: <CIA-31> alanwilter roundup * #9485/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9486/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <fdrake> gutworth: Too late. tarek is lost to us. <CIA-31> alanwilter roundup * #9487/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9488/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... But the relevant bug entries don't exist. Regards Antoine. On Tue, 3 Aug 2010 15:59:50 +0200 Florent Xicluna <florent.xicluna@gmail.com> wrote:
There's no new issue posted this morning. I tried to post an issue, and an error occurred on submit.
So...
-- Florent
2010/8/3 Fred Drake <fdrake@acm.org>
On Tue, Aug 3, 2010 at 1:01 AM, Ray Allen <ysj.ray@gmail.com> wrote:
Is the tracker OK now?
It's working for me.
-Fred
-- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein _______________________________________________
On Tue, 03 Aug 2010 16:35:01 +0200, Antoine Pitrou <solipsis@pitrou.net> wrote:
Apparently you are not the only one experiencing it. On #python-dev we get such notifications:
<CIA-31> alanwilter roundup * #9485/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9486/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <fdrake> gutworth: Too late. tarek is lost to us. <CIA-31> alanwilter roundup * #9487/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9488/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ...
But the relevant bug entries don't exist.
Fixed. Apparently a line was dropped when applying a patch to the tracker, but the mistake didn't surface until roundup was restarted after the reboot. -- R. David Murray www.bitdance.com
On Tue, Aug 3, 2010 at 11:58, R. David Murray <rdmurray@bitdance.com> wrote:
On Tue, 03 Aug 2010 16:35:01 +0200, Antoine Pitrou <solipsis@pitrou.net> wrote:
Apparently you are not the only one experiencing it. On #python-dev we get such notifications:
<CIA-31> alanwilter roundup * #9485/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9486/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <fdrake> gutworth: Too late. tarek is lost to us. <CIA-31> alanwilter roundup * #9487/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ... <CIA-31> alanwilter roundup * #9488/signal.signal/signal.alarm not working as expected: [new] I have this example code to illustrate a problem I am ...
But the relevant bug entries don't exist.
Fixed. Apparently a line was dropped when applying a patch to the tracker, but the mistake didn't surface until roundup was restarted after the reboot.
-- R. David Murray www.bitdance.com
Are these issues going to show up or are they lost? Via IRC, #9490 and it's apparent dupe #9491 looked interesting to me (Windows service related).
Am 03.08.2010 19:05, schrieb Brian Curtin:
On Tue, Aug 3, 2010 at 11:58, R. David Murray <rdmurray@bitdance.com
Fixed. Apparently a line was dropped when applying a patch to the tracker, but the mistake didn't surface until roundup was restarted after the reboot.
-- R. David Murray www.bitdance.com <http://www.bitdance.com>
Are these issues going to show up or are they lost? Via IRC, #9490 and it's apparent dupe #9491 looked interesting to me (Windows service related).
I would recommend contacting the poster via the address he registered in the tracker. Georg
On Tue, 03 Aug 2010 20:36:36 +0200, Georg Brandl <g.brandl@gmx.net> wrote:
Am 03.08.2010 19:05, schrieb Brian Curtin:
On Tue, Aug 3, 2010 at 11:58, R. David Murray <rdmurray@bitdance.com
Fixed. Apparently a line was dropped when applying a patch to the tracker, but the mistake didn't surface until roundup was restarted after the reboot.
Are these issues going to show up or are they lost? Via IRC, #9490 and it's apparent dupe #9491 looked interesting to me (Windows service related).
I would recommend contacting the poster via the address he registered in the tracker.
Yes, please do that. As far as I know the issues never got created, even though the issue counter did increment. --David
participants (10)
-
Antoine Pitrou -
Brian Curtin -
David Stanek -
Dirkjan Ochtman -
Florent Xicluna -
Fred Drake -
Georg Brandl -
Nick Coghlan -
R. David Murray -
Ray Allen