Opened 17 years ago
Closed 17 years ago
#249 closed defect (duplicate)
Build Status errors on build_config access
Reported by: | rkdecampo@… | Owned by: | cmlenz |
---|---|---|---|
Priority: | minor | Milestone: | 0.6 |
Component: | General | Version: | dev |
Keywords: | Cc: | ||
Operating System: | Windows |
Description
I am trying to install and use Bitten on an existing Trac 0.10.4 installation. The version of Bitten appears to be 0.6dev_r519.
I am seeing the following error message, when I access the Build Status page. The message is similar to ticket {198}, however I do have build configuration.
Traceback (most recent call last):
File "C:\Python24\lib\site-packages\trac\web\main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "C:\Python24\lib\site-packages\trac\web\main.py", line 237, in dispatch
resp = chosen_handler.process_request(req)
File "c:\python24\lib\site-packages\bitten-0.6dev_r519-py2.4.egg\bitten\web_ui.py", line 128, in process_request
self._render_overview(req)
File "c:\python24\lib\site-packages\bitten-0.6dev_r519-py2.4.egg\bitten\web_ui.py", line 143, in _render_overview
for idx, config in enumerate(configs):
File "c:\python24\lib\site-packages\bitten-0.6dev_r519-py2.4.egg\bitten\model.py", line 167, in select
for name, path, active, recipe, min_rev, max_rev, label, description \
File "C:\Python24\lib\site-packages\trac\db\util.py", line 40, in iter
row = self.cursor.fetchone()
File "c:\python24\lib\site-packages\pyPgSQL\PgSQL.py", line 3158, in fetchone
raise Error, \
Error: fetchone() failed - cursor does not contain a result.
I checked the SQL which was running in the model.py source and it returns results when run directly in the database. I do have Trac configured to run within a specific schema in the database other than public, not sure if that is relevant. Also, I am running on Windows 2000.
I tried upgrading pyPgSQL to 2.5.1 but that has not helped. I'd appreciate any guidance.
Attachments (0)
Change History (3)
comment:1 Changed 17 years ago by rkdecampo@…
- Priority changed from major to minor
comment:2 Changed 17 years ago by thomas_mueller_ffb
duplicate of #198
comment:3 Changed 17 years ago by wbell
- Resolution set to duplicate
- Status changed from new to closed
Closing, #198 is a better description of the problem.
I managed to get beyond this by using psycops instead of pyPgSQL. I hadn't realized that pyPgSQL was no longer supported.