public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bill Hoffman <bill.hoffman@kitware.com>
To: cygwin@cygwin.com, jeremy@bopp.net
Subject: Re: git and openssh issue
Date: Thu, 22 Jul 2010 15:22:00 -0000	[thread overview]
Message-ID: <4C485D3D.7070307@kitware.com> (raw)
In-Reply-To: <4C4677CA.2090608@bopp.net>

On 7/21/2010 12:30 AM, Jeremy Bopp wrote:

>> http://git.661346.n2.nabble.com/Error-when-cloning-gc-ed-repository-td4425832.html
>>
>>
>> Basically, it is this random error:
>> fatal: early EOFs:  47% (657/1396)
>>
>>
>> Seems like an issue with openssh and not git as using plink fixes the
>> problem.   Anyway, with some direction I would be willing to help, I
>> have a very reproducible case of this.
>
> I haven't been able to reproduce this problem myself, but I was thinking
> that using plink rather than ssh also eliminates a bit of Cygwin pipe
> handling performed under ssh.  It might be useful to see if this can be
> reproduced another way such as over something relatively basic like rsh.
>   If the problem reproduces with rsh, that should point more directly to
> a problem with the Cygwin DLL rather than ssh.
>
> Do you have control over the server hosting the repository you're
> cloning such that you can try that out?  If not, have you tried setting
> up your own server with a complete clone of the repository to see if you
> can reproduce the problem when cloning from that one?
>

OK, I was able to test with rsh and it works.  So with the following 
install:
   cygwin                  1.7.5-1
   openssh                 5.5p1-2
   openssl                 0.9.8o-2
   rsh                     0.17-1

rsh works no problem.   ssh fails to clone with the EOF error.  Windows 
plink also works with no problem.


Are there any other experiments you would like to see?   Seems to happen 
with any reasonable size git repo.  So, if you were to say clone VTK or 
Qt, I am sure you could reproduce this as well.

-Bill



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2010-07-22 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 17:15 Bill Hoffman
2010-07-21  5:48 ` Jeremy Bopp
2010-07-22 15:22   ` Bill Hoffman [this message]
2010-07-22 15:49     ` Jeremy Bopp
2010-07-22 19:49       ` Bill Hoffman
2010-07-22 23:48         ` Jeremy Bopp
2010-07-23  1:53           ` Bill Hoffman
2010-07-23 16:28             ` Jeremy Bopp
2010-07-23 17:01               ` git and openssh issue (eblake?) Christopher Faylor
2010-08-02 14:08                 ` Bill Hoffman
2010-08-12 13:46                   ` Bill Hoffman
2010-10-03  2:54                 ` Christopher Faylor

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=4C485D3D.7070307@kitware.com \
    --to=bill.hoffman@kitware.com \
    --cc=cygwin@cygwin.com \
    --cc=jeremy@bopp.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).