loggerhead times out annotating large single files (eg sql_parse.cc from mysql-server)
Bug #401412 reported by
Christian Hammers
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Unassigned | ||
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
| loggerhead |
Triaged
|
High
|
Unassigned | ||
| loggerhead-breezy |
Triaged
|
High
|
Unassigned | ||
Bug Description
Hello
http://
repeatedly gives a:
Please try again
Sorry, there was a problem connecting to the Launchpad server.
Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
Thanks for your patience.
I tried a few days and 5 minutes ago with the same error. Other files from the same directory work. Maybe this file is just
too big (230k) or has had too many changes so that some kind of PHP memory_limit or Timeout is hit. Please fix!
bye,
-christian-
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
| summary: |
- Internal Server Error when viewing annotated file + error annotating large file |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote Re: error annotating large file | #2 |
| Changed in launchpad-code: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in loggerhead: | |
| status: | New → Invalid |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #3 |
| Changed in launchpad-code: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Robert Collins (lifeless) wrote | #4 |
| Changed in loggerhead: | |
| status: | Invalid → Triaged |
| importance: | Undecided → High |
| Changed in launchpad: | |
| importance: | Medium → High |
| summary: |
- error annotating large file + timeout annotating sql_parse.cc from myself-server |
Revision history for this message
| Robert Collins (lifeless) wrote Re: timeout annotating sql_parse.cc from myself-server | #5 |
| Changed in launchpad: | |
| importance: | High → Medium |
| Changed in loggerhead: | |
| importance: | High → Critical |
| Changed in launchpad: | |
| importance: | Medium → Critical |
| summary: |
- timeout annotating sql_parse.cc from myself-server + loggerhead times out annotating large single files (eg sql_parse.cc from + mysql-server) |
| Changed in bzr: | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: timeout |
| tags: | added: codebrowse |
| tags: | added: check-for-breezy |
| Changed in loggerhead-breezy: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| information type: | Public → Private |
| information type: | Private → Public |
| Changed in bzr: | |
| status: | Confirmed → Fix Released |
| Changed in launchpad: | |
| importance: | Critical → High |
| Changed in loggerhead: | |
| importance: | Critical → High |
To post a comment you must log in.
Confirmed today, so not connected to any transient problems with the rewrite map.
Christian, I suspect this file does have too long or complex of a history to be annotated within the cap on request time. Obviously it would be good to: annotate it faster, perhaps give partial data rather than total failure, or at least give a more useful message.