History and Layout snapshots should sync to the cloud periodically

It appears that History and Layout snapshots are only uploaded to the cloud when Logos shuts down normally. If Logos crashes, you lose all the History and Layout changes, though everything else you've done in the session did get synced.

Please rectify this. I'd almost call it a bug, but I'm sure you don't see it that way.

Find more posts tagged with

Comments

Milford Charles Murray

It appears that History and Layout snapshots are only uploaded to the cloud when Logos shuts down normally. If Logos crashes, you lose all the History and Layout changes, though everything else you've done in the session did get synced.

Peace, Rosie! *smile*

Happiness and Blessings to you for 2013! I'm giving 2013 a Name: Emmanuel! Because He is truly with us!

Rosie, what is the source of information that you are working with??? I've never heard before that we would (could!?) lose History and Layout charges in such a way. It seems to me this should be part of the regular syncing .........

NB.Mick

https://community.logos.com/discussion/comment/449144#Comment_449144

Rosie, what is the source of information that you are working with??? I've never heard before that we would (could!?) lose History and Layout charges in such a way. It seems to me this should be part of the regular syncing .........

Milford,

just to come in from the sideline: while I can't comment on history (I simply didn't bother to check after restarting, but from the quick look onto it, losses seem probable), I experienced layout change losses a lot in the current beta. It seems, my Logos closes more often due to 1887 error than to proper closing - which means, on restarting, it takes me back not to where I was, but to an old layout it saved days ago as "application closed". This annoyed me to the extend I saved the current state as a new named layout just to not be brought to this other view again.

Mick

Milford Charles Murray

https://community.logos.com/discussion/comment/449146#Comment_449146

Milford,

just to come in from the sideline: while I can't comment on history (I simply didn't bother to check after restarting, but from the quick look onto it, losses seem probable), I experienced layout change losses a lot in the current beta. It seems, my Logos closes more often due to 1887 error than to proper closing - which means, on restarting, it takes me back not to where I was, but to an old layout it saved days ago as "application closed". This annoyed me to the extend I saved the current state as a new named layout just to not be brought to this other view again.

Mick

Peace, Mick! That's absolutely "crystal-clear"! Thank you!

Quite a "scarey" scenario, actually" My Layouts are very important to me!

NetworkGeek

It appears that History and Layout snapshots are only uploaded to the cloud when Logos shuts down normally.

This is not true, there must be more to it than that. Maybe this is a beta issue, as I was testing on 5.0a SR-3 (5.0.1.0278) ?
I tried replicating this, and here is what I saw:

1. I brought up Logos, made sure no sync was needed (sync circle was gray)

2. I brought up a layout - it now needs to sync

3. I made a layout change, and updated it - still needs to sync

I brought up Windows Task Manager (Ctrl-Shift-Esc and quickly killed the Logos app, simulating a non-normal program closure. But that quick, it sync'd. I confirmed when I brought it back up, that the layout change was sync'd.

Could it be a beta issue? If a computer is a little slow sync doesn't get a chance to run with other stuff going on? Network issue prevents the sync?

Not denying that the update did not happen on Rosie's computer, but it's not as simple as layout syncs only happen during normal shutdown.

Graham Criddle

https://community.logos.com/discussion/comment/449181#Comment_449181

This sounds a little similar to what I reported at http://community.logos.com/forums/p/63761/447913.aspx (this was on 5.0b B1)

Could it be a beta issue?

The last I saw I don't think Rosie is running the beta.

Rosie Perera

https://community.logos.com/discussion/comment/449181#Comment_449181

It appears that History and Layout snapshots are only uploaded to the cloud when Logos shuts down normally.

This is not true, there must be more to it than that. Maybe this is a beta issue, as I was testing on 5.0a SR-3 (5.0.1.0278) ?

I tried replicating this, and here is what I saw:

1. I brought up Logos, made sure no sync was needed (sync circle was gray)

2. I brought up a layout - it now needs to sync

3. I made a layout change, and updated it - still needs to sync

I brought up Windows Task Manager (Ctrl-Shift-Esc and quickly killed the Logos app, simulating a non-normal program closure. But that quick, it sync'd. I confirmed when I brought it back up, that the layout change was sync'd.

Could it be a beta issue? If a computer is a little slow sync doesn't get a chance to run with other stuff going on? Network issue prevents the sync?

Not denying that the update did not happen on Rosie's computer, but it's not as simple as layout syncs only happen during normal shutdown.

Graham is right. I'm not using the beta.

Here's how to replicate the behavior I'm seeing:

Start Logos with an empty layout.

Open a random resource you haven't used in a long time, or have never opened (just to make sure it wouldn't have been in your recent History naturally anyway).

Open a couple of other random things (this isn't necessary, but the more changes you make to the layout the more there will be to demonstrate the problem).

Click to drop down the Layouts menu. Notice that the "Now" snapshot looks current.

Bring up Task Manager and force Logos process to terminate (simulating a crash).

Open Logos again.

Click to drop down the Layouts menu. The "Now" snapshot that was there before you forced the simulated crash is no longer anywhere. It should have gotten synced to the server so that you could recover your last layout before the crash.

And I was wrong about History not being synced. It looks like it is now. Press Ctrl+H and see that the last few things you opened before the "crash" are listed there. I'm surprised it is working, because the beta release notes for 5.0b Beta 1 include "Implemented sync for History panel." But I'm running 5.0a SR-3. So I don't know how I managed to have this feature working. Oh well, I won't complain. Still, I think the most recent Layout snapshots need to get synced.

NetworkGeek

https://community.logos.com/discussion/comment/449233#Comment_449233

Ah - that's different. "Now" is updated when you close. If you actually update a Layout, which is what you originally said, that gets sync'd right away, or as soon as it can get CPU cycles to do so.

Whether they would consider that a bug I am not sure - "Now" is like unsaved work in memory. It's like closing Notepad with text in it before you save - it's gone. Word sometimes recovers in-memory crashes, sometimes not. I thought you were saying layouts I save get lost, which is not true thankfully. They could certainly change that if they wanted to!

NB.Mick

https://community.logos.com/discussion/comment/449237#Comment_449237

Ah - that's different. "Now" is updated when you close. If you actually update a Layout, which is what you originally said, that gets sync'd right away, or as soon as it can get CPU cycles to do so.

Dominick,

I didn't read Rosie as to referring to saved "named layouts", especially since she used "snapshots" in the thread title. These are done by Logos at some intervals (maybe these were simply more often in the past than now) - reminds of the auto-save feature in text processors. And since you brought in the Word-comparison: the manageable suggestion for Logos developers (as they need more than "we want more stability, better performance and no lost work" to really act upon") I read from this thread would be:

Implement a system-wide setting "save layout snapshot every X minutes", x maybe counting in 10, 20, 30 steps (or 30, 60, 90... whatever makes sense) with 0 never. Thus users with a less than stable installation may set this at shorter intervals, users who don't care may opt for "never".

Mick

Rosie Perera

https://community.logos.com/discussion/comment/449336#Comment_449336

Ah - that's different. "Now" is updated when you close. If you actually update a Layout, which is what you originally said, that gets sync'd right away, or as soon as it can get CPU cycles to do so.

Dominick,

I didn't read Rosie as to referring to saved "named layouts", especially since she used "snapshots" in the thread title. These are done by Logos at some intervals (maybe these were simply more often in the past than now) - reminds of the auto-save feature in text processors.

Yup, you interpreted me correctly, Mick.

the manageable suggestion for Logos developers (as they need more than "we want more stability, better performance and no lost work" to really act upon") I read from this thread would be:

Implement a system-wide setting "save layout snapshot every X minutes", x maybe counting in 10, 20, 30 steps (or 30, 60, 90... whatever makes sense) with 0 never. Thus users with a less than stable installation may set this at shorter intervals, users who don't care may opt for "never".

Well put.