We are using:
- Win 7 Laptops
- Flare 8.1 bound to subversion source control
- 4 occurances: on 2 different laptops
On 4 occasions, we have lost our local SVN repository in the blink of an eye. It often happens when another error occurs, such as PuTTY or a network error. Once you click OK, you realize ALL of your content is gone. Sometimes it is just the content folder, sometimes it the entire project. If we use SVN tools, we can download a new set of files because the SVN server thinks we are up to date. The only recourse was to delete what ever is left and import a new version from the SVN repository.
Today, we noticed a new twist that we didn't notice before. The content folder was eradicated, however, when I tried to delete what appeared to be an empty project folder, it stated that there was still 500+MB of data in the folder. In essence, it is like the files and folders were suddenly hidden. This makes sense since the files never appear in the recycle bin and the deletion occurs faster than Windows can actually delete a folder of that size. The next time this happens, we will investigate resolving the problem with an eye that the files were now hidden.
Has ANYONE else seen this? Resolving this takes hours so I'd prefer not to have to rebuild my local repository when this happens. I have reported this to the support folks.
Flare + SVN: Local Repository instantly wiped out!
-
Penthesilea
- Propeller Head
- Posts: 10
- Joined: Thu Aug 16, 2012 5:15 pm
-
kevinthekingsson
- Jr. Propeller Head
- Posts: 9
- Joined: Wed Apr 17, 2013 10:04 am
Re: Flare + SVN: Local Repository instantly wiped out!
We have had an experience that may shed some light on this. Our newly-installed Raid server failed after putting all our projects under Source Control and no-one had got around to scheduling the backups. So it fell to me to attempt to restore them from my local copies.
After reading around a bit, I decided that it would be basically a matter of unbinding my projects from Source Control, recreating the main repository directory and re-binding the projects. Not too difficult, I thought.
So I opened my first project, carefully declined the offer to get the latest versions, and apart from an obscure 'file:' error at one point, things seemed to be OK. I could see my local files in the contents and projects panels and even successfully opened one. I can't recall the exact sequence of events; but I was on the point of unbinding the project when I suddenly found that my project and contents folders were now empty!
It took a lot of hard work to rebuild that project, by tediously generating a new project from a copy of the .chm file (that had fortunately not been deleted) and comparing that with a pre-Source Control backup. Fortunately, I then found an easier and safer way of restoring my remaining projects, which I have described here: http://forums.madcapsoftware.com/viewto ... &sk=t&sd=a
Afterwardsm, I tried a number of experiments to figure out exactly how Flare came to wipe my local copy: but have been unable to reproduce it exactly. This may be because:
1. Deleting the repository's project directory using Tortoise SVN has a less drastic effect than an uncontrolled kill of the entire repository,
or,
2. My recollection of exactly what I did and when is not entirely accurate.
I know that, (a) when I first loaded the project, the local svn directory was still present, (b) that I responded 'No' when prompted to get the latest copies of the files and (c) that all files subsequently appeared to be present and correct. But I do remember that 'file:' error message which, at the time, didn't seem to have caused any serious problem. The only time I have seen a similar message since then was during an attempted update after the repository folder had been deleted - an action that will, without fail, wipe the local directory. Since the option to perform automatic updates before compiling was set, it's possible that attempting to view the target files triggered a compilation, which in turn triggered the automatic update.
One would not have thought that attempting to update the local folders from an empty or unavailable directory should have this effect: but it does - and it does so without warning! Seemingly Flare, or VPN, treats a missing file as being more 'up-to-date' than an existing file in these circumstances, and deletes it without trace. Having read the comments in the original post, I spent many hours with a data recovery tool, scouring my hard disk for any trace of the lost files, but found only relics of temporary files and pre-Source Control versions.
This is a bug that really needs to be fixed!
After reading around a bit, I decided that it would be basically a matter of unbinding my projects from Source Control, recreating the main repository directory and re-binding the projects. Not too difficult, I thought.
So I opened my first project, carefully declined the offer to get the latest versions, and apart from an obscure 'file:' error at one point, things seemed to be OK. I could see my local files in the contents and projects panels and even successfully opened one. I can't recall the exact sequence of events; but I was on the point of unbinding the project when I suddenly found that my project and contents folders were now empty!
It took a lot of hard work to rebuild that project, by tediously generating a new project from a copy of the .chm file (that had fortunately not been deleted) and comparing that with a pre-Source Control backup. Fortunately, I then found an easier and safer way of restoring my remaining projects, which I have described here: http://forums.madcapsoftware.com/viewto ... &sk=t&sd=a
Afterwardsm, I tried a number of experiments to figure out exactly how Flare came to wipe my local copy: but have been unable to reproduce it exactly. This may be because:
1. Deleting the repository's project directory using Tortoise SVN has a less drastic effect than an uncontrolled kill of the entire repository,
or,
2. My recollection of exactly what I did and when is not entirely accurate.
I know that, (a) when I first loaded the project, the local svn directory was still present, (b) that I responded 'No' when prompted to get the latest copies of the files and (c) that all files subsequently appeared to be present and correct. But I do remember that 'file:' error message which, at the time, didn't seem to have caused any serious problem. The only time I have seen a similar message since then was during an attempted update after the repository folder had been deleted - an action that will, without fail, wipe the local directory. Since the option to perform automatic updates before compiling was set, it's possible that attempting to view the target files triggered a compilation, which in turn triggered the automatic update.
One would not have thought that attempting to update the local folders from an empty or unavailable directory should have this effect: but it does - and it does so without warning! Seemingly Flare, or VPN, treats a missing file as being more 'up-to-date' than an existing file in these circumstances, and deletes it without trace. Having read the comments in the original post, I spent many hours with a data recovery tool, scouring my hard disk for any trace of the lost files, but found only relics of temporary files and pre-Source Control versions.
This is a bug that really needs to be fixed!
Re: Flare + SVN: Local Repository instantly wiped out!
I spent many hours with a data recovery tool, scouring my hard disk for any trace of the lost files, but found only relics of temporary files and pre-Source Control versions.