Handle non-branch repositories better
Bug #512517 reported by
Aaron Bentley
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| loggerhead |
Triaged
|
Low
|
Unassigned | ||
| loggerhead-breezy |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
When Launchpad tries to show a branch with Loggerhead, but the location actually contains a shared repository with no branches, we see "Internal Server Error". This recently happened with http://
(Obviously, we can't display a branch, but we should give a clear error..)
| description: | updated |
Revision history for this message
| Matt Nordhoff (mnordhoff) wrote | #1 |
| Changed in loggerhead: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in loggerhead-breezy: | |
| status: | New → Incomplete |
To post a comment you must log in.
When using serve-branches, non-branch locations generate a directory listing, e.g.:
http://
Of course, for an empty shared repo, an empty directory listing isn't super-useful...
I'd be happy to take a patch that made serve-branches and start-loggerhead show a helpful message in this case. I probably wouldn't work on it, though... :P