Badge branches with import/mirror errors
Bug #79492 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Tim Penhey | ||
Bug Description
Branches can be in an error state because e.g. the import failed, or the mirroring failed, or some other states. It would be good to show a little /!\ icon next to them to show there's a problem.
Revision history for this message
| David Allouche (ddaa) wrote | #1 |
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in launchpad-bazaar: | |
| assignee: | nobody → thumper |
| status: | Confirmed → In Progress |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
| Changed in launchpad-bazaar: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-bazaar: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
To clarify: you suggest displaying this badge in branch listings, right?
Sounds like a good thing. But in some cases, the error is expected. For example the import is expected not to work (restricted svn, non-main CVS, etc.) or the mirroring is expected not to work (restricted access, bogus branch).
Expected failures occur when Launchpad is used as a simple registry.
Expected import failures can be marked by providing a UI to set importstatus to DONTSYNC (currently, I set this by poking directly into the DB).
Expected mirror failures are harder. If it is a mirror (non-upload, non-import) branch, for which no data was ever mirrored, it should be possible to set a simple "dont-mirror" flag. If some data was mirrored, it's not clear whats should be done. For upload and import branch, the dont-mirror flag does not make sense.
Regardless, we could display this badge on branches without blocking a way to indicate expected failures.