Closed GoogleCodeExporter closed 8 years ago
Can the next Tortoise release use the older (stable) version of the serf
library if the fix is not available yet? Most updates I do now require half a
dozen or more cleanups due to the frequent crashes.
Original comment by NickGlas...@gmail.com
on 2 Jun 2014 at 6:31
I second that, any checkout (or update) of a large repo fails requiring
multiple clean-ups.
Original comment by bthhar...@gmail.com
on 3 Jun 2014 at 8:38
I had to revert to version 1.8.4, Build 24972 to be able to complete my
checkout.
Original comment by sebastie...@gmail.com
on 4 Jun 2014 at 12:49
it happened to me using this versions (from the about box):
TortoiseSVN 1.8.7, Build 25475 - 64 Bit , 2014/05/05 20:52:12
Subversion 1.8.9, -release
apr 1.5.1
apr-util 1.5.3
serf 1.3.5
OpenSSL 1.0.1g 7 Apr 2014
zlib 1.2.8
Original comment by alexande...@hdle.com
on 6 Jun 2014 at 9:31
Hello:
This issue happened to one of my test users. When she tried to checkout a large
repository with TortoiseSVN 1.8.7 (64-bit), the application crashed. Gladly,
the user didn't upgrade her saved repository to the new version; so we were
able to download and use an older version of TortoiseSVN.Is there any update
for a new version?
Thanks
Original comment by dsenec...@gmail.com
on 9 Jun 2014 at 8:05
[deleted comment]
excerpt from the serf issue tracker:
"we released serf 1.3.6 last Monday to revert the original problematic change
from the 1.3.x line.
A new TortoiseSVN release with serf 1.3.6 should resolve the issue."
Original comment by alexande...@hdle.com
on 13 Jun 2014 at 1:41
about box info from the latest nightly build of the trunk:
TortoiseSVN 1.8.7, Build 25568 - 64 Bit -dev, 2014/06/11 20:21:33
Subversion 1.8.9, -release
apr 1.5.1
apr-util 1.5.3
serf 1.3.6
OpenSSL 1.0.1h 5 Jun 2014
zlib 1.2.8
its assumed the issue is gone with that.
I am unable to verify it as I don't have the needed it-always-happens test
environment right here to my hands.
Original comment by alexande...@hdle.com
on 13 Jun 2014 at 1:58
[deleted comment]
For what it's worth, I duly had this bug display in my browser when I attempted
to check-out anew a large code tree using TortoiseSVN 2013/11/11 21:33:57
(r24944) against Subversion 1.8.5.
(I really think this feature of when a crash occurs, the user is immediately
taken to this bug page, is neat. Bravo.)
If someone will point me to a Windows Build that they want me to test with to
see if the "serf issue" is fixed, I have a good example of a large directory
tree that I can try to check out that causes the problem to manifest itself.
Original comment by jlpool...@gmail.com
on 13 Jun 2014 at 6:11
@jplool...
please try out the latest nightly build of the trunk.
Original comment by alexande...@hdle.com
on 16 Jun 2014 at 7:33
The latest nightly build (r25597) fails on my project:
"Error ra_serf: the server sent a truncated HTTP response body."
TortoiseSVN 1.8.7 crashes without errors.
I'm using SVN server 1.8.8.
To solve the problem necessarily update the server to the latest version
(1.8.9)?
Original comment by Sergey.S...@gmail.com
on 20 Jun 2014 at 10:18
the latest build r25602 works.
Original comment by RalphThe...@gmail.com
on 22 Jun 2014 at 3:10
FWIW, I'm experiencing the problem checking out an empty repository with r25597.
Original comment by patchett...@gmail.com
on 25 Jun 2014 at 9:03
So annoying :(
Original comment by edua...@bestrafender.com
on 1 Jul 2014 at 4:22
@edua...
please provide details of the version you used.
can you give the latest nightly build a try?
Original comment by alexande...@hdle.com
on 1 Jul 2014 at 4:35
Where can you download the latest nightly build for x64? I tried here
http://nightlybuilds.tortoisesvn.net/latest/x64/full/ but the msi file says
only 60k on the size and when i try to execute it I get an error that it is not
a valid windows installer image.
Original comment by juniver...@gmail.com
on 10 Jul 2014 at 7:52
@Juniver:
I (as a T-SVN user) took a look at that location.
When virtually sorting the file listing after the modification date starting
with about 2014-Jul-11 02:55:26 (a language file) the file sizes are getting
doubtful small or even zero. Currently the main application file for 64bits is
just zero bytes.
To me it looks like there is a quota problem - the file storage of the project
is used up and data of new files can only be stored when some other files will
get deleted first. According to the log of the build upload did work - but
maybe the uploader missed the fact that some of the files got truncated. -
Thats a two item thing: a somewhat broken uploader script and a media that ran
full.
-> the nightly build is sort of broken at present for its publishing step. FIX
NEEDED!
going for the whole tree - there is only this single subdir. i found no build
history for e.g. the last 2 weeks or similar.
.
BTW: don't you (=developers) have MD5 sums or SHA256 sums along with respective
files to publish for the nightly build? at least i can not see any such file in
those folder.
Original comment by alexande...@hdle.com
on 11 Jul 2014 at 8:20
I'm apparently getting this issue if I try to save my password along with the
SVN Action. If I chose to not save my password, then everything works fine. I
did change my password recently, and I'm speculating that the length of the
password is an issue. I changed from a 29 Character long password to a 34
Character Password. Might this be the cause?
Original comment by aardm...@gmail.com
on 21 Jul 2014 at 1:23
I had this issue when changing password fot the first time while committing, my
password is only 8 characters long.
My version is (from about):
TortoiseSVN 1.8.7, Build 25475 - 64 Bit , 2014/05/05 20:52:12
Subversion 1.8.9, -release
apr 1.5.1
apr-util 1.5.3
serf 1.3.5
OpenSSL 1.0.1g 7 Apr 2014
zlib 1.2.8
Wonder if I can just remove SVN and install an older version ...
Original comment by pia.dann...@gmail.com
on 23 Jul 2014 at 5:32
@pia - its a known issue when you end up here. as you can read its a problem
introduced by an underlying third party library. the library got a work around
and T-SVN was adopting that version in its development path.
please try to use an actual nightly build if you feel the issue is impacting
noticeably on your works. - i just looked at the nightly build location and the
file sizes there do look to me like the problem with insufficient space for the
storage location might have vanished.
Original comment by alexande...@hdle.com
on 23 Jul 2014 at 7:49
I ran into this issue with a large merge today, but was able to get past it
after installing the latest version on the nightly builds link above.
Original comment by scytalez...@gmail.com
on 23 Jul 2014 at 6:35
@Alexande(r?)
Thanks a lot, but where do I find nightly builds?
Looking at "Downloads"
(https://code.google.com/p/tortoisesvn/downloads/list?can=1&q=&colspec=Filename+
Summary+Uploaded+ReleaseDate+Size+DownloadCount)
indicates release and upload dates in 2013.
Original comment by pia.dann...@gmail.com
on 24 Jul 2014 at 6:22
Found a kind of work-around for problems with password change.
I did a SVN-Update on a folder I was sure was up-to-date, password changed OK.
Then I started commit and it runs OK now.
Still I would like to have a fixed version, to avoid work-aorund so if someone
can provide link to nightly build I will be happy
:-)
Original comment by pia.dann...@gmail.com
on 24 Jul 2014 at 7:07
@pia
Catch the link:
http://nightlybuilds.tortoisesvn.net/1.8.x/x64/full/
:)
Original comment by Sergey.S...@gmail.com
on 24 Jul 2014 at 7:30
This error popped up when updating a folder with nested folders and files
having very long file paths and file names.
Using Win 7 64bit.
Original comment by angelo.q...@gmail.com
on 31 Jul 2014 at 7:20
[deleted comment]
This page seems to be visited relatively often. Just to avoid any superfluous
posts:
As anyone can read above - The problem is addressed for a while in the nightly
builds.
The link for downloading an adequate version was posted multiple times above
already.
Original comment by alexande...@hdle.com
on 4 Aug 2014 at 7:36
I'm having this problem also, it needs to do a lot of cleanups to do a proper
checkout.
Original comment by valterhe...@gmail.com
on 5 Aug 2014 at 12:07
Cannot merge branches with large numbers of files, especially with large file
sizes, e.g. jar files. Currently running build 25475. Is there a download of
TortoiseSVN that will work and fix the issue?
Original comment by jeff.b...@gmail.com
on 10 Sep 2014 at 7:34
You are running an old version. Try 1.8.8 (r25755)
Original comment by simon.to...@gmail.com
on 10 Sep 2014 at 7:59
After installing TortoiseSVN-1.8.8.25755-win32-svn-1.8.10.msi on my
workstation, I attempted to do a merge with a large number of files, some
of which were large jar files. The same error occurred after merging many
of the files:
"Error: ra_serf: The server sent a truncated HTTP response body."
Is there any other solution I might try?
New version installed 09/11/2014:
----
TortoiseSVN 1.8.8, Build *25755* - 32 Bit , 2014/08/10 14:44:06
Subversion 1.8.10, -release
apr 1.5.1
apr-util 1.5.3
serf 1.3.7
OpenSSL 1.0.1i 6 Aug 2014
zlib 1.2.8
Original comment by jeff.b...@gmail.com
on 11 Sep 2014 at 5:32
@Jeff - "Error: ra_serf: The server sent a truncated HTTP response body."
i am not that deep in the subject but know something got fixed with those build
that helped me.
but if you are seeing a similar item for your setup you might be in need for
more debugging. a truncated server message might be a problem of the server
rather than the client - but unless more details on the communication at your
setup is available i am not sure if a solution can be done. - if possible,
please provide more details, e.g. a debug log or some network trace. (not sure
how to enable that best, see the web - but its the item i would put my finger
upon first in your case.)
Original comment by alexande...@hdle.com
on 22 Sep 2014 at 10:06
I'm having this same error, and I know alexande...@hdle.com said that there is
an answer as to what to do somewhere in this posting... but I still can't
figure out what that is. I apologize if I seem like an idiot, but I am a motion
designer, so my knowledge on any of this is greatly limited. I tried going to
the nightly build link and wasn't sure what to download. I chose
TortoiseSVN-1.8.8.25955-dev-x64-svn-1.8.10.msi, installed it and still have the
same error. Any other ideas would be greatly appreciated!
Original comment by KSunderh...@gmail.com
on 20 Oct 2014 at 8:20
Original issue reported on code.google.com by
tortoisesvn
on 28 May 2014 at 6:14