On 12/11/05, W-Mark Kubacki <firstname.lastname@example.org> wrote:
> The error occurs with any version of Trac 0.9 series
> [snip config information]
> Steps to reproduce:
> 1. install these versions
> 2. make some commits to your SVN repository
> 3. go to Trac's page and try to open "timeline", "changeset viewer" or
> "code browser" (that is, any component interacting with Trac)
> You will either receive a blank page or a traceback.
> I've attached three tracebacks to this email, which (essentially) only
> differ in the last line containing that address.
> And there is something that makes me very puzzled:
> If you reloaded that page after having received that error (and
> traceback) everything is shown properly. - And yes, I've cleaned my
> browser's cache.
> Perhaps Trac has some sort of failback-code, I don't know. (Downgrading
> to SVN 1.2.3 makes the errors disappear.)
This looks like it's a bug related to interaction between Subversion's
python bindings and mod_python. I have not tested Subversion 1.3.0rc4
with mod_python yet, but I am hoping to do so soon. A few questions:
1) Are you using mod_python?
2) If you restart Apache, does it help?
3) If you switch Trac to CGI mode, does it still report the errors?
4) Do the test suites for the Python bindings and Trac pass when you
ran them via the command-line?
Running the test suite for the Python bindings:
From the Subversion directory, type make check-swig-py
Running the test suite for Trac:
From the Trac directory, type cp trac/test.py . && python test.py
David James -- http://www.cs.toronto.edu/~james
Received on Sun Dec 11 16:36:30 2005