Error in Timeline view

[anonymous]

Hi,

We have been using Trac for some time and it is a wonderful product. We have set up a project with multiple customized fields. However, when we click on the "Timeline" link, it throws an error. We notice this this occur on certain date range in the Timeline view only (perhaps related to some data).

Below is the traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 206, in handler
    dispatch_request(mpr.path_info, mpr, env)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/trac/Timeline.py", line 140, in process_request
    filters)
  File "/usr/lib/python2.4/site-packages/trac/ticket/web_ui.py", line 280, in get_timeline_events
    for t, id, resolution, status, type, message, author, summary \
  File "/usr/lib/python2.4/site-packages/trac/db.py", line 83, in __iter__
    row = self.cursor.fetchone()
  File "/usr/lib/python2.4/site-packages/pyPgSQL/PgSQL.py", line 3119, in fetchone
    raise Error, \
Error: fetchone() failed - cursor does not contain a result.

[ngwp99@…]

Just to add to this ticket, the error above occurs when we select the option to display "Tickets changes" in the Timeline screen. If we exclude that option and choose to display other changes (Milestones, Repository checkins, Wiki changes), the screen will display correctly.

[Matthew Good]

What version of pyPgSql is installed? Try upgrading it, since this appears to be a bug in pyPgSql. If this still occurrs with the latest pyPgSql, then I think it will need confirmed and reported to pyPgSql.

It looks like pyPgSql is throwing an error trying to fetch the results when the previous query returned 0 rows. This error should be raised if the query did not have a result (like an insert or update), but should not be for a select with an empty result: ​http://sourceforge.net/tracker/index.php?func=detail&aid=562738&group_id=16528&atid=116528

[ngwp99@…]

I have just upgraded to pyPgSql-2.5.1 on postgreSQL 8.0.8, and the error still occur.

[Christian Boos]

Perhaps a malformed query involving the custom fields? It's probably worth investigating. If the reporter is still listening, maybe he could provide us:

• with his custom fields configuration
• with the data corresponding to the ticket change triggering the failure (if this can be identified by narrowing the timeline interval triggering the exception)

[anonymous]

on windows + trac 0.10.3 + python 2.4 I also can't use pyPgSql-2.5.1 as well as pyPgSql-2.5.0, but pyPgSQL-pre2.5-20050926.win32-py2.4.exe is well.

[anonymous]

Replying to anonymous:

on windows + trac 0.10.3 + python 2.4 I also can't use pyPgSql-2.5.1 as well as pyPgSql-2.5.0, but pyPgSQL-pre2.5-20050926.win32-py2.4.exe is well.

still me:

in trac_parent uri it displays : Error (DLL load failed: The specified module could not be found.)

[Christian Boos]

Without additional info which could make it possible to reproduce the issue, we probably can't do anything here.

[anonymous]

Replying to ngwp99@yahoo.com:

I have just upgraded to pyPgSql-2.5.1 on postgreSQL 8.0.8, and the error still occur.

[Christian Boos]

(clearing report:35)