[Tickets #12589] Re: Kolab_Storage: Ensure status($folder) is not cached

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12589
------------------------------------------------------------------------------
  Ticket             | 12589
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab_Storage: Ensure status($folder) is not cached
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Jan Schneider
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-20 18:19) wrote:

> The correct way of fixing this (at least as of Horde_Imap_Client  
> 2.14.0) will be to add Horde_Imap_Client::STATUS_FORCE_REFRESH to  
> the mask passed in the $flags parameter to status().

thanks, that's exactly what I was looking for!
(I browsed the Imap_Client source for 30 minutes or so looking for a  
mechanism like this ;))

@mjr: I've only seen this problem with Kolab and only with non-mail  
data. Probably it was triggered because I was only syncing one  
collection and one folder at that time. Otherwise the imap connection  
gets re-used internally and issues SELECT on different folders.

I can look into the proper fix using the new flag probably at the end  
of September, may be earlier.
In fact I would assign the bug to myself but I didn't get my developer  
status back since horde transitioned to git (which was ages ago) ;)