Opened 16 years ago
Last modified 3 years ago
#7354 closed defect
Unable to Edit or Delete an invalid tickets report — at Version 3
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11.1 |
Component: | report system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Ryan J Ollos | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
While editing the SQL (which I don't really know much about at all) for a new report that I was trying to create, I managed to create an error that I cannot seem to get out of:
After editing the report's SQL, I clicked on "SAVE REPORT".
I imediately got "Oops… Trac detected an internal error:".
I then tried going back into "View Tickets" with the intention of undoing my mistake, but now I am unable to get into the edit view for that ticket.
The View Tickets list does not seem to have a way for me to go directly to edit. So I have to select the report, which immediately fails again.
The Python Traceback follows:
Traceback (most recent call last): File "C:\programs\python2.4\lib\site-packages\trac\web\main.py", line 406, in dispatch_request dispatcher.dispatch(req) File "C:\programs\python2.4\lib\site-packages\trac\web\main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "C:\programs\python2.4\lib\site-packages\trac\ticket\report.py", line 88, in process_request resp = self._render_view(req, db, id) File "C:\programs\python2.4\lib\site-packages\trac\ticket\report.py", line 346, in _render_view value['date'] = format_date(cell) File "C:\programs\python2.4\lib\site-packages\trac\util\datefmt.py", line 68, in format_date return format_datetime(t, format, gmt) File "C:\programs\python2.4\lib\site-packages\trac\util\datefmt.py", line 58, in format_datetime t = time.localtime(float(t)) ValueError: invalid literal for float(): dbcole
Change History (3)
comment:1 by , 16 years ago
Component: | general → report system |
---|---|
Keywords: | needinfo added |
comment:2 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:3 by , 16 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 0.11.2 |
Resolution: | worksforme |
Status: | closed → reopened |
It happens at least here on t.e.o:
Traceback (most recent call last): File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/api.py", line 339, in send_error 'text/html') File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/chrome.py", line 708, in render_template if not req.session or not int(req.session.get('accesskeys', 0)): File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/api.py", line 168, in __getattr__ value = self.callbacks[name](self) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/main.py", line 257, in _get_session return Session(self.env, req) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/session.py", line 142, in __init__ self.get_session(req.authname, authenticated=True) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/session.py", line 156, in get_session super(Session, self).get_session(sid, authenticated) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/web/session.py", line 56, in get_session (sid, int(authenticated))) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/local/virtualenv/lib/python2.4/site-packages/Trac-0.11dev_r7225-py2.4.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) ProgrammingError: current transaction is aborted, commands ignored until end of transaction block
Try editing any of the reports, insert an error and save it. You'll get the above "raw" backtrace (i.e. as text). It must somehow be PostgreSQL specific, maybe the connection is not properly reset after the initial error and all subsequent use will fail (here while retrieving session info during rendering of the error page).
Testing on 0.11, but I can't recreate your problem. For all errors I provoke, it provides an error message instead of a report table, but the 'Edit' button is always available.
I'm closing as 'worksforme' as without further information it does not look like an current issue:
?action=edit
on the url, and provide the SQL you tried to run.Reopen ticket if you have new information.