I just turned off experimental. There aren't that many things being tested
there at the moment, so no one should need to use it. One of plugins being
tested (the git plugin) may also be causing all of these zombie git
processes.
On Thu, Jun 14, 2012 at 2:14 PM, Jonathan Bober wrote:
> I think th
Jonathan Bober writes:
> I think that the experimental trac server is getting hit by Baidu in
> bad places, and it isn't behaving well. There should be a robots.txt
> for trac, which should probably completely disallow the experimental
> installation, and something probably needs to be fixed with
I think that the experimental trac server is getting hit by Baidu in
bad places, and it isn't behaving well. There should be a robots.txt
for trac, which should probably completely disallow the experimental
installation, and something probably needs to be fixed with the
experimental installation.
I assume this has been noticed by others, but Trac has been a nightmare
today. Just pointing it out, I understand if there isn't anything that can
be done...
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsu
On Wed, Jun 13, 2012 at 2:58 PM, Nils Bruin wrote:
> On Jun 13, 11:35 am, William Stein wrote:
>> For "fun", I just did
>>
>> /etc/init.d/apache2 restart
>> /etc/init.d/postgresql restart
>>
>> which might impact something...
>
> Has anyone checked trac's logs to see *why* trac is slow? Wit
On Wed, Jun 13, 2012 at 1:10 PM, Keshav Kini wrote:
> Benjamin Jones writes:
>> On Wed, Jun 13, 2012 at 2:08 PM, Starx wrote:
To fix the patchbot problem, you can always run a patchbot
instance yourself on this particular ticket and the new results will
show up.
>>>
>>> Can I? I
On Jun 13, 11:35 am, William Stein wrote:
> For "fun", I just did
>
> /etc/init.d/apache2 restart
> /etc/init.d/postgresql restart
>
> which might impact something...
Has anyone checked trac's logs to see *why* trac is slow? With fully
automated things like patchbots, it wouldn't surprise m
Benjamin Jones writes:
> On Wed, Jun 13, 2012 at 2:08 PM, Starx wrote:
>>> To fix the patchbot problem, you can always run a patchbot
>>> instance yourself on this particular ticket and the new results will
>>> show up.
>>
>> Can I? I assumed I would need some kind of admin access to fiddle
>> w
