- Previous by thread: Re: CLue to duplicate appts.
- Next by thread: RE: CLue to duplicate appts.
This is probably a bug. The trick with fixing these bugs is
to be able to reproduce them in a controlled environment so that
somebody can get enough debugging information to track down
what's going on.
In a nutshell, SyncCM sync works by converting both the Pilot
and Sun calendar records to a neutral format, then merging
them together and determining what's changed. SyncCM compares
appointments in the neutral format to try to establish a
mapping between the Pilot and CM appointments. What we might
be seeing here is that there is a slight discrepancy in the
code that does this correlation (or possibly in the code that
does the translation into the neutral fomat).
The trick here is to dump out the records for the offending
appointments and examine them closely. You can find a certain
amount of information in the SyncCM database, stored in your
~/.pilotmgr/SyncCM directory (hint, if you read it in and write
it back out again with Data::Dumper you can get it into a user-
readable format). But at some point, somebody's going to have
to go after this bug with debugging code and/or the debugger
and figure out where the translation broke down. Alas, I don't
have the cycles to do that anymore. I suspect that Alan is also
pretty damn busy these days.
Does anybody have the time and inclination to become a saviour
to the masses and investigate this?
-Bharat
> -----Original Message-----
> From: Robin Jeffries [mailto:Robin.Jeffries@xxxxxxxxxxx]
> Sent: Tuesday, June 22, 1999 12:57 PM
> To: pilotmgr@xxxxxxxxxxxxxxxxxxxx; Alan.Harder@xxxxxxxxxxxx
> Subject: Re: CLue to duplicate appts.
>
>
> OK, I'll admit that I also sync in multiple machines, but I
> definitely
> don't understand why it should lead to the problems I see. I have to
> sync with my PC, because its the only place that will backup
> everything on my pilot. I set the PC to "pilot overrides
> desktop", so
> all the dates should be the same, whatever they are. On the Solaris
> box I do a full merge.
>
> The explanation of the archive dates doesn't make sense to me. If
> this were the problem, then I should have it with all my
> appointments,
> not just with a random few. In particular, it shouldn't take
> the same
> 3 appointments (out of 997) and change their status on every sync.
> This has to be a bug, and I don't see how it can relate to the
> multiple syncs.
>
>
> Robin
>
> |From: Alan Harder <Alan.Harder@xxxxxxxxxxxx>
> |To: pilotmgr@xxxxxxxxxxxxxxxxxxxx, jloran@xxxxxxxxxxxxxxxx
> |Subject: Re: CLue to duplicate appts.
> |
> |> I've just assumed that it had to do with archive dates and such.
> When
> |> you sync on one machine, it must change an archive date on the
> |> appointments on the pilot, which no longer will match the date the
> other
> |> machine thinks the appointments were changed. So everything gets
> |> confused. Now I'm just guessing here. I have no familiarity with
> the
> |> code, so experts, please correct me or clarify.
> |
> |you are quite right.. if you sync to more than one machine you should
> |expect some unexpected behavior :)
> |
> | - Alan
> |---------------------------------------------------------------------
> ---
> |***********************************************************
> |* This is a public mailing list! *
> |* Please do not publish Sun proprietary information here! *
> |* - - - - - - - - - - - - - - *
> |* http://www.moshpit.org/pilotmgr *
> |***********************************************************
>
> --------------------------------------------------------------
> ----------
> ***********************************************************
> * This is a public mailing list! *
> * Please do not publish Sun proprietary information here! *
> * - - - - - - - - - - - - - - *
> * http://www.moshpit.org/pilotmgr *
> ***********************************************************
>
|
|