Edgewall Software

Changes between Version 18 and Version 19 of MostFrequentDuplicates


Ignore:
Timestamp:
May 20, 2015, 11:06:40 PM (9 years ago)
Author:
figaro
Comment:

Moved most frequent duplicate to top

Legend:

Unmodified
Added
Removed
Modified

  • MostFrequentDuplicates

    v18 v19  
    22
    33We have lots of tickets and lots of users, so some bugs will be reported multiple times. Here's a short list of the issues with a pathologically high duplicate rate:
     4
     5=== #3446: '''!OperationalError: `database is locked`''' ([search:"!OperationalError: database is locked" see all])
     6
     7This used to be an issue when using Trac in combination with the SQLite database. The problem has been fixed in Trac version 0.12 and above.
     8
     9More information on this issue can be found on the following pages:
     10
     11 * http://trac.edgewall.org/ticket/3446#comment:39
     12 * wiki:PySqlite#OperationalError:databaseislocked
     13 * [https://www.sqlite.org/rescode.html#locked SQLite (6) SQLITE_LOCKED]
     14
     15A more scary variant of this issue is #4929, where the lock situation seems to persist and needs a server restart. This situation is rare, however.
    416
    517=== #3839: '''Authentication information not available.''' ([search:'Authentication information not available.' see all])
    … …  
    1224
    1325A problem inherent to the SWIG-based Subversion bindings when they are used from multiple Python interpreters in the same process. That situation can happen when the Trac server front-end is mod_python or mod_wsgi. See TracSubversion#instance-dict-restricted-mode for the mod_python instructions and [mod-wsgi:IntegrationWithTrac] for the mod_wsgi instructions.
    14 
    15 === #3446: '''Rate of `database is locked` errors is too high''' ([search:"!OperationalError: database is locked" see all])
    16 
    17 This used to be an issue when using Trac in combination with the SQLite database. The problem has been fixed in Trac version 0.12 and above.
    18 
    19 More information on this issue can be found on the following pages:
    20 
    21  * http://trac.edgewall.org/ticket/3446#comment:39
    22  * wiki:PySqlite#OperationalError:databaseislocked
    23  * [https://www.sqlite.org/rescode.html#locked SQLite (6) SQLITE_LOCKED]
    24 
    25 A more scary variant of this issue is #4929, where the lock situation seems to persist and needs a server restart. This situation is rare, however.
    2626
    2727=== #4365: '''"HTMLParseError: bad end tag"''' ([search:'"HTMLParseError: bad end tag"' see all])