lp:~divmod-dev/divmod.org/dangling-1091

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1635. By glyph on 2006-06-06

a fix which fixes the test, but doesn't clean up databases comprehensively

1634. By glyph on 2006-06-06

remove spurious assert, add comments, fix whitespace

1633. By glyph on 2006-06-06

tests which fails (unfortunately due to spurious assert)

1632. By glyph on 2006-06-06

Branching to 'dangling-1091'

1631. By glyph on 2006-06-06

Fix cross-store transactions, and substore attachment.

Previously generated SQL was cached on item classes, which was incorrect
because different databases could potentially be attached to their parents,
changing the SQL that was generated. Now the SQL is properly cached per-store.

That change will also be useful to anyone wanting to implement distinct
backends for different Store objects.

Also, cross-store transactions were previously broken because items on attached
substores are not checkpointed.

Together, this change should make transactions between and across substores
work properly in the case of both success and failure.

Author: soyt

Reviewer: glyph

Fixes #1092

Fixes #1087

1630. By exarkun on 2006-06-06

Merge insecure-pop3-981

Author: exarkun
Reviewer: washort
Fixes #981

This adds handling for POP3Client's InsecureAuthenticationDisallowed
exception and sets status appropriately when it is raised.

1629. By washort on 2006-06-05

Make benchmark actually work again. Closes #1104.

1628. By washort on 2006-06-05

Don't run spamfilter tests if DSPAM is not installed. Closes #1103.

1627. By moe on 2006-06-05

apply fix for #1099. author: moe, reviewer: glyph. prevents alert() if the search box is present. closes #1099

1626. By glyph on 2006-06-05

Merge prints-and-logs-1097.

Author: exarkun (unwilling)

Reviewer: glyph

Fixes #1097

This merges in some useful messages about grabber invocation and SQLite timings
from the QA working copy.

If your SQL is taking a really long time, or a particular grabber is hosing
your Quotient instance (hey, you'd *better* not actually be running a Quotient
instance yet) this will help you find out.