TracBurndown-01.05.10-py2.4.egg error

[anonymous]

Upon installing the plugin from source and deploying the following egg (TracBurndown-01.05.10-py2.4.egg) I receive the following error upon clicking on the "Burndown" menu item:

Traceback (most recent call last):
  File "C:\Python24\lib\site-packages\trac-0.10-py2.4.egg\trac\web\main.py", line 356, in dispatch_request
    dispatcher.dispatch(req)
  File "C:\Python24\lib\site-packages\trac-0.10-py2.4.egg\trac\web\main.py", line 224, in dispatch
    resp = chosen_handler.process_request(req)
  File "build\bdist.win32\egg\burndown\burndown.py", line 174, in process_request
  File "build\bdist.win32\egg\burndown\burndown.py", line 190, in getBurndownData
  File "C:\Python24\lib\site-packages\trac-0.10-py2.4.egg\trac\db\util.py", line 48, in execute
    return self.cursor.execute(sql)
  File "C:\Python24\lib\site-packages\trac-0.10-py2.4.egg\trac\db\sqlite_backend.py", line 56, in execute
    args or [])
  File "C:\Python24\lib\site-packages\trac-0.10-py2.4.egg\trac\db\sqlite_backend.py", line 48, in _rollback_on_error
    return function(self, *args, **kwargs)
OperationalError: near "s": syntax error

Have I done something incorrectly?

The "timingandestimationplugin 0.3.7" is installed and has no issues.

[Noah Kantrowitz]

Fixing formatting.

[Sam Bloomquist]

Are other people having trouble with py2.4? I myself am using it with 2.3 and am not having this problem. I don't have a trac instance with 2.4 set up to test this right now. Could someone else help out with this one?

[anonymous]

I'm seeing the same error which clicking on the burndown link, but with Python2.3:

Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 406, in dispatch_request

dispatcher.dispatch(req)

File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 237, in dispatch

resp = chosen_handler.process_request(req)

File "/var/trac/engage/plugins/TracBurndown-01.08.10-py2.3.egg/burndown/burndown.py", line 195, in process_request File "/var/trac/engage/plugins/TracBurndown-01.08.10-py2.3.egg/burndown/burndown.py", line 211, in get_burndown_data File "/usr/lib/python2.3/site-packages/trac/db/util.py", line 51, in execute

return self.cursor.execute(sql)

File "/usr/lib/python2.3/site-packages/trac/db/sqlite_backend.py", line 56, in execute

args or [])

File "/usr/lib/python2.3/site-packages/trac/db/sqlite_backend.py", line 48, in _rollback_on_error

return function(self, *args, kwargs)

OperationalError: near "s": syntax error

[anonymous]

An row in the component table had an apostrophe in the name. I ran sqlite3 against the db and renamed it:

update component set name = "Dr. Grays Pages" where name = "Dr. Gray's Pages";

And that solved the problem I "me too"d above.

Jamie

[daan]

(In [5058]) Release of version 1.9.1 of the Trac Scrum burndown plugin. See ​http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released for more information.

A new version of the Scrum Burndown plugin for Trac is released, bringing compatibility for PostgreSQL, MySQL, Trac 0.11.2.1, and many bug fixes. Upgrading is recommended.

New features The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Trac 0.11.2.1 Python 2.4 and Python 2.5. Additional to the previous SQLite compatibility, support for both PostgreSQL 8.3 and MySQL 5 has been added.

The following issues are fixed:

• Fixes #1462 better control of milestone: a way to ‘reset’ a milestone
• Fixes #1217 database upgrade fails after installing latest scrumburndownplugin
• Fixes #2476 Error: ‘line_graph’ is undefined - stop graph from displaying
• Fixes #1730 couldn’t upgrade
• Fixes #2729 Error while running under PostgreSQL
• Fixes #3102 burndown_job.py fails INSERT NULL id
• Fixes #1909 Overshooting estimate reduces remaining effort while ticket is open
• Fixes #1189 TracBurndown-01.05.10-py2.4.egg error
• Fixes #1800 No chart when clicking Burndown chart button.
• Fixes #4047 AttributeError: ‘NoneType’ object has no attribute ‘getValue’
• Fixes #2224 Changing ticket component causes removal from burndown
• Fixes #2562 Creating a new component breaks the burndown graphic for “All Components”
• Fixes #4222 Install fails on mysql
• Fixes #2218 ScrumBurndownPlugin, trac 0.10.4, mysql