approving merge proposal by email can hit db permission error

Bug #562048 reported by Michael Hudson-Doyle
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Tim Penhey

Bug Description

As seen in https://lp-oops.canonical.com/oops.py/?oopsid=1564CEMAIL22, the 'processmail' user needs select on the codeimport table.

This isn't biting us all the time because of the order in which things that grant you launchpad.Edit on the merge proposal are checked: it's the third line out of this condition that hits the problem:

        return (user.inTeam(self.obj.registrant) or
                user.inTeam(self.obj.source_branch.owner) or
                check_permission('launchpad.Edit', self.obj.target_branch) or
                user.inTeam(self.obj.target_branch.reviewer))

Related branches

Tim Penhey (thumper)
Changed in launchpad-code:
status: Triaged → In Progress
assignee: nobody → Tim Penhey (thumper)
milestone: none → 10.04
Revision history for this message
John A Meinel (jameinel) wrote :

What is this going to take to get fixed? My standard review model is to review via email, and when one of these email bounces, it doesn't even post the comment on the review. So I have to go track down what email I was reviewing (since the URL isn't included in the failure message), and then track down my original submission, and copy and paste it into the review dialog. (And then click 2-3 more times to get all the review statuses updated.)

It gets in my way about 1-2 times per day, and basically makes it so that reviewing is basically the last thing I want to be doing...

Revision history for this message
Aaron Bentley (abentley) wrote :

John, it has been fixed, but the fix cannot be deployed to edge. It must wait for our next full release. That will be on Tuesday.

Revision history for this message
Tim Penhey (thumper) wrote : Re: [Bug 562048] Re: approving merge proposal by email can hit db permission error

On Sat, 01 May 2010 06:29:55 you wrote:
> What is this going to take to get fixed? My standard review model is to
> review via email, and when one of these email bounces, it doesn't even
> post the comment on the review. So I have to go track down what email I
> was reviewing (since the URL isn't included in the failure message), and
> then track down my original submission, and copy and paste it into the
> review dialog. (And then click 2-3 more times to get all the review
> statuses updated.)
>
> It gets in my way about 1-2 times per day, and basically makes it so
> that reviewing is basically the last thing I want to be doing...

The fix has been landed, and will be rolled out on Tuesday.

Tim

Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
Changed in launchpad-code:
status: In Progress → Fix Committed
tags: added: qa-needstesting
Tim Penhey (thumper)
tags: added: qa-ok
removed: qa-needstesting
Tim Penhey (thumper)
Changed in launchpad-code:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.