Opened 15 years ago

Last modified 6 years ago

#4476 assigned defect

TracHours causes internal error after — at Initial Version

Reported by: chuntley@… Owned by: Jeff Hammel
Priority: normal Component: TracHoursPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

When I enable TracHours on a Trac that I migrated from sqlite to postgresql, I get and IndexError: list index out of range error every time I try to view a ticket.

The traceback is

File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 423, in _dispatch_request
  dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 219, in dispatch
  data, content_type)
File "/usr/lib/python2.4/site-packages/trac/web/chrome.py", line 690, in render_template
  stream |= self._filter_stream(req, method, filename, stream, data)
File "/usr/lib64/python2.4/site-packages/genshi/core.py", line 128, in __or__
  return Stream(_ensure(function(self)), serializer=self.serializer)
File "/usr/lib/python2.4/site-packages/trac/web/chrome.py", line 777, in inner
  data)
File "/usr/lib/python2.4/site-packages/TracHoursPlugin-0.2.-py2.4.egg/trachours/hours.py", line 244, in filter_stream
  stream = handler(req, stream, data)
File "/usr/lib/python2.4/site-packages/TracHoursPlugin-0.2.-py2.4.egg/trachours/hours.py", line 1017, in filter_ticket
  totalhours = [ field for field in data['fields'] if field['name'] == 'totalhours' ][0]

From reading elsewhere, it appears that this might have something to do with sequences in Postgresql not being updated properly in the migration. However, I thought I'd report it here because others seems might be having the same problem.

Change History (0)

Note: See TracTickets for help on using tickets.