Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#1864 closed defect (fixed)

RuntimeError: maximum recursion depth exceeded while calling a Python object

Reported by: mlennert Owned by: strk
Priority: major Milestone:
Component: SysAdmin/Trac Keywords:


Trying to display, I get the following error:

Trac detected an internal error:

RuntimeError: maximum recursion depth exceeded while calling a Python object

here was an internal error in Trac. It is recommended that you notify your local Trac administrator with the information needed to reproduce the issue.

To that end, you could [Create] a ticket.

[Create] is a button, but when I push it I get:

Request-URI Too Large

The requested URL's length exceeds the capacity limit for this server.

which is not surprising as the URL is:``%2C+Trac+issued+an+internal+error.%0D%0A%0D%0A%27%27%28please+provide+additional+details+here%29%27%27%0D%0A%0D%0ARequest+parameters%3A%0D%0A{{{%0D%0A{}%0D%0A}}}%0D%0A%0D%0AUser+agent%3A+`Mozilla%2F5.0+%28X11%3B+Linux+x86_64%3B+rv%3A45.0%29+Gecko%2F20100101+Firefox%2F45.0`%0D%0A%0D%0A%3D%3D%3D%3D+System+Information+%3D%3D%3D%3D%0D%0A%27%27System+information+not+available%27%27%0D%0A%0D%0A%3D%3D%3D%3D+Enabled+Plugins+%3D%3D%3D%3D%0D%0A%27%27Plugin+information+not+available%27%27%0D%0A%0D%0A%3D%3D%3D%3D+Interface+Customization+%3D%3D%3D%3D%0D%0A%27%27Interface+customization+information+not+available%27%27%0D%0A%0D%0A%3D%3D%3D%3D+Python+Traceback+%3D%3D%3D%3D%0D%0A{{{[mimetype][1]}}}&create=Create#

Change History (9)

comment:1 by mlennert, 7 years ago

Priority: normalmajor
Type: taskdefect

comment:2 by mlennert, 7 years ago

Component: Systems AdminTrac
Owner: changed from sac@… to strk

comment:3 by strk, 7 years ago

Status: newassigned

I noticed:!topic/trac-users/yaMesS3G6uo Seems to be only working in grass, does it happen when trying to open/view *any* .py file ?

comment:6 by strk, 7 years ago

This happened after Trac upgrade to 1.2 (#1863) Upstream ticket:

comment:7 by strk, 7 years ago

Uninstalling python-pygments seems to have fixed this. At the cost (I'm afraid) of lost syntax highlighting. Could re-install a newer version...

comment:8 by strk, 7 years ago

Resolution: fixed
Status: assignedclosed

It turns out that by uninstalling the package-managed python-pygments, which was at version 1.3.1, a more recent pygments library was revealed (2.2.0). Evidently the package was shadowing the new one. So syntax highlight is available.

Closing, and looking forward to next issue.

comment:9 by strk, 7 years ago

For the record: the bug was fixed upstream (thank you OSGeo for helping with the development of free software code tracking solutions !) --

Note: See TracTickets for help on using tickets.