[Tickets #2973] Cache either expired prematurely or not rebuilt

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2973
-----------------------------------------------------------------------
 Ticket             | 2973
 Updated By         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | Cache either expired prematurely or not rebuilt
 Queue              | IMP
 Version            | HEAD
-State              | Assigned
+State              | Feedback
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-11-14 21:46) wrote:

I used to get these errors myself . . . until I implemented some code a few
days ago.  This used to happen when a body structure was the first object
created for a UID (for example, a new message that comes in when you are in
the message screen will create the structure cache object only in
IMP_Contents).  then, when you would go back to the mailbox screen, the
overview object would not be cached so you would get all the undefined
errors.

However, I thought this commit fixed this:
http://lists.horde.org/archives/cvs/Week-of-Mon-20051107/050680.html
The logic is as follows - if no mailbox cache exists, $ret_load is false and
this information must be obtained from the IMAP server.  If $ret_load is
true, the mailbox cache exists and we loop through the message array.  Every
message index that does not contain a uid entry in the cache (the uid
variable only exists if overview info is stored in the cache) is flagged for
retrieval by the IMAP server.

Long story short, I experienced the same behavior in the same conditions as
you report (on a reproducible basis).  However, I have not seen this a
single time since I made the above mentioned change.  And i can't reproduce
it now.