Subclipse: Updating Change Sets for SVNStatusSubscriber (UPDATED - clock sync issue)

Question

I see this when digging into the error logs of Eclipse - I keep getting an error:

An internal error occurred during: "Updating Change Sets for SVNStatusSubscriber"

It happens a few times when trying to update or commit, and eventually hoses my local copy of SVN, and I'm forced to rebuild it.

Has anyone every encountered either of these or have any thoughts on fixing? It's a huge annoyance to have to rebuild SVN each time. I'm using Subclipse with Helios. Also I'm connected via FUSE/SSHfs to the project on a VM.

Answer 1

Did samba fix it? Have you tried using different client implementations?

Answer 2

Okay, so this is still not 100% certain, but it would appear that what's happened is that the date goes out of sync on the VM on occassion. During svn updates or commits, this causes inconsistent synchronization data and the client in Eclipse, confused, ends up throwing errors.

Because the errors cause an abort of the update or commit process, this leaves the repository in a very unstable state, my guess is that it tries to retrieve a name of a file but gets back null, and ends up writing this back to the .svn/entries somehow.

As I said I can't confirm that this is the only thing causing the problems, but it makes sense as after my clock went out of sync, pretty much all of svn was broken on the next svn up call.