[Chandler-dev] Sorted subindex...not sorted properly - Rebuilding
index...installed on value...
Andi Vajda
vajda at osafoundation.org
Mon Feb 12 14:06:05 PST 2007
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..
More information about the chandler-dev
mailing list