Opened 9 years ago
Closed 7 years ago
#12311 closed defect (fixed)
Change milestone name gives an internal server error
Reported by: | Owned by: | Russ Tyndall | |
---|---|---|---|
Priority: | normal | Component: | TimingAndEstimationPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 1.0 |
Description
Getting internal server error when changing milestone name.
To get this error, on the admin panel I change the milestone name, and then I have the following error:
Python Traceback Most recent call last: File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/web/main.py", line 513, in _dispatch_request dispatcher.dispatch(req) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/web/main.py", line 222, in dispatch resp = chosen_handler.process_request(req) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/admin/web_ui.py", line 120, in process_request path_info) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/ticket/admin.py", line 55, in render_admin_panel return self._render_admin_panel(req, cat, page, version) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/ticket/admin.py", line 261, in _render_admin_panel mil.update(author=req.authname) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/ticket/model.py", line 1088, in update self.move_tickets(self.name, author, "Milestone renamed") File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/ticket/model.py", line 1143, in move_tickets ticket.save_changes(author, comment, now) File "c:/users/ammall~1/appdata/local/temp/easy_install-4unthi/Trac-1.0.5-py2.7-win32.egg.tmp/trac/ticket/model.py", line 369, in save_changes listener.ticket_changed(self, comment, author, old_values) File "build/bdist.win32/egg/timingandestimationplugin/ticket_daemon.py", line 153, in ticket_changed self.watch_hours(ticket, author) File "build/bdist.win32/egg/timingandestimationplugin/ticket_daemon.py", line 107, in watch_hours hours = convertfloat(ticket['hours']) File "build/bdist.win32/egg/timingandestimationplugin/ticket_daemon.py", line 14, in convertfloat return float(x.replace(',','.')) System Information: User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Trac 1.0.5 Docutils 0.9.1 Genshi 0.7 (without speedups) mod_wsgi 3.3 (WSGIProcessGroup WSGIApplicationGroup %{GLOBAL}) Pygments 1.5 pysqlite 2.6.0 Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] pytz 2011c setuptools 1.1.6 SQLite 3.8.9 Subversion 1.7.3 (r1242825) jQuery 1.7.2 jQuery UI 1.8.21 jQuery Timepicker 1.0.1 Enabled Plugins: timingandestimationplugin 1.4.7b c:\python27\lib\site-packages\timingandestimationplugin-1.4.7b-py2.7.egg trac-jsgantt 0.11 c:\python27\lib\site-packages\trac_jsgantt-0.11-py2.7.egg tracmastertickets 3.0.4 c:\python27\lib\site-packages\tracmastertickets-3.0.4-py2.7.egg tracsubticketsplugin 0.2.0.dev-20150225 c:\work\trac\projects\sweng\plugins\tracsubticketsplugin-0.2.0.dev_20150225-py2.7.egg
Another weird thing is that after the error, part of the tickets have its milestone changed to the new milestone name, which is not visible on the Manage Milestones administration screen, that is, it looks like the milestone is not created, and the other part continues with the previous milestone name. This last milestone continue existing on Manage Milestones administration screen.
Attachments (0)
Change History (4)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
Sorry, I guess I never saw this. I can see where there might be a null error there. I can probably be defensive and resolve the error without having to actually recreate it.
comment:3 Changed 7 years ago by
I think I found and fixed this error in another ticket #13219 Try version 1.5.0(b)
Thanks for the bug report and cheers, Russ Tyndall
comment:4 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Another hint for this issue. I did a batch update, setting "add hours to ticket" to all tickets on my db and this error stopped appearing. I wonder if it was my fault during configuration. Doing something likean upgrade or so.