[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Project Monitor losing recorded projects

From: Stefan Hett <stefan_at_egosoft.com>
Date: Thu, 2 Mar 2017 12:50:16 +0100

On 2/21/2017 7:58 PM, Stefan Küng wrote:
> On 21.02.2017 17:16, Stefan Hett wrote:
>> Hi,
>> it happened regularly in the past for me that all the projects I added
>> to the project monitor suddenly vanished. I think it corresponded to the
>> cases where I installed the nightly build of TSVN 1.9. Is there a known
>> limitation in this regards and/or does that ring a bell directly on what
>> might cause this behavior?
>> Note that I'm using the project monitor successfully for a couple of
>> months on a different machine where I don't use nightly builds. There, I
>> never ran into this problem of projects being reset.
>> @StefanK in case you are picking this up: Please don't spend much time
>> on it. It might very well be a local issue and I would not feel good if
>> that post would cause you wasting time on a none-issue. I'll get back on
>> this one if it becomes more annoying and I actually invest some time in
>> debugging the problem myself...
> The project monitor settings are saved to
> %appdata%\TortoiseSVN\MonitoringData.ini.
> They're saved on exit and loaded on start, with a retry count of 5 and a
> wait time between tries of half a second.
> There's even a backup file MonitoringData_backup.ini in case the
> original file can't be loaded.
> Not sure how it can happen that both files get corrupted on your machine.
> But you can export all the settings (including the project monitor data)
> from the settings dialog->Sync->Export settings to file...
> If you do that, then you can restore all data easily again with the
> "Import Settings from file..." button in the same dialog.
> Also, you can set up a sync location, e.g. in your onedrive folder which
> then makes all settings sync across machines - and as a bonus it also
> creates a backup of your settings.

Thanks for the info. I just got some time to run a couple of tests
(up-/downgrading TSVN) on my machine. Unfortunately, I could not
reproduce the issue.
I'll get back toit, if it ever reoccurs (and then will double check the
content of the MonitoringData.ini-file - comparing it to the daily
backup I already do for my machine (unfortunately I don't have the old
backup at the point where the issue occurred last time, so couldn't look
things up there)).

If I'm not getting back to it, let's assume it was just some TSVN
independent local temporary issue associated with something on my
machine, rather than some issue in TSVN.

Stefan Hett
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-03-04 02:19:02 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.