Ondřej Čertík ondrej.certik at gmail.com writes:
When I access tickets, for example:
http://projects.scipy.org/numpy/ticket/2185
then sometimes I get:
Trac detected an internal error:
OperationalError: database is locked
For example yesterday. A refresh in about a minute fixed the
On Fri, Aug 31, 2012 at 9:35 AM, Pauli Virtanen p...@iki.fi wrote:
Ondřej Čertík ondrej.certik at gmail.com writes:
When I access tickets, for example:
http://projects.scipy.org/numpy/ticket/2185
then sometimes I get:
Trac detected an internal error:
OperationalError: database is locked
On Fri, Aug 31, 2012 at 11:35 AM, Pauli Virtanen p...@iki.fi wrote:
Ondřej Čertík ondrej.certik at gmail.com writes:
When I access tickets, for example:
http://projects.scipy.org/numpy/ticket/2185
then sometimes I get:
Trac detected an internal error:
OperationalError: database is locked
01.09.2012 00:08, Ognen Duzlevski kirjoitti:
[clip]
I personally think moving away from Trac (which IMHO is bloated and
awkward in addition to having a very weird way of being administered)
would be a better idea.
Yes, moving away from Trac is planned, both for Numpy and Scipy. Also
agreed on
Hi,
When I access tickets, for example:
http://projects.scipy.org/numpy/ticket/2185
then sometimes I get:
Trac detected an internal error:
OperationalError: database is locked
For example yesterday. A refresh in about a minute fixed the problem.
Today it still lasts at the moment.
Ondrej
