I've increased the mod_reqtimeout limits, if we are hitting a timeout on
the trac side then it must be that. Though it could very well be a timeout
on the network in front of trac...
On Sunday, January 31, 2016 at 9:38:53 PM UTC+1, Dima Pasechnik wrote:
>
> I can comment just fine on some ticke
I can comment just fine on some tickets, and just cannot on some others.
It really does not look like a networking error, but rather some trac
trouble...
On Sunday, 31 January 2016 15:59:06 UTC, Daniel Krenn wrote:
>
> On 2016-01-31 14:19, Daniel Krenn wrote:
> > On 2016-01-31 14:07, Dima Pasec
Dear Qing Liu,
Sage is already using a fairly recent version of PARI (a development
version of about 2 months old). As it happens, an upgrade of PARI in
Sage was just approved (http://trac.sagemath.org/ticket/19905).
Of course, there can be bugs, but you should be more precise: which
version
-- Forwarded message --
From: "Qing Liu"
Date: 31 Jan 2016 18:20
Subject: Re: genus2reduction
To: "John Cremona" , "William Stein" <
wst...@gmail.com>
Cc: "Karim Belabas"
Dear John and William,
I wonder if Sage could update its PARI to a more recent version.
Recently I got repor
On 2016-01-31 14:19, Daniel Krenn wrote:
> On 2016-01-31 14:07, Dima Pasechnik wrote:
>> On Sunday, 31 January 2016 12:23:59 UTC, Volker Braun wrote:
>>
>> There is a request data read error in the log, this seems to be a
>> networking error and not the fault of the trac server. I tried and
On 2016-01-31 14:07, Dima Pasechnik wrote:
> On Sunday, 31 January 2016 12:23:59 UTC, Volker Braun wrote:
>
> There is a request data read error in the log, this seems to be a
> networking error and not the fault of the trac server. I tried and
> could comment on the ticket just fine.u
On Sunday, 31 January 2016 12:23:59 UTC, Volker Braun wrote:
>
> There is a request data read error in the log, this seems to be a
> networking error and not the fault of the trac server. I tried and could
> comment on the ticket just fine.urther
>
I keep getting the same problem; a further sy
There is a request data read error in the log, this seems to be a
networking error and not the fault of the trac server. I tried and could
comment on the ticket just fine.
On Sunday, January 31, 2016 at 12:53:42 PM UTC+1, Dima Pasechnik wrote:
>
> trac server basically hangs on hitting "Submit C
trac server basically hangs on hitting "Submit Changes"
Is it just me?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To
