"<Lost+Found>"

[M H]

After a sync, I noticed the creation of a top level task group called
<Lost+Found>. There's no mention of it in the manual. I suspect that
there was a conflict where both my Android or iPad and PC edited the
file. Is this how MLO handles conflicts? Or is this something else?

[M H]

I was guessing it worked like this.  I quite like this system.  Builds confidence that even if the sync doesn't know what to do, that I won't loose the info.  I'm impressed.

[M H]

Okay, now I'm nervous.

I did a sync today and had two <Lost+Found> branches show up. It
seems one was a re-creation of a PC delete I had made and another held
an item that I'm presuming the sync had trouble with on my Android.
The real scary part was, that my android had an item in the <Lost
+Found> branch that wouldn't show up on my PC, no matter how many
times I sync'ed. I sync'ed one and then the other, back and forth
three times and the PC wouldn't get the one item from the Android. If
I added a child item into the <Lost+Found>, that item would sync. In
fact that <Lost+Found> branch, a top level branch, wouldn't have its
position in the list sync'ed until I added a child item under it.

So, it seems that what ever problem arises seems to be left on a
single device and doesn't propagate. This is very troublesome to me.
If I push sync, I'm trusting that once the cloud service has a copy of
my sync'ed data, any device I then sync, will have an EXACT copy of
that data. If the sync logic allows problematic items to exist on a
single device, then I have to add checking every device for aberrant
data as part of my work flow... which is exactly what syncing is
supposed to prevent!

Is this a bug or something that I'm not understanding?

[m...@grantsmiths.org]

When a task is in L&F I think my job is to fix it ASAP and then sync. Part
of fixing it is getting it out of L&F, because nothing really *belongs*
there. It sounds to me as though you are building a branch of stuff that
makes its permanent home in L&F - that sounds wrong to me. Try moving the
tasks to where they belong and see if sync doesn't start working right.

This is just my feeling, I have no inside knowledge of how L&F was designed.
But if there's something wrong with a task on the phone and you instantiate
that error on Windows through sync, you are creating a "propagated error".
Propagated errors involve many more variables than simple errors, and are
generally way more difficult to reproduce, diagnose, and repair. By not
syncing your tasks that are still in L&F I would say MLO is doing a good job
of protecting against error propagation.

--
You received this message because you are subscribed to the Google Groups
"MyLifeOrganized" group.
To post to this group, send email to mylifeo...@googlegroups.com.
To unsubscribe from this group, send email to
mylifeorganiz...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mylifeorganized?hl=en.

[M H]

Creating items under <Lost+Found> was only done to test the syncing.
No, I don't hold any information there. I'm trying to get rid of
these folders by cleaning up the items.

On the Android, syncing doesn't create an error report or error
message. It just creates an item in the <Lost+Found> folder. When I
sync, I presume a full parallel has been created. The beauty, to my
mind, of the <Lost+Found> branch is that it is a safe place where
items are dumped that the sync has issues with. Once an item is place
in that group of items, it CAN be sync'ed. I have no plans to sync my
phone and then check the <Lost&Found>, sync my PC and then check its
<Lost+Found>, etc. One PC, two Androids and an iPad. Syncing becomes
a Herculean task.

I think I understand your concept of the propogated error, the catch
is, that by creating a new item in <Lost+Found>, a new item is created
and it turns into a simple error. The original item is left alone,
the new item is created. Both can be sync'ed. The user then fixed
the issue on one instance and both items are then 'caught up'. I
don't know why this would be not the model.

I'm waiting for the day when a true autosync exists. If all these
devices have active WIFI, by morning, they should all be the same.

[m...@grantsmiths.org]

Hi, M.H.
I think that one of the things you are saying is that there should be some
sort of error report detailing situations encountered on the Android side of
the sync, what action was taken, and perhaps what the user should do next.
If so, I enthusiastically agree with you.
-Dwight