Modify

Opened 7 years ago

Closed 6 years ago

#2330 closed defect (fixed)

How to enable ScrumBurndownPlugin in 0.11b1

Reported by: anonymous Owned by: daan
Priority: high Component: ScrumBurndownPlugin
Severity: major Keywords: ScrumBurndownPlugin Error
Cc: Trac Release: 0.11

Description

I recevied these error messages, after I enabled ScrumBurndownPlugin component in trac.ini file and execute trac-admin ./project-name upgrade.

Traceback (most recent call last):
  File "/.../bin/trac-admin", line 7, in ?
    sys.exit(
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/admin/console.py", line 1194, in run
    return admin.onecmd(command)
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/admin/console.py", line 102, in onecmd
    rv = cmd.Cmd.onecmd(self, line) or 0
  File "/.../lib/python2.4/cmd.py", line 219, in onecmd
    return func(arg)
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/admin/console.py", line 1105, in do_upgrade
    self.__env.upgrade(backup=do_backup)
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/env.py", line 427, in upgrade
    if participant.environment_needs_upgrade(db):
  File "../bdist.linux-i686/egg/timingandestimationplugin/api.py", line 232, in environment_needs_upgrade
  File "../bdist.linux-i686/egg/timingandestimationplugin/api.py", line 129, in reports_need_upgrade
  File "../bdist.linux-i686/egg/timingandestimationplugin/reportmanager.py", line 16, in __init__
  File "../bdist.linux-i686/egg/timingandestimationplugin/reportmanager.py", line 22, in upgrade
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/.../lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
psycopg2.ProgrammingError: current transaction is aborted, commands ignored until end of transaction block

Who knows what's going on here?

Attachments (0)

Change History (3)

comment:1 Changed 7 years ago by anonymous

I found putting a db.commt(); in burndown/burndown.py works. i.e., make it like so:

    def upgrade_environment(self, db):
        cursor = db.cursor()

        needsCreate = False
        try:
            cursor.execute('SELECT * FROM burndown LIMIT 1')
        except:
            needsCreate = True
        db.commit();

comment:2 Changed 6 years ago by daan

  • Owner changed from sambloomquist to daan

comment:3 Changed 6 years ago by daan

  • Resolution set to fixed
  • Status changed from new to closed

(In [4736]) Release of version 1.9 of the Trac Scrum burndown plugin. See http://stuq.nl/weblog/2008-11-04/scrum-burndown-plugin-19-released for more information.

The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Python 2.4 and Python 2.5.

Issues fixed: Fixed #3498 Incompatible with Genshi 0.5 Fixed #1743 No support for 0.11 version on trac Fixed #2330 How to enable ScrumBurndownPlugin in 0.11b1 Fixed #1590 printing to stderr causes svn post-commit hook to crash Fixed #1510 Porting to Trac 0.11 and Genshi templates Fixed #2936 problem installing plugin Fixed #1668 Environment Not Found Fixed #1472 URL Not Found when click Burndown menu Fixed #3017 Trac 0.11 - Burndown Chart does not show tickets with status 'accepted'

Add Comment

Modify Ticket

Action
as closed The owner will remain daan.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.