corrupt cache produces unhelpful error messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpadlib |
Triaged
|
Low
|
Unassigned | ||
python-launchpadlib (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: python-launchpadlib
My launchpadlib scripts on a server in the data center were not running at all and I was receiving the following error:
The authorization page (https:/
browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press <Enter>
to finish the authentication process.
Traceback (most recent call last):
File "package-
launchpad = Launchpad.
File "/usr/lib/
credentials
File "/usr/lib/
raise HTTPError(response, content)
launchpadlib.
However, my credentials were good and I had successfully used the same ones on my system at home. While investigating the problem I received this traceback:
brian@cranberry:~$ python
Python 2.5.2 (r252:60911, Jul 22 2009, 15:33:10)
[GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.path.
'/home/
>>> from launchpadlib.
>>> from launchpadlib.errors import HTTPError
>>> from launchpadlib.
>>> credentials = Credentials()
>>> credfile = os.path.
>>> credentials.
>>> cachedir = os.path.
>>> launchpad = Launchpad(
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/
self._wadl = self._browser.
File "/usr/lib/
return Application(
File "/usr/lib/
self.doc = ET.fromstring(
File "<string>", line 86, in XML
SyntaxError: no element found: line 14374, column 4
After some lucky guesswork I moved aside my cachedir and was able to successfully use launchpadlib again. Determining the source of the problem was very cryptic and I think the error messages could be more informative.
I was using python-launchpadlib version 0.2~bzr25-
Changed in python-launchpadlib (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
The corrupt cache itself was presumably caused by bug 459418.