We should raise a TimeoutError before sending the results back if the hard timeout is expired
Bug #228331 reported by
Francis J. Lacoste
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It happens that a request can complete in a time higher than our hard timeout limit. That's because hard timeout are only enforced when issueing query to the database. These pages will log a soft timeout.
We rather should abort those request with a hard timeout, since these will be flagged differently in our QA process.
| Changed in launchpad: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| importance: | High → Low |
To post a comment you must log in.
