-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/10 02:51, Terry Reedy wrote:
>> I hope I can go sleep before dawn :-P.
>
> I added a comment to one issue and opened another with no problem during
> the last couple of hours.
My changes have work now. After like 8 hours and a retry every fi
On 11/23/2010 8:32 PM, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/10 01:31, Jesus Cea wrote:
Still retrying, with no luck.
Anybody else can reproduce?.
One of my tracker changes was just processed.
The important one still retrying every 5 minutes...
I hope I ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/10 01:31, Jesus Cea wrote:
> Still retrying, with no luck.
>
> Anybody else can reproduce?.
One of my tracker changes was just processed.
The important one still retrying every 5 minutes...
I hope I can go sleep before dawn :-P.
- --
Jes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 21:33, Jesus Cea wrote:
> Happen to me last Sunday, and happening just now.
>
> I can access http://bugs.python.org/ just fine, but trying to post a
> message, open a new bug, change nosy, etc., takes a LONG time (minutes)
> and it is fina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Happen to me last Sunday, and happening just now.
I can access http://bugs.python.org/ just fine, but trying to post a
message, open a new bug, change nosy, etc., takes a LONG time (minutes)
and it is finally failing with a "400 Bad Request" error:
"
