I introduced this bug with the previous bugfix. I immediately fixed the new
bug, but then forgot to check it in, which I just did now.
Can you 'cvs update' and try again?
(Here's another case where an automated regression test suite at 5AM would
have helped (although that's no excuse for introducing bugs)).
At 02:27 PM 1/27/2001 -0500, Chris AtLee wrote:
>I just did a 'cvs update -dp', and now whenever I try and access a file I
>get the following error:
>Traceback (innermost last):
> File "/usr/lib/python1.5/threading.py", line 376, in __bootstrap
> File "/usr/lib/python1.5/threading.py", line 364, in run
> apply(self.__target, self.__args, self.__kwargs)
> File "ThreadedAppServer.py", line 124, in threadloop
> File "ThreadedAppServer.py", line 260, in handleRequest
> transaction = self.server._app.dispatchRawRequest(dict)
> File "Application.py", line 279, in dispatchRawRequest
> return self.dispatchRequest(self.createRequestForDict(newRequestDict))
> File "Application.py", line 323, in dispatchRequest
> path = request.serverSidePath()
> File "HTTPRequest.py", line 208, in serverSidePath
> self._serverSidePath = app.serverSidePathForRequest(self)
> File "Application.py", line 985, in serverSidePathForRequest
> raise AssertionError, "Unexpected if-else fall through."
>AssertionError: Unexpected if-else fall through.