VM

Subject threading bug - 'missing

Bug #851978 reported by Uday Reddy
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
Medium
Uday Reddy

Bug Description

When there is a tree of messages as follows:

  917+2
     918
     919

and 917 is expunged, then 918 becomes the subject root of the remainder of the thread. However, its subtree doesn't contain 919. It seems that it hasn't been recognized that 918 has become a subject root, and all its data updated accordingly.

Tags: 8.2 threads

Related branches

Revision history for this message
Uday Reddy (reddyuday) wrote :

Another potential problem seems to be this. Given a subject thread like

    917+2 Subject
       918 Subject
       919 Re: Subject

where 919's reference parent is 917, expunging 917 causes it to be removed from the subject thread. This makes 919 dangling. Even though 919 records 918 as its root, 918 doesn't record 919 as a descendant.

Revision history for this message
Uday Reddy (reddyuday) wrote :

These problems are fixed in revision 894 of the 8.2.x branch.

However, there are still other errors giving 'spurious messages in integrity check.

Subject threading is more complicated than it first appeared. It seems better to use the Jamie Zawinski idea of ghost messages as the roots of reference threads.

Revision history for this message
Uday Reddy (reddyuday) wrote :

Ghost roots are now implemented in revision 1239 of the trunk.

Changed in vm:
status: Triaged → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
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.