In Zopeless, mails should be sent only when the transaction is committed

Bug #29744 reported by Björn Tillenius
2
Affects Status Importance Assigned to Milestone
Launchpad itself
In Progress
Low
Colin Watson

Bug Description

When sending mail in normal Zope mode, as well as in tests, which test the sending of mail, the mail is sent only if the transaction is commited. This is good.

However, when you are in an Zopeless environment, mail is sent immediately. This causes problems with the email interface, since bug notifications get sent out even though the transaction is later aborted. It would be possible to work around this, but it's quite troublesome, and it seems better to fix the real problem, make sending mail in a Zopeless environment have same semantics as in a Zope environment.

Related branches

Changed in launchpad:
assignee: nobody → stub
Dafydd Harries (daf)
Changed in launchpad:
status: Unconfirmed → Confirmed
Stuart Bishop (stub)
Changed in launchpad:
assignee: stub → nobody
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Please note that there is code depending on this behaviour in archiveuploader/uploadprocessor.py. When this bug is fixed, that code will also need to be addressed. Search for "29744" in the file to see the comment in there.

Curtis Hovey (sinzui)
tags: added: tech-debt
Revision history for this message
Julian Edwards (julian-edwards) wrote :

It's probably best if we make is so there's a choice of send the email now, or send when the transaction is committed so that the code in uploadprocessor (and soon to be also in packagecopyjob.py) still works after a txn is rejected.

Changed in launchpad:
importance: Medium → Low
Colin Watson (cjwatson)
Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
status: Triaged → In Progress
Colin Watson (cjwatson)
summary: - In Zopeless, mails should be sent only when the transaction is commited
+ In Zopeless, mails should be sent only when the transaction is committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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