Edgewall Software
Modify

Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#5041 closed defect (worksforme)

unable to edit milestone info

Reported by: anonymous Owned by: Matthew Good
Priority: high Milestone:
Component: report system Version: 0.9.6
Severity: major Keywords: milestone
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Emmanuel Blot)

I have created Ashoka0.12.0 milestone.

I have also made it genetic for the users that they can get all the details of Ashoka 0.12.0 milestone. I have done wiki some formating to get the output.The format which i have used is

:== Ashoka 0.12.0 Status ==

Details on All Tickets for Ashoka 0.12.0

Current Tickets in this build: No results

I have also created the status link in which it presents the results in the graphical format that How many tickets are closed ? and the tickets which are Active.

But when i try to generate it in a graphical format i.e. edit Milestone info it gives me the following error message.

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/standalone.py", line 303, in _do_trac_req
    dispatch_request(path_info, req, env)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/roadmap.py", line 355, in process_request
    self._do_save(req, db, milestone)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/roadmap.py", line 411, in _do_save
    milestone.update()
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/model.py", line 594, in update
    (self.name, self.due, self.completed, self.description,
  File "/usr/local/lib/python2.4/site-packages/trac/db.py", line 219, in execute
    args or [])
  File "/usr/local/lib/python2.4/site-packages/trac/db.py", line 211, in _rollback_on_error
    return function(self, *args, **kwargs)
OperationalError: column name is not unique

Attachments (1)

test-failures-on-dapper.txt (5.7 KB ) - added by Tim Hatch 17 years ago.
Failure log from unittests when run with Dapper's sqlite 3.2.8

Download all attachments as: .zip

Change History (5)

comment:1 by Emmanuel Blot, 18 years ago

Description: modified (diff)
Keywords: unable to edit info removed
Priority: highesthigh
Severity: blockermajor

Which version of Trac are you using, and which database backend is used (SQLite, PostgreSQL, MySQL) ?

comment:2 by anonymous, 17 years ago

Resolution: worksforme
Status: newclosed
Version: 0.9.6

The original ticket's traceback matches against Trac 0.9.4-0.9.6.

I just encountered this error in the unit tests (post-0.11b2) on Ubuntu Dapper using its pysqlite. Ten of the tests fail with the same exception.

  • python 2.4.3-0ubuntu6.1
  • libsqlite3-0 3.2.8-1ubuntu1
  • python-pysqlite2 2.0.5-1ubuntu1

There are a lot of deps for the edgy packages, so I just removed the existing sqlite3 and pysqlite2, installed them from source and the errors went away. I'm therefore closing as worksforme since:

  1. the packages in Dapper haven't been updated since April 2006
  2. this error has unittests that detect it, so consequently…
  3. we know it's not an issue on any other platform

The test failures are too wide for the page so I'm attaching them separately.

by Tim Hatch, 17 years ago

Attachment: test-failures-on-dapper.txt added

Failure log from unittests when run with Dapper's sqlite 3.2.8

comment:3 by Tim Hatch, 17 years ago

Oops, forgot to log in before closing. That was me up there.

comment:4 by Christian Boos, 17 years ago

Milestone: 0.12

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Matthew Good.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Matthew Good to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.