530141 - PendingCommitTracker does not get deletion notified, blind move may be wrong

Status: NEW

(MailNews Core :: Database, defect)

Description

[Andrew Sutherland [:asuth] (he/him)]

While writing another unit test today I noticed that PendingCommitTracker failed to update some headers (and therefore failed the test) if I added a test at the end of base_index_messages that forced a commit.

Preliminary investigation suggests that explicit deletion cases are insufficient and that noteBlindMove may have gotten side-swiped by a change in the method it was reusing.  I also need to audit whether implied deletion by a move to another folder is doing the right thing.

The good news is that PendingCommitTracker will not permanently break for any of this stuff.  It will, however, output things to the error console, which may concern users.  Implied deletion due to a move may currently result in us writing gloda-id/gloda-dirty properties on headers that don't need to be written but are harmless.

This would be an appropriate fix for 3.0.x but is not a 3.0 blocker.