Page MenuHomePhabricator

"Download as PDF" on [[Purnia district]] throws "maximum recursion depth exceeded in cmp" error
Open, MediumPublic

Description

On this specific revision: https://en.wikipedia.org/w/index.php?title=Purnia_district&oldid=535741684

Abbreviated traceback:
File "/home/pp/local/lib/python2.6/site-packages/mwlib/refine/compat.py", line 188, in _change_classes _change_classes(x) File "/home/pp/local/lib/python2.6/site-packages/mwlib/refine/compat.py", line 188, in _change_classes _change_classes(x) File "/home/pp/local/lib/python2.6/site-packages/mwlib/refine/compat.py", line 33, in _change_classes if node.type==T.t_complex_table and node.children: RuntimeError: maximum recursion depth exceeded in cmp in function system, file /home/pp/local/bin/nslave.py, line 64

Note that this was reported as [[ticket:2013011710010252]]


Version: unspecified
Severity: major
URL: https://en.wikipedia.org/w/index.php?title=Special:Book&bookcmd=render_article&arttitle=Purnia+district&oldid=535741684&writer=rl

Details

Reference
bz44521

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:24 AM
bzimport added a project: Collection.
bzimport set Reference to bz44521.
bzimport added a subscriber: Unknown Object (MLST).

Thanks for reporting. I can confirm this.

I guess it's worth pointing out that this isn't just on that old revision, the current newest version also has the problem.

NewPP limit report
Preprocessor visited node count: 9526/1000000
Preprocessor generated node count: 59584/1500000
Post-expand include size: 138926/2048000 bytes
Template argument size: 44844/2048000 bytes
Highest expansion depth: 28/40
Expensive parser function count: 3/500

Looks like a bug specifically in PediaPress' server side parser code

(In reply to comment #2)

I guess it's worth pointing out that this isn't just on that old revision,
the
current newest version also has the problem.

Yes sorry, I was just specifying a revision to make sure no one edited the page and fixed it.

Looks like a bug specifically in PediaPress' server side parser code

Should this be reported upstream somewhere then?