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

Re: [PATCH v2 2/2] remote.c: remove BUG in show_push_unqualified_ref_name_error()

From
Patrick Steinhardt <ps@pks.im>
Date
Aug 5, 2025, 13:27 UTC
Message-ID
<aJIG3TNq5eSzwSPX@pks.im>
In-Reply-To
<2bd892b26c94133cd1a266d6ff4f2217418b0660.1754375026.git.liu.denton@gmail.com>
On Mon, Aug 04, 2025 at 11:24:40PM -0700, Denton Liu wrote:
Show 14 quoted lines
> When "git push <remote> <src>:<dst>" does not spell out the
> destination side of the ref fully, and when <src> is not given
> as a reference but an object name, the code tries to give advice
> messages based on the type of that object.
> 
> The type is determined by calling odb_read_object_info() and
> signalled by its return value.  The code however reported a
> programming error with BUG() when this function said that there
> is no such object, which happens when the object name is given
> as a full hexadecimal (if the object name is given as a partial
> hexadecimal or an non-existing ref, the function would have died
> without returning, so this BUG() wouldn't have triggered).  This
> is wrong.  It is an ordinary end-user mistake to give an object
> name that does not exist and treated as such.
Yup, makes sense.
Show 11 quoted lines
> diff --git a/remote.c b/remote.c
> index e965f022f1..4ad20110e9 100644
> --- a/remote.c
> +++ b/remote.c
> @@ -1218,8 +1218,7 @@ static void show_push_unqualified_ref_name_error(const char *dst_value,
>  			 "'%s:refs/tags/%s'?"),
>  		       matched_src_name, dst_value);
>  	} else {
> -		BUG("'%s' should be commit/tag/tree/blob, is '%d'",
> -		    matched_src_name, type);
> +		advise(_("The <src> part of the refspec is an oid that doesn't exist.\n"));

I think we should rather say "object ID", as "oid" is an abbreviation that might not be immediately obvious to the user. Also, should we continue to mention the object ID? Otherwise it might be hard for the user to figure out which object ID doesn't exist in case they pass multiple refspecs.

Patrick
Previous: Denton LiuNext: Denton Liu
Message 10 of 34 in “remote.c: remove erroneous BUG case”
  1. 0/2 remote.c: remove erroneous BUG caseDenton Liu, Aug 4, 2025
  2. 1/2 t5516: introduce 'push ref expression with non-existent oid src'Denton Liu, Aug 4, 2025
  3. 2/2 remote.c: remove BUG in show_push_unqualified_ref_name_error()Denton Liu, Aug 4, 2025
  4. Junio C HamanoAug 4, 2025
  5. 0/2 *** SUBJECT HERE ***Denton Liu, Aug 5, 2025
  6. 1/2 t5516: introduce 'push ref expression with non-existent oid src'Denton Liu, Aug 5, 2025
  7. Patrick SteinhardtAug 5, 2025
  8. Junio C HamanoAug 5, 2025
  9. 2/2 remote.c: remove BUG in show_push_unqualified_ref_name_error()Denton Liu, Aug 5, 2025
  10. Patrick SteinhardtAug 5, 2025
  11. 0/2 remote.c: remove erroneous BUG caseDenton Liu, Aug 6, 2025
  12. 1/2 t5516: remove surrounding empty lines in test bodiesDenton Liu, Aug 6, 2025
  13. Patrick SteinhardtAug 6, 2025
  14. 2/2 remote.c: remove BUG in show_push_unqualified_ref_name_error()Denton Liu, Aug 6, 2025
  15. Patrick SteinhardtAug 6, 2025
  16. Junio C HamanoAug 6, 2025
  17. remote.c: convert if-else tower to switchDenton Liu, Aug 7, 2025
  18. Patrick SteinhardtAug 7, 2025
  19. remote.c: convert if-else tower to switchDenton Liu, Aug 7, 2025
  20. Ben KnobleAug 7, 2025
  21. Eric SunshineAug 7, 2025
  22. Junio C HamanoAug 7, 2025
  23. 0/3 remote.c: remove erroneous BUG caseDenton Liu, Aug 8, 2025
  24. 1/3 t5516: remove surrounding empty lines in test bodiesDenton Liu, Aug 8, 2025
  25. 2/3 remote.c: convert if-else ladder to switchDenton Liu, Aug 8, 2025
  26. Patrick SteinhardtAug 8, 2025
  27. Denton LiuAug 8, 2025
  28. 3/3 remote.c: remove BUG in show_push_unqualified_ref_name_error()Denton Liu, Aug 8, 2025
  29. 0/3 remote.c: remove erroneous BUG caseDenton Liu, Aug 8, 2025
  30. 1/3 t5516: remove surrounding empty lines in test bodiesDenton Liu, Aug 8, 2025
  31. 2/3 remote.c: remove BUG in show_push_unqualified_ref_name_error()Denton Liu, Aug 8, 2025
  32. 3/3 remote.c: convert if-else ladder to switchDenton Liu, Aug 8, 2025
  33. Patrick SteinhardtAug 8, 2025
  34. Junio C HamanoAug 8, 2025

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.