> > svn: REPORT request failed on '/svnroot/magnus/!svn/vcc/default'
> > svr: REPORT of '/svnroot/magnus/!svn/vcc/default': Could not read response body: Secure connection truncated (https://svn.sourceforge.net)
>
> Something is very messed up with sourceforge's svn server. Report
> this to sourceforge! It's not normal at all.
I fully agree that sourceforge is broken. My gut feel (and this is
just a guess) is that SVN relies heavily on tmp space in order to
do 'transactions'. sourceforge probably randomly runs out of tmp space
depending on how many SVN sessions are running. Since sourceforge would
not SEE the errors they can validly claim that it isn't their fault.
My issue isn't with the setup of the system but with the design. It
is my belief that SVN does not properly recover from these failures in
any convenient way. It should be possible to automatically retry a
transaction or, if not that, to restart a transaction. Network and
storage errors are usually temporary but SVN does not recover well at
all. Often times my work system gets wedged into a state with 'locks'.
In work we use 'tortoise' as a windows cover and it recommends that we
run cleanup. (BTW, why have cleanup? Why not just fail to a clean
state instead?) Cleanup takes a long time and NEVER succeeds. Once a
transaction fails SVN leaves the world in a broken state and the only
recovery action available is to redo the work.
Clearly SVN 'works' since I can do a checkout followed by 10 updates
and I get all my code back. It 'works' in theory.
A code archive is just a way to store and recover work.
It should be as robust as a copy operation and just as easy to use.
Imagine if copy 'locked' your source directory so you couldn't
restart the copy. And the cleanup command couldn't fix it?
Would that be a reasonable design for the 'cp' command?
Claiming I'm an 'outlier' on the usage curve is not solution.
Perhaps I'm using SVN in some stupid way and don't know all of the
special switches. But really, how hard is this? Checkout, change,
commit. That's all I ever do. It should 'just work'.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 2 17:20:11 2006