[Tickets #13825] Re: Remi PHP update to 5.5.21-1 results in constant resyncing

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13825
------------------------------------------------------------------------------
  Ticket             | 13825
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Remi PHP update to 5.5.21-1 results in constant
                     | resyncing
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2015-02-04 22:21) wrote:

>>> C: 31 UID SEARCH RETURN (ALL COUNT) HEADER MESSAGE-ID
>>> <00d701d01f08$6f76a3f0$4e63ebd0$@amusing.de> UID 0:215
>>> S: 31 BAD Error in IMAP command UID SEARCH: Invalid UID messageset
>>
>> Obviously, 0 is not allowed.  Imap code doesn't do assert checking
>> for this situation (it probably should).  But that 0 has to come from
>> the calling code.
>
> I can't reproduce this. The ids provided to the method that calls  
> this search routine come from the list of uids provided from the  
> IMAP server. There is an array_diff that removes uids that we know  
> have since vanished.

Any chance that maybe the array_diff, or something after it, is a  
doing a re-indexing of the ids list (not looking at code, so this is  
just spitballing).  Trying to think of logical ways an array can end  
up having a zero value.