Re: Full sync after update to Horde_ActiveSync 2.9.0

Michael J Rubinsky <[email protected]>
Newsgroups gmane.comp.horde.sync
Message-ID <20131119103740.Horde.e6trmzEbbFPXy3bYttGo8A1@h4.theupstairsroom.com>
Quoting [email protected]:

> Zitat von Michael J Rubinsky <[email protected]>:
>
>> Zitat von [email protected]:
>>>
>>> on the testserver we have done the update to ActiveSync 2.9.0 with  
>>> stopping Apache do the pear upgrade, do horde-clear-cache and  
>>> horde-db-migrate. After this the iPhone 4S connected with  
>>> ActiveSync does a full resync for the mailbox. Is this expected  
>>> behaviour or can this be prevented somehow?
>>
>> This is due to a change in the format of some of the cached data  
>> that is saved for each collection. I've added code to attempt to  
>> load the previous format before throwing the error to save the  
>> repairing. This *should* prevent the resync.
>
> At least for the iPhone it looks like it does not work reliable, so  
> one have to be aware that the devices will re-download the whole  
> mailbox after update...

So, you tested it with the fix I just added already? The code to try  
the older format was just committed:
https://github.com/horde/horde/commit/d9ef7956f009fe0558f9bff8d3bdb36c522420a9


>>> Another oddity is the following in the sync log
>>>
>>> "ERR: Cache version change"
>>>
>>> Not sure what is...
>>
>> This is an expected message when the cached data format changes.
>
> Ok, so why the data *format* of the cache changes? This is not about  
> *content* of the cache, no? It scares me because it is listed as  
> "ERR" (error).

Yes, it really shouldn't be an ERR I'll change it to NOTICE.


-- 
mike

The Horde Project (www.horde.org)
[email protected]

-- 
sync mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
smime.p7s (application/pkcs7-signature, 5.7 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.