On Mon, 12 Feb 2007, Andre Mueninghoff wrote:
That much I can confirm already from my side from my testing this past weekend, if I selected no to the timezone prompt (because sync encountered an event with the timezone set) then the adhoc index error would not appear. Thanks much your explanation of the possible cause. I had been wondering if there was some relationship to when I clicked yes on the timezone prompt. I will experiment a bit further, but my recollection is that when I was multi-tasking during the sync and clicked yes well after the sync completed had completed then the error did not occur.
Hi André,The floatingEvents collection check() failure was indeed a merge bug with handling datetime/time values whose only change is to a timezone of same offset such as Floating to Pacific when Pacific is the default timezone. In that case python lies and return True for newValue == oldValue and that caused the merging code to skip the change.
It's fixed in rev 13142. Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
