Auto saves mess double saving panes and so restore is messed up?! about tmux-continuum

[bruno-]

Hey, thank you for reporting this issue.

Do you have the latest versions of both tmux-resurrect and tmux-continuum?

What is your status-interval option value $ tmux -g show status-interval?
I see you have set -g status-interval 5 in the tmux.conf, but that is commented out.

About "double" saving - that could happen if status-interval is low (5 seconds is low) and saving takes relatively long (5-10 seconds). Here's the possible scenario how that could happen:

• automatic saving starts and will take 10 seconds to complete
• in the meantime, another automatic save is started (because the first one is not done yet) and it duplicates entries in the last file

I think I addressed this possibility, but I will look into this again.
I will be pretty responsive over the weekend so your replies would be helpful @hoschi!

[bruno-]

Hi,
I've been investigating and trying to reproduce this issue.
I've set very aggressive auto-save settings:

• set -g status-interval 2 # tmux setting that influences how often last timestamp will be checked
• set -g @continuum-save-interval '1' # auto save happens every 60 seconds
• I also have a large number of panes and windows so save takes around 5-7 seconds

I couldn't notice anything unusual with the "continuum" last file. The content was all ok.

I've also inspected the code and after the first review I think we have mechanism in place that should prevent multiple saves happening at the same time..

So, can you please fetch latest tmux-continuum and tmux-resurrect versions and try this again? I'm curious about the results.

One other thing I noticed about your tmux.conf: set -g @tpm_plugins "... and run-shell ~/.tmux/plugins/tpm/tpm lines should be at the very bottom of tmux.conf.
It's possible set -g @continuum-restore 'on' line was not detected because of that.

[hoschi]

show -g status-interval gives me '2' for the value. Man pages states it is 15, so I configured that in my tmux.conf now. Also I moved the lines down as you said. I removed resurrect and continuum from ~/.tmux/plugins added and hit Ctrl-I to install it again.

But I got the same result as before when the first continuum auto save takes place :(
This line is actually fake (because of privacy):

pane    notes   1   :AA 0   :-  0   :/home/hoschi/Dropbox/notes 1   vim :vim /home/hoschi/foo.md

the dir name has a space in it. E.g. /home/hoschi/foo bar/foo.md which leads to a wrong restore. It restores vim /home/hoschi/foo instead of /home/hoschi/foo bar/foo.md. I know this is restore, not save ... but this is the only thing I saw as secondary problem.

I have no other idea what can break continuum auto save. I thought of strange session names or so, but then resurrect should also fail.

[yamsu]

Hi,

I also am experiencing the same problem. Every now and then I get triplicate entries the autosave file. This can be a real issue if this file is used by resurrect to recover a session. The worst case is when a vim session is recovered, the addition lines are send to vim and that can mess up a code file/document. in the I have made the following changes:

The end of my .tmux.conf:

set -g @resurrect-processes 'vifm ssh'
#set -g @resurrect-processes ':all:'
set -g @resurrect-strategy-vim 'session'
set -g @resurrect-save-bash-history 'on'
set -g @continuum-restore 'on'

Save every thirty minutes

set -g @continuum-save-interval '30'
set -g @tpm_plugins '
tmux-plugins/tpm
tmux-plugins/tmux-sensible
tmux-plugins/tmux-resurrect
tmux-plugins/tmux-continuum
tmux-plugins/tmux-open
'
run-shell '~/.tmux/plugins/tpm/tpm'

[bruno-]

We likely fixed this problem via #61. I'll close the issue now. If anyone reproduces this same problem again, please reopen.