Context Navigation

Changes between Version 13 and Version 14 of MostFrequentDuplicates

Timestamp:: May 9, 2015, 10:12:23 AM (9 years ago)
Author:: figaro
Comment:: Rearranged paragraphs to maintain consistency with Trac versions being affected.

Legend:

: Unmodified
: Added
: Removed
: Modified

MostFrequentDuplicates

-              v13
+              v14
 = Most Frequently Reported Bugs in Trac
+We have lots of tickets and lots of users, so it's not unlikely that sometimes a bug will be reported twice, or thrice, or ... dozens of times for some!
+Here's a short list of the issues with a pathologically high duplicate rate:
+=== #9403: '''!ValueError: timestamp out of range for platform time_t''' ([search:'"ValueError: timestamp out of range for platform time_t"' see all])
+This is not a bug, but an installation issue. This is typically seen when upgrading a Trac installation to 0.12 then downgrading to 0.11 again. During the upgrade, the timestamps previously stored as number of seconds since Unix epoch were converted to microseconds. If the Trac 0.11 code sees that database again, it won't be able to deal with these larger values correctly and will throw this error. Solution: make sure you're using 0.12, or at worst, revert to the backup database generated during the upgrade.
+=== #5028: '''!TracError: Unsupported version control system "svn"''' ([search:'!TracError: Unsupported version control system "svn"' see all])
+An installation issue. The error means that for some reason, the Python bindings to the Subversion libraries couldn't be found or loaded. The TracSubversion page provides detailed [TracSubversion#Troubleshooting troubleshooting] information. In Trac [milestone:0.11], if this problem happens, it will only be reported as a warning for non-repository related pages.
+The error message has been improved, so this issue is less frequently reported now (#6796).
+We 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:
 === #3839: '''Authentication information not available.''' ([search:'Authentication information not available.' see all])
+This message is frequently encountered, which simply indicates that no authentication information has been setup for the server. How to actually set it depends on the actual form of the deployment, as mentioned in the [TracFaq#WhataboutthisAuthenticationinformationnotavailable.error FAQ]. This issue is documented in TracInstall and other places.
+This message indicates that no authentication information has been setup for the server. How to actually set it depends on the actual form of the deployment, as mentioned in the [TracFaq#WhataboutthisAuthenticationinformationnotavailable.error FAQ].
+This issue and its troubleshooting steps are documented in TracInstall and other places.
 === #3371: '''!RuntimeError: instance.!__dict!__ not accessible in restricted mode''' ([search:"!RuntimeError: instance.__dict__ not accessible in restricted mode" see all])
 …
 === #3446: '''Rate of `database is locked` errors is too high''' ([search:"!OperationalError: database is locked" see all])
 This used to be a plague with the SQLite database backend, but it seems that things improved over time and this once !#1 duplicate bug is less frequent those days. ''The problem should even be completely gone with 0.11.6 or 0.12dev''. A more scary variant of #3446 is #4929, where the lock situation seems to persist and needs a server restart (rare).
+This used to be a plague with the SQLite database backend, but it seems that things improved over time and this once !#1 duplicate bug is less frequent those days. The problem has been fixed in Trac version 0.12 and above.
+=== #4311: ''''cStringIO.StringO' object has no attribute 'len'''' ([search:"'cStringIO.StringO' object has no attribute 'len'" see all])
+Attaching files won't work with Trac < 0.10.4 and Python 2.5. This was a simple compatibility issue with Python 2.5, which was reported and fixed. Upgrading to the newest version solves this issue.
+A more scary variant of #3446 is #4929, where the lock situation seems to persist and needs a server restart (rare).
 === #4365: '''"HTMLParseError: bad end tag"''' ([search:'"HTMLParseError: bad end tag"' see all])
 SilverCity has a bug which is fixed in its version 0.9.7. SilverCity on t.e.o needs to be updated.
+SilverCity has a bug which is fixed in its version 0.9.7. SilverCity on t.e.o needs to be updated, although support for it has been removed as of Trac [milestone:1.1.3].
 === #6976 '''!TypeError: cannot concatenate 'str' and '!NoneType' objects''' ([search:"cannot concatenate 'str' and 'NoneType' objects" see all])
 This is a bug in the TH:GitPlugin for Trac on nonexistent paths, see TH:ticket:2671.
+=== #9403: '''!ValueError: timestamp out of range for platform time_t''' ([search:'"ValueError: timestamp out of range for platform time_t"' see all])
+This is not a bug, but an installation issue. This is typically seen when upgrading a Trac installation to 0.12 then downgrading to 0.11 again. During the upgrade, the timestamps previously stored as number of seconds since Unix epoch were converted to microseconds. If the Trac 0.11 code sees that database again, it won't be able to deal with these larger values correctly and will throw this error.
+Make sure you're using Trac 0.12, or at worst, revert to the backup database generated during the upgrade.
+=== #5028: '''!TracError: Unsupported version control system "svn"''' ([search:'!TracError: Unsupported version control system "svn"' see all])
+This is an installation issue. The error means that for some reason, the Python bindings to the Subversion libraries couldn't be found or loaded. The error message has been improved, so this issue is less frequently reported now (#6796).
+The TracSubversion page provides detailed [TracSubversion#Troubleshooting troubleshooting] information. If this problem happens in Trac [milestone:0.11], it will only be reported as a warning for non-repository related pages.
+=== #4311: ''''cStringIO.StringO' object has no attribute 'len'''' ([search:"'cStringIO.StringO' object has no attribute 'len'" see all])
+Attaching files won't work with Trac < 0.10.4 and Python 2.5. This was a compatibility issue with Python 2.5, which was reported and fixed. Upgrade to the newest version of Trac.