Georg Rehfeld <rehfeld@georg-rehfeld.de> wrote on 07/17/2006 09:47:00 PM:
> I'm using Subclipse since some month against the 'Gallery2' Sourceforge
> repository and have regularily problems, when synchronizing my working
> copy with the repository.
>
> The synch itself takes a loooooong time (10-30 minutes against 5533
> files in 3674 dirs not counting the .svn* files) obviously accessing my
> local copy extensively (disk accesses continuously) only sending/
> receiving few network packages (verified with Etherial). Thats annoying
> in the first place.
>
> But the real problem is: 95% of the time Subclipse is unable to finish
> the synch (after 10 minutes or so, beeing at 30% in the progress view)
> with this error:
Most likely the errors have killed the process so it really is not doing
anything any more.
> > Problems reported while synchronizing SVNStatusSubscriber. 0 of 1
> resources were synchronized.
> > An error occurred synchronizing /gallery2_CVS2SVN: Error getting
status
> for resource P/gallery2_CVS2SVN org.tigris.subversion.javahl.
> ClientException: RA layer request failed
> > svn: REPORT request failed on '/svnroot/gallery/!svn/vcc/default'
> > svn: REPORT of '/svnroot/gallery/!svn/vcc/default': Could not read
> response body: Secure connection truncated (https://svn.sourceforge.net)
> >
> > Error getting status for resource P/gallery2_CVS2SVN org.tigris.
> subversion.javahl.ClientException: RA layer request failed
> > svn: REPORT request failed on '/svnroot/gallery/!svn/vcc/default'
> > svn: REPORT of '/svnroot/gallery/!svn/vcc/default': Could not read
> response body: Secure connection truncated (https://svn.sourceforge.net)
> >
> > org.tigris.subversion.javahl.ClientException: RA layer request
failed
> > svn: REPORT request failed on '/svnroot/gallery/!svn/vcc/default'
> > svn: REPORT of '/svnroot/gallery/!svn/vcc/default': Could not read
> response body: Secure connection truncated (https://svn.sourceforge.net)
> >
I do not know what would cause these problems. Others have had them with
SourceForge too. All of the communucations is done in layers that are
beyond our control. Your best bet might be to replicate some of the
errors using the command line (not in Cygwin if possible). Then report to
the Subversion users@ list.
For Synchronize, we would be running a command like:
svn status -u -v
From the project root (or whatever you selected).
> The very same error sometimes shows up, when updating from the
> repository, but in that case part of my working copy is brought in synch
> with the repository at least. Repeated updates then finally finish.
>
> A 'switch' to some other repository version is prone to the same
> problem as reported: it NEVER finishes.
Command line would be "svn switch".
> I'm unsure, where the problem really is:
> - I actually could synch sometimes (very seldom)
> - One Sourceforge person suspected their setup using a https proxy
> - Some other Gallery devs seem to NOT experience the problem
> - I have seen similar probs when trying to 'switch' using the command
> line cygwin svn client.
The best bet would be to widen your audience. Use a standard Windows
command line client or even better would be Linux. See if you can trigger
some of the same problems. If you can, it will be easier to ger other
people to look at it. If you can't, then maybe there are some clues for
us in that. Operations like "switch" and "update" should work the same in
Subclipse and command line as we are doing little more than running the
same command. There is a bit more happening when doing a Synchronize, so
it is at least conceivable that we are doing something (like run multiple
commands at once) that you could not easily recreate from a command line.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jul 18 14:54:48 2006