OSError when trying to access http://localhost:8123/provisioning/ #335

New Issue

tahoe-lafs · 2008-03-08T22:41:51Z

dreid commented

2008-03-08 22:41:51 +00:00

It seems nevow/loaders.py isn't prepared for you template to be inside a zipfile. It tries to call os.getmtime on the path below.

<type 'exceptions.OSError'>: [Errno 20] Not a directory: '/Volumes/Users/dreid/Downloads/Allmydata Tahoe.app/Contents/Resources/lib/python2.5/site-packages.zip/allmydata/web/provisioning.xhtml'

It seems nevow/loaders.py isn't prepared for you template to be inside a zipfile. It tries to call os.getmtime on the path below. ``` <type 'exceptions.OSError'>: [Errno 20] Not a directory: '/Volumes/Users/dreid/Downloads/Allmydata Tahoe.app/Contents/Resources/lib/python2.5/site-packages.zip/allmydata/web/provisioning.xhtml' ```

tahoe-lafs added the

labels 2008-03-08 22:41:51 +00:00

tahoe-lafs added this to the undecided milestone 2008-03-08 22:41:51 +00:00

dreid commented

2008-03-09 02:38:35 +00:00

One option would be to use a py2app recipe to specify that the allmydata python package isn't to be install in the site-packages.zip.

http://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html#id27 I think has the relevant information.

One option would be to use a py2app recipe to specify that the allmydata python package isn't to be install in the site-packages.zip. <http://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html#id27> I think has the relevant information.

dreid commented

2008-03-09 04:27:49 +00:00

Attachment provisioning_getxmlfile.patch (673 bytes) added

**Attachment** provisioning_getxmlfile.patch (673 bytes) added

provisioning_getxmlfile.patch

673 B

dreid commented

2008-03-09 04:29:11 +00:00

The attached patch fixes the problem, as you can see allmydata.provisioning.getxmlfile is not using resource_filename as allmydata.web.common.getxmlfile is. I've simply removed the getxmlfile from allmydata.provisioning and this appears to fix the bug.

zooko commented

2008-03-09 16:46:37 +00:00

The patch looks good, but before committing it I want to have an automated test of it. After chatting with dreid and with exarkun on IRC, I think that the best way to automatically test it is to add a step to buildbot called PrivateInstall, and then run the unit tests on the source code thus locally installed.

The patch looks good, but before committing it I want to have an automated test of it. After chatting with dreid and with exarkun on IRC, I think that the best way to automatically test it is to add a step to buildbot called `PrivateInstall`, and then run the unit tests on the source code thus locally installed.

zooko commented

2008-03-09 16:47:23 +00:00

See related issue http://divmod.org/trac/ticket/2527

See related issue <http://divmod.org/trac/ticket/2527>

zooko commented

2008-03-10 23:08:53 +00:00

I went ahead and applied dreid's patch changeset:1ddeb88e9b312185, to fix the bug in v0.9.0, but I still want automated tests showing that this stuff works when it is being run out of a py2exe or py2app package.