loggerhead does not handle incompatible repositories (CHKInventoryRepository)

I'm not sure this shouldn't throw an oops: it indicates that the user isn't able to get the data out of the branch, and this is something we could at least try to fix. (Either by cross-format stacking, or by upgrading the branches for them.)

On Tue, Jan 11, 2011 at 12:27 PM, Martin Pool <email address hidden> wrote:
> I'm not sure this shouldn't throw an oops: it indicates that the user
> isn't able to get the data out of the branch, and this is something we
> could at least try to fix.  (Either by cross-format stacking, or by
> upgrading the branches for them.)

We could record an oops, but I don't think we want to show the oops
screen to the user when (often) they can fix the situation themselves.
(Certainly for local installs of loggerhead the local user can fix it,
and when looking at ones own branch in launchpad).

Also OOPS are rather inefficient for generating a list of all branches
that need fixing : we can do that better with an analysis script for
the branch hosting area.

Okay, so it sounds like the best fix would be for launchpad to have an analysis script, instead of having a custom exception handler in loggerhead to deal with this specific situation. Loggerhead itself normally actually shows the user the error it received--it's only on Launchpad that it hides the error. So I think a launchpad-specific resolution would be more appropriate here, and this probably does not need any work on loggerhead.

I disagree. Even for standalone loggerhead installs we can do better than barfing.