git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] enable "no-done" extension only when fetching over smart-http

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 29, 2011, 17:16 UTC
Message-ID
<7vlizxsv82.fsf@alter.siamese.dyndns.org>

When 'no-done' protocol extension is used, the upload-pack (i.e. the server side) process stops listening to the fetch-pack after issuing the final NAK, and starts sending the generated pack data back, but there may be more "have" send by the latter in flight that the fetch-pack is expecting to be responded with ACK/NAK. This will typically result in a deadlock (both will block on write that the other end never reads) or SIGPIPE on the fetch-pack end (upload-pack will finish writing a small pack and goes away).

Disable it unless fetch-pack is running under smart-http, where there is no such streaming issue.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 builtin/fetch-pack.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/builtin/fetch-pack.c b/builtin/fetch-pack.c
index 59fbda5..52707a8 100644
--- a/builtin/fetch-pack.c
+++ b/builtin/fetch-pack.c
@@ -708,7 +708,8 @@ static struct ref *do_fetch_pack(int fd[2],
 		if (server_supports("no-done")) {
 			if (args.verbose)
 				fprintf(stderr, "Server supports no-done\n");
-			no_done = 1;
+			if (args.stateless_rpc)
+				no_done = 1;
 		}
 	}
 	else if (server_supports("multi_ack")) {
Next: Shawn Pearce
Message 1 of 5 in “enable "no-done" extension only when fetching over smart-http”
  1. enable "no-done" extension only when fetching over smart-httpJunio C Hamano, Mar 29, 2011
  2. Shawn PearceMar 29, 2011
  3. enable "no-done" extension only when serving over smart-httpJunio C Hamano, Mar 29, 2011
  4. Shawn PearceMar 29, 2011
  5. enable "no-done" extension only when serving over smart-httpJunio C Hamano, Mar 29, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.