From: Kim Gybels <kgybels@infogroep.be>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Jeff King <peff@peff.net>, Kim Gybels <kgybels@infogroep.be>
Subject: [PATCH 0/2] Fix early EOF with GfW daemon
Date: Thu, 12 Apr 2018 23:07:55 +0200 [thread overview]
Message-ID: <20180412210757.7792-1-kgybels@infogroep.be> (raw)
It has been reported [1] that cloning from a Git-for-Windows daemon would
sometimes fail with an early EOF error:
$ git clone git://server/test
Cloning into 'test'...
remote: Counting objects: 36, done.
remote: Compressing objects: 100% (24/24), done.
fatal: read error: Invalid argument
fatal: early EOF
fatal: index-pack failed
These patches solve the issue by only changing git-daemon, its child processes
can remain unaware that stdin/stdout are actually network connections.
[1] https://github.com/git-for-windows/git/issues/304
Kim Gybels (2):
daemon: use timeout for uninterruptible poll
daemon: graceful shutdown of client connection
daemon.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
--
2.17.0.windows.1
next reply other threads:[~2018-04-12 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:07 Kim Gybels [this message]
2018-04-12 21:07 ` [PATCH 1/2] daemon: use timeout for uninterruptible poll Kim Gybels
2018-04-13 12:36 ` Johannes Schindelin
2018-04-15 17:08 ` Kim Gybels
2018-04-18 21:16 ` Johannes Schindelin
2018-04-15 21:54 ` Junio C Hamano
2018-04-15 22:16 ` Junio C Hamano
2018-04-18 21:07 ` Johannes Schindelin
2018-04-18 21:51 ` Junio C Hamano
2018-04-19 21:33 ` Kim Gybels
2018-04-19 23:18 ` Junio C Hamano
2018-04-12 21:07 ` [PATCH 2/2] daemon: graceful shutdown of client connection Kim Gybels
2018-04-13 13:03 ` Johannes Schindelin
2018-04-15 20:21 ` Kim Gybels
2018-04-18 21:48 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180412210757.7792-1-kgybels@infogroep.be \
--to=kgybels@infogroep.be \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).