Issuing the 'affects' command before a 'bug' command while editing multiple bugs using the email interface shouldn't crash.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
j.c.sackett | ||
Bug Description
As seen in the following traceback, the email handler crashed because the affects command was specified before the bug command.
This should just work.
> To: <email address hidden>
> Subject: Cron <launchpad@
> |_/srv/
> Date: Wed, 31 Jan 2007 13:15:13 +0000 (GMT)
> Reply-To: <email address hidden>
> X-Spambayes-
>.
> 13:15:11 ERROR An exception was raised inside the handler:
> http://
> -> http://
OOPS-780S232
Exception type AttributeError
Exception value 'NoneType' object has no attribute 'getBugTask'
Related branches
- Benji York (community): Approve (code)
-
Diff: 115 lines (+64/-11)3 files modifiedlib/canonical/launchpad/mail/commands.py (+10/-0)
lib/canonical/launchpad/mail/errortemplates/command-with-no-bug.txt (+8/-0)
lib/lp/bugs/tests/bugs-emailinterface.txt (+46/-11)
| Changed in malone: | |
| status: | Unconfirmed → Confirmed |
| description: | updated |
| Changed in malone: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
| importance: | Low → High |
| tags: | removed: fix-it-friday |
| Robert Collins (lifeless) wrote | #1 |
| Martin Pool (mbp) wrote Re: [Bug 83426] Re: Issuing the 'affects' command before a 'bug' command while editing multiple bugs using the email interface shouldn't crash. | #2 |
| Robert Collins (lifeless) wrote | #3 |
| Changed in launchpad: | |
| importance: | High → Critical |
| Changed in launchpad: | |
| assignee: | nobody → j.c.sackett (jcsackett) |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| Launchpad QA Bot (lpqabot) wrote | #4 |
| Changed in launchpad: | |
| milestone: | none → 11.04 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
Because we support
bug foo
affects bar
bug quux
affects zany
we probably want to report an error to the user, like we do on other un-executable mails. Not OOPS matters too of course ;)