6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
8/11/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#2973] Cache either expired prematurely or not rebuilt
*
Your Email Address
*
Spam protection
Enter the letters below:
. ..__.. ,.__.. . \ /| | \./ | || | \/ |__| | |__\|/\|
Comment
> 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. > >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers