From: Graeme Geldenhuys <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Re: 'git svn fetch' keeps giving a error after freezing
Date: Fri, 10 Jul 2009 09:07:13 +0200 [thread overview]
Message-ID: <h36pc1$4cv$1@ger.gmane.org> (raw)
In-Reply-To: <h31vg6$b38$1@ger.gmane.org>
Graeme Geldenhuys wrote:
>
> ==============================
> $ git svn fetch
> .....
> A fixes_2_0/fv/gadgets.pas
> A fixes_2_0/fv/colortxt.pas
> A fixes_2_0/fv/outline.pas
> RA layer request failed: REPORT of '/svn/fpc/!svn/vcc/default': Could
> not read response body: connection was closed by server
> (http://svn2.freepascal.org) at /usr/local/libexec/git-core/git-svn line
> 4505
> ==============================
It seems this issue has nothing to do with Git. It's a bug in the TCP
traffic handling in all SVN clients from Collabnet. Here is a recent bug
report about this exact issue.
http://sourceforge.net/apps/trac/sourceforge/ticket/1576
The problem gets triggered on slow connections and large revisions
(commits) or large files.
Our slow connection is probably why I keep getting the issue. Even
though we have a 4MB ADSL connection, we hardly ever reach that speeds.
Plus some more research revealed the shaped ADSL connection goes through
our ISP's transparent proxy, making the connection even more flaky/slow.
Luckily the FPC repository has an alternative port that it listens to as
well (port 8080) which bypasses the transparent proxy. Using the new
port, the 'git svn fetch' is flying!!!! :-) At Last!
Thanks to all that tried to help me...
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
prev parent reply other threads:[~2009-07-10 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:21 'git svn fetch' keeps giving a error after freezing Graeme Geldenhuys
2009-07-08 23:59 ` Eric Wong
2009-07-09 8:51 ` Graeme Geldenhuys
2009-07-09 8:52 ` Graeme Geldenhuys
2009-07-09 9:34 ` Yann Dirson
2009-07-09 12:46 ` Graeme Geldenhuys
2009-07-09 12:01 ` Michael J Gruber
2009-07-10 7:07 ` Graeme Geldenhuys [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h36pc1$4cv$1@ger.gmane.org' \
--to=graemeg@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).