[Tickets #9766] Re: JS error during mailbox loading

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9766
------------------------------------------------------------------------------
  Ticket             | 9766
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | JS error during mailbox loading
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-20 05:21) wrote:

> I still see this. Can you give me a quick overview of what's in the  
> viewPort response. IIUC the message count in there is wrong? Where  
> is it?

Here's what you need to do:

1. Isolate the first load request for the mailbox where you encounter  
the error.  This provides the initial state of the browser mailbox DB.
2. Find the delete Messages request that causes the error.
3. From these 2 you can figure out the index that originally existed,  
but no longer exists, that is causing the error.
4. Given this sequence number/UID (also the cacheID values of the  
mailboxes), you should take a look at the IMAP logs of the delete  
request to see if anything looks strange.  Also, pay attention to  
reported number of messages in the mailbox - as I previously  
mentioned, in all the cases I've seen that you have posted, it looks  
like there is an off-by-one error somewhere in this message count.

The goal is to determine why the browser is dropping the DB record of  
a message/UID that 1) still exists (according to IMAP and IMP server)  
and 2) the browser previously reported to IMP server that it had  
cached (the cache variable sent back in viewport requests).