500 error on TestDriven

6 views
Skip to first unread message

Ken Kuhlman

unread,
Jun 4, 2007, 10:53:44 PM6/4/07
to doc...@googlegroups.com
It's sort of ironic, but the page on test driven development:

http://docudo.webfactional.com/current/TestDriven
is producing the stack trace below.


Good job getting Docudo up and running again.
-Ken

Page handler: <bound method Root.default of <docudo.controllers.Root object at 0xb769cfac>>
Traceback (most recent call last):
File "/home2/docudo/lib/python2.4/CherryPy-
2.2.1-py2.4.egg/cherrypy/_cphttptools.py", line 105, in _run
self.main()
File "/home2/docudo/lib/python2.4/CherryPy- 2.2.1-py2.4.egg/cherrypy/_cphttptools.py", line 254, in main
body = page_handler(*virtual_path, **
self.params)
File "<string>", line 3, in default
File "/home2/docudo/lib/python2.4/TurboGears- 1.0-py2.4.egg/turbogears/controllers.py", line 334, in expose
output = database.run_with_transaction
(
File "<string>", line 5, in run_with_transaction
File "/home2/docudo/lib/python2.4/TurboGears- 1.0-py2.4.egg/turbogears/database.py", line 260, in so_rwt
retval = func(*args, **kw)

File "<string>", line 5, in _expose
File "/home2/docudo/lib/python2.4/TurboGears-1.0-py2.4.egg /turbogears/controllers.py", line 351, in <lambda>
mapping, fragment, args, kw)))

File "/home2/docudo/lib/python2.4/TurboGears-1.0-py2.4.egg/turbogears/controllers.py", line 378, in _execute_func
output = errorhandling.try_call(func, *args, **kw)
File "/home2/docudo/lib/python2.4/TurboGears-
1.0-py2.4.egg/turbogears/errorhandling.py", line 73, in try_call
return func(self, *args, **kw)
File "/home2/docudo/webapps/tg/docudo/controllers.py", line 194, in default
doc = Document(page_id,version)

File "/home2/docudo/webapps/tg/docudo/document.py", line 36, in __init__
self.load()
File "/home2/docudo/webapps/tg/docudo/document.py", line 44, in load
self.load_properties()

File "/home2/docudo/webapps/tg/docudo/document.py", line 69, in load_properties
raw_enabled=False))["html_body"]
File "/usr/local/lib/python2.4/site-packages/docutils/core.py", line 431, in publish_parts

enable_exit_status=enable_exit_status)
File "/usr/local/lib/python2.4/site-packages/docutils/core.py", line 612, in publish_programmatically
output = pub.publish(enable_exit_status=enable_exit_status)

File "/usr/local/lib/python2.4/site-packages/docutils/core.py", line 203, in publish
self.apply_transforms()
File "/usr/local/lib/python2.4/site-packages/docutils/core.py", line 184, in apply_transforms

self.document.transformer.apply_transforms()
File "/usr/local/lib/python2.4/site-packages/docutils/transforms/__init__.py", line 171, in apply_transforms
transform.apply(**kwargs)
File "/usr/local/lib/python2.4/site-packages/docutils/transforms/references.py", line 832, in apply

self.document.walk(visitor)
File "/usr/local/lib/python2.4/site-packages/docutils/nodes.py", line 140, in walk
if child.walk(visitor):
File "/usr/local/lib/python2.4/site-packages/docutils/nodes.py", line 140, in walk

if child.walk(visitor):
File "/usr/local/lib/python2.4/site-packages/docutils/nodes.py", line 132, in walk
visitor.dispatch_visit(self)
File "/usr/local/lib/python2.4/site-packages/docutils/nodes.py", line 1535, in dispatch_visit

return method(node)
File "/usr/local/lib/python2.4/site-packages/docutils/transforms/references.py", line 883, in visit_reference
base_node=node)
File "/usr/local/lib/python2.4/site-packages/docutils/utils.py", line 207, in error

return self.system_message(3, *args, **kwargs)
File "/usr/local/lib/python2.4/site-packages/docutils/utils.py", line 171, in system_message
print >>self.stream, msgtext

IOError: [Errno 5] Input/output error

Kevin Horn

unread,
Jun 5, 2007, 8:56:58 PM6/5/07
to doc...@googlegroups.com
Thanks Ken!

I noticed this as well, but haven't had time to look into it yet.  I'll get to it as soon as I can.  In the meantime, if anyone else has any ideas as to what's causing this, feel free to post them here.

Kevin Horn

Kevin Horn

unread,
Jun 12, 2007, 11:09:43 PM6/12/07
to doc...@googlegroups.com
I still haven't had time to look into this properly, but:
- it's coming from docutils
- its an IOError
- its choking on a print statement
print >>self.stream
, msgtext
My guess is that self.stream isn't valid...but I haven't dug through the docutils source to figure anything further out, so it _is_ only a guess.

Suggestions welcome.

Kevin Horn

Kevin Horn

unread,
Jun 12, 2007, 11:24:52 PM6/12/07
to doc...@googlegroups.com
OK, digging into docutils a little deeper...it appears that the page itself has markup errors in it (or is causing docutils to throw some other error).  When docutils tries to print this error, it can't (for some reason) and thus the traceback we see, rather than an error message.

Opening a ticket in trac... #31

Kevin Horn
Reply all
Reply to author
Forward
0 new messages