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

Re: [PATCH v4 3/3] connect: advertized capability is not a ref

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 9, 2016, 20:40 UTC
Message-ID
<xmqqtwdoajt0.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160909194037.GG25016@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 16 quoted lines
> Jonathan Tan wrote:
>
>> --- a/connect.c
>> +++ b/connect.c
>> @@ -172,8 +173,24 @@ struct ref **get_remote_heads(int in, char *src_buf, size_t src_len,
>>  			continue;
>>  		}
>>  
>> +		if (!strcmp(name, "capabilities^{}")) {
>> +			if (saw_response)
>> +				warning("protocol error: unexpected capabilities^{}, "
>> +					"continuing anyway");
>
> Please use die() for these.
> ...
> The rest looks good.
Will squash this in, then.
 connect.c | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/connect.c b/connect.c
index df25d21..5ccbd10 100644
--- a/connect.c
+++ b/connect.c
@@ -175,11 +175,9 @@ struct ref **get_remote_heads(int in, char *src_buf, size_t src_len,
 
 		if (!strcmp(name, "capabilities^{}")) {
 			if (saw_response)
-				warning("protocol error: unexpected capabilities^{}, "
-					"continuing anyway");
+				die("protocol error: unexpected capabilities^{}");
 			if (got_dummy_ref_with_capabilities_declaration)
-				warning("protocol error: multiple capabilities^{}, "
-					"continuing anyway");
+				die("protocol error: multiple capabilities^{}");
 			got_dummy_ref_with_capabilities_declaration = 1;
 			continue;
 		}
@@ -188,8 +186,7 @@ struct ref **get_remote_heads(int in, char *src_buf, size_t src_len,
 			continue;
 
 		if (got_dummy_ref_with_capabilities_declaration)
-			warning("protocol error: unexpected ref after capabilities^{}, "
-				"using this ref and continuing anyway");
+			die("protocol error: unexpected ref after capabilities^{}");
 
 		ref = alloc_ref(buffer + GIT_SHA1_HEXSZ + 1);
 		oidcpy(&ref->old_oid, &old_oid);
Previous: Jonathan NiederNext: Junio C Hamano
Message 43 of 45 in “handle empty spec-compliant remote repos correctly”
  1. 0/2 handle empty spec-compliant remote repos correctlyJonathan Tan, Sep 2, 2016
  2. 2/2 connect: know that zero-ID is not a refJonathan Tan, Sep 2, 2016
  3. Jonathan NiederSep 2, 2016
  4. Shawn PearceSep 2, 2016
  5. Stefan BellerSep 2, 2016
  6. Shawn PearceSep 2, 2016
  7. Jeff KingSep 2, 2016
  8. Jonathan TanSep 2, 2016
  9. Jeff KingSep 2, 2016
  10. Shawn PearceSep 3, 2016
  11. Jeff KingSep 3, 2016
  12. 1/2 tests: move test_lazy_prereq JGIT to test-lib.shJonathan Tan, Sep 2, 2016
  13. 0/2 handle empty spec-compliant remote repos correctlyJonathan Tan, Sep 2, 2016
  14. 1/2 tests: move test_lazy_prereq JGIT to test-lib.shJonathan Tan, Sep 2, 2016
  15. Junio C HamanoSep 7, 2016
  16. 2/2 connect: advertized capability is not a refJonathan Tan, Sep 2, 2016
  17. Jonathan NiederSep 2, 2016
  18. Jeff KingSep 2, 2016
  19. Stefan BellerSep 2, 2016
  20. Jonathan NiederSep 3, 2016
  21. Jonathan NiederSep 2, 2016
  22. Jeff KingSep 3, 2016
  23. Junio C HamanoSep 7, 2016
  24. Junio C HamanoSep 7, 2016
  25. Jonathan NiederSep 7, 2016
  26. Junio C HamanoSep 7, 2016
  27. 0/2 handle empty spec-compliant remote repos correctlyJonathan Tan, Sep 7, 2016
  28. 1/2 tests: move test_lazy_prereq JGIT to test-lib.shJonathan Tan, Sep 7, 2016
  29. 2/2 connect: advertized capability is not a refJonathan Tan, Sep 7, 2016
  30. Jonathan NiederSep 8, 2016
  31. connect: tighten check for unexpected early hang up (Re: [PATCH v3 2/2] connect: advertized capability is not a ref)Jonathan Nieder, Sep 8, 2016
  32. Jonathan NiederSep 8, 2016
  33. Jonathan NiederSep 8, 2016
  34. Junio C HamanoSep 8, 2016
  35. Stefan BellerSep 8, 2016
  36. Junio C HamanoSep 8, 2016
  37. 0/3 handle empty spec-compliant remote repos correctlyJonathan Tan, Sep 9, 2016
  38. 1/3 tests: move test_lazy_prereq JGIT to test-lib.shJonathan Tan, Sep 9, 2016
  39. Torsten BögershausenSep 10, 2016
  40. Jeff KingSep 10, 2016
  41. 3/3 connect: advertized capability is not a refJonathan Tan, Sep 9, 2016
  42. Jonathan NiederSep 9, 2016
  43. Junio C HamanoSep 9, 2016
  44. Junio C HamanoSep 9, 2016
  45. 2/3 connect: tighten check for unexpected early hang upJonathan Tan, Sep 9, 2016

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.