Modify ↓
Opened 15 years ago
Closed 15 years ago
#8315 closed defect (invalid)
OperationalError: no such column: remaining_time
Reported by: | jan | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.11.4 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
How to Reproduce
While doing a POST operation on /ticket/4
, Trac issued an internal error.
(please provide additional details here)
Request parameters:
{'__FORM_TOKEN': u'2aa4627eafe3acb84219ed3e', 'action': u'resolve', 'action_resolve_resolve_resolution': u'worksforme', 'cnum': u'8', 'comment': u'', 'field_businessvalue': u'', 'field_cc': u'', 'field_component': u'component1', 'field_description': u"clarify how timed content and 'relative to one of the stories' defined\r\n\r\nQ) Is timing always relative to real world time? \r\n\r\ne.g. Tues 12th Episode 2 TXed so display this content\r\n\r\nor is timing relative to game time?\r\n\r\ne.g. 30 secs since entering this module\r\n\r\nThere are two issues here: one is content being delivered and published to dig it all based on the broadcast schedule of the television program. This means that from a CMS perspective - the broadcaster must be able to set a release date for the first show and the appropriate episodic content must be launched and implemented with the broadcasting of the show.\r\n\r\nThe query here is whether each broadcaster will be able to set their own schedule? As an example - the ABC is planning on broadcasting the show twice daily on two different channels - this would mean that over the course of a week, 5 shows will have been released, while the CBC may only release one episode a week. How do we allow for the broadcaster to control the release of the unique web based content? What safeguards can we put into play to ensure the timed release?\r\n\r\nThe second issue - and the one addressed in this query is Persistent attributes vs./and 'game time'. This issue/query will be addressed in a separate query.", 'field_drp_resources': u'', 'field_i_links': u'', 'field_keywords': u'', 'field_milestone': u'', 'field_o_links': u'', 'field_priority': u'should have', 'field_rd_points': u'', 'field_remaining_time': u'', 'field_reporter': u'michela', 'field_sprint': u'', 'field_story_priority': u'', 'field_summary': u'timed content - relative to one of the stories', 'field_type': u'requirement', 'field_version': u'', 'id': u'4', 'pane': u'edit', 'replyto': u'', 'submit': u'Submit changes', 'ts': u'2009-05-23 02:46:42+00:00'}
User Agent was: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10
System Information
Trac | 0.11.4
|
Python | 2.4.4 (#1, Apr 15 2008, 23:37:53) [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)]
|
setuptools | 0.6c9
|
SQLite | 3.3.8
|
pysqlite | 2.3.2
|
Genshi | 0.5.1
|
Agilo | 0.7.3.3-r1417-20090313
|
jQuery: | 1.2.6
|
Python Traceback
Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/web/main.py", line 435, in _dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/web/main.py", line 205, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/ticket/web_ui.py", line 182, in process_request return self._process_ticket_request(req) File "/usr/lib/python2.4/site-packages/agilo-0.7.3.3_r1417_20090313-py2.4.egg/agilo/ticket/web_ui.py", line 202, in _process_ticket_request template, data, content_type = super(AgiloTicketModule, self)._process_ticket_request(req) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/ticket/web_ui.py", line 508, in _process_ticket_request self._do_save(req, ticket, action) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/ticket/web_ui.py", line 1014, in _do_save cnum=internal_cnum): File "/usr/lib/python2.4/site-packages/agilo-0.7.3.3_r1417_20090313-py2.4.egg/agilo/ticket/model.py", line 645, in save_changes res = super(AgiloTicket, self).save_changes(author, comment, when, db, cnum) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/ticket/model.py", line 273, in save_changes (self[name], self.id)) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/db/sqlite_backend.py", line 58, in execute args or []) File "/usr/lib/python2.4/site-packages/Trac-0.11.4-py2.4.egg/trac/db/sqlite_backend.py", line 50, in _rollback_on_error return function(self, *args, **kwargs) OperationalError: no such column: remaining_time
Attachments (0)
Note:
See TracTickets
for help on using tickets.
PluginIssue (AgiloForScrum), please report it to the plugin maintainer.