Debugging branch access problems requires running custom scripts against live data

[Jonathan Lange]

I just helped benji debug a problem where a user could not read a private branch, even though he rightfully expected to be able to.

As part of the process, we needed to figure out whether *Launchpad* thought he could access the branch, and through what mechanisms. Is he a member of the owning team? Is he subscribed to the branch? etc.

To make this happen, I wrote a custom script (attached) that gathered this data and printed it out. It had to be run by a LOSA on production, which is far from ideal.

I guess ideally this information would be available as a web page to some tier of Launchpad's tech support (probably admins).

[Robert Collins (lifeless)]

We don't use medium according to our triage guidelines. Bumping to high, because operational efficiency matters™.

[Jonathan Lange (jml)]

On Wed, Jan 26, 2011 at 12:44 AM, Robert Collins
<email address hidden> wrote:
> We don't use medium according to our triage guidelines. Bumping to high,
> because operational efficiency matters™.

And I was using the triage guidelines too!

Guess I'm going to have to edit them to make it more readable.

jml

[Robert Collins (lifeless)]

So doing this is basically add an admin only form or api taking (branch, userid) and print the thing jml did.

[Robert Collins (lifeless)]

Marking low now; we haven't had that particular confusion since, I think.