| 2006-02-15 10:58:08 |
Dafydd Harries |
bug |
|
|
added bug |
| 2006-02-15 10:58:33 |
Dafydd Harries |
launchpad: status |
Unconfirmed |
Confirmed |
|
| 2006-02-15 10:58:33 |
Dafydd Harries |
launchpad: assignee |
|
stub |
|
| 2006-02-15 10:58:33 |
Dafydd Harries |
launchpad: statusexplanation |
|
|
|
| 2006-03-10 18:08:41 |
Diogo Matsubara |
bug |
|
|
added subscriber Launchpad Infrastructure |
| 2006-05-04 12:22:22 |
Andrew Bennetts |
launchpad: assignee |
stub |
spiv |
|
| 2006-05-04 12:22:22 |
Andrew Bennetts |
launchpad: statusexplanation |
|
Steve's asked me to work on this. |
|
| 2006-05-05 20:40:50 |
Diogo Matsubara |
description |
When an OOPS occurs because of a psycopgda Retry exception (e.g. OOPS-45A331), the traceback doesn't include any information about what the query that failed was. |
When an OOPS occurs because of a psycopgda Retry exception (e.g. OOPS-45A331), the traceback doesn't include any information about what the query that failed was.
Jamesh suggested in bug 39441:
"To help debug these problems, it would be useful to see the details of the wrapped exception/traceback, and include them in the OOPS report.
This could either be done specific to Retry exceptions, or we could try and detect wrapped exceptions with something like:
if len(value.args) == 3 and issubclass(value.args[0], Exception) and isinstance(value.args[2], traceback):
...
The additional traceback could just be appended after the first traceback in the OOPS report." |
|
| 2006-05-23 12:50:12 |
Diogo Matsubara |
launchpad: severity |
Normal |
Critical |
|
| 2006-05-23 12:50:12 |
Diogo Matsubara |
launchpad: statusexplanation |
Steve's asked me to work on this. |
|
|
| 2006-05-30 15:39:25 |
Diogo Matsubara |
launchpad: severity |
Critical |
Major |
|
| 2006-12-17 16:28:24 |
Christian Reis |
launchpad: importance |
High |
Medium |
|
| 2007-09-27 18:25:07 |
Francis J. Lacoste |
launchpad: assignee |
spiv |
|
|
| 2009-03-20 13:37:32 |
Diogo Matsubara |
description |
When an OOPS occurs because of a psycopgda Retry exception (e.g. OOPS-45A331), the traceback doesn't include any information about what the query that failed was.
Jamesh suggested in bug 39441:
"To help debug these problems, it would be useful to see the details of the wrapped exception/traceback, and include them in the OOPS report.
This could either be done specific to Retry exceptions, or we could try and detect wrapped exceptions with something like:
if len(value.args) == 3 and issubclass(value.args[0], Exception) and isinstance(value.args[2], traceback):
...
The additional traceback could just be appended after the first traceback in the OOPS report." |
When an OOPS occurs because of a psycopgda Retry exception (e.g. OOPS-45A331), the traceback doesn't include any information about what the query that failed was.
Jamesh suggested in bug 39441:
"To help debug these problems, it would be useful to see the details of the wrapped exception/traceback, and include them in the OOPS report.
This could either be done specific to Retry exceptions, or we could try and detect wrapped exceptions with something like:
if len(value.args) == 3 and issubclass(value.args[0], Exception) and isinstance(value.args[2], traceback):
...
The additional traceback could just be appended after the first traceback in the OOPS report."
SteveA suggested in bug 92185 more information that we should capture in cases like this:
"OOPS reports should take into account whether the request has been retried by showing how many retries occurred, and preferably showing independently the SQL and non-SQL time for each retry. This will allow us to see whether retried requests are using a lot of database resources, particularly with transactions involving writes to the database, it will help us debug cases where state that should be reset on a Retry is not reset, and will give us insight into whether some OOPS reports that have a lot of non-sql time are requests that were retried. That is, if we're resetting the SQL statement log on a Retry, but not resetting the non-sql-time counter." |
|
| 2011-05-30 08:12:13 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
| 2011-09-20 21:01:56 |
Robert Collins |
launchpad: importance |
Medium |
High |
|
| 2011-10-22 14:02:55 |
Curtis Hovey |
tags |
infrastructure lp-foundations |
infrastructure lp-foundations oops-infrastructure |
|
| 2011-12-12 22:55:25 |
Robert Collins |
summary |
Retry exceptions should include information about the original query |
OOPS reports on retried exceptions should include information about the original query |
|
