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

Re: [PATCH v10 24/44] fetch.c: use a single ref transaction for all ref updates

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
May 17, 2014, 15:17 UTC
Message-ID
<53777D89.2090501@alum.mit.edu>
In-Reply-To
<53777AA1.1020107@alum.mit.edu>
On 05/17/2014 05:05 PM, Michael Haggerty wrote:
Show 13 quoted lines
> On 05/16/2014 07:37 PM, Ronnie Sahlberg wrote:
>> [...]
>> disk and thus we would not return STORE_REF_ERROR_DF_CONFLICT for this case.
>>
>> I think this new behaviour is more correct, since if there was a problem
>> we would not even try to commit the transaction but need to highlight this
>> change in how/what errors are reported.
>> This change in what error is returned only occurs if there are multiple
>> refs that fail to update and only some, but not all, of them fail due to
>> ENOTDIR.
> 
> Thanks for the detailed explanation.  The change in behavior seems
> reasonable to me.
Wait, now I'm having second thoughts.

Won't the old code display *all* of the errors that occur, each time proceeding nevertheless? Whereas the new code displays only the *first* error that would occur and then aborts?

This could be very frustrating if three references have problems, but the user only finds out about one problem each time she runs "git fetch". Instead of

    git fetch # oops, ref1, ref2, and ref3 failed
    fix, fix, fix
    git fetch # :-)
she'd have to do
    git fetch # oops, ref1 failed
    fix ref1
    git fetch # oops, ref2 failed
    fix ref2
    git fetch # oops, ref3 failed
    fix ref3
    git fetch # :-( git I hate you

What kind of failures are we talking about here? Are we talking about errors like non-ff updates that happen routinely, or rarer/more serious errors that would be expected to happen singly?

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Michael HaggertyNext: Ronnie Sahlberg
Message 38 of 65 in “Use ref transactions for all ref updates”
  1. 00/44 Use ref transactions for all ref updatesRonnie Sahlberg, May 16, 2014
  2. 01/44 refs.c: constify the sha arguments for ref_transaction_create|delete|updateRonnie Sahlberg, May 16, 2014
  3. 02/44 refs.c: allow passing NULL to ref_transaction_freeRonnie Sahlberg, May 16, 2014
  4. 03/44 refs.c: add a strbuf argument to ref_transaction_commit for error loggingRonnie Sahlberg, May 16, 2014
  5. 04/44 refs.c: add an err argument to repack_without_refsRonnie Sahlberg, May 16, 2014
  6. Michael HaggertyMay 17, 2014
  7. Ronnie SahlbergMay 27, 2014
  8. 05/44 refs.c: make ref_update_reject_duplicates take a strbuf argument for errorsRonnie Sahlberg, May 16, 2014
  9. 06/44 refs.c: add an err argument to delete_ref_looseRonnie Sahlberg, May 16, 2014
  10. 07/44 refs.c: make update_ref_write update a strbuf on failureRonnie Sahlberg, May 16, 2014
  11. 08/44 update-ref.c: log transaction error from the update_refRonnie Sahlberg, May 16, 2014
  12. 09/44 refs.c: remove the onerr argument to ref_transaction_commitRonnie Sahlberg, May 16, 2014
  13. 10/44 refs.c: change ref_transaction_update() to do error checking and return statusRonnie Sahlberg, May 16, 2014
  14. 11/44 refs.c: change ref_transaction_create to do error checking and return statusRonnie Sahlberg, May 16, 2014
  15. 12/44 refs.c: ref_transaction_delete to check for error and return statusRonnie Sahlberg, May 16, 2014
  16. 13/44 tag.c: use ref transactions when doing updatesRonnie Sahlberg, May 16, 2014
  17. Michael HaggertyMay 17, 2014
  18. Ronnie SahlbergMay 19, 2014
  19. Ronnie SahlbergMay 19, 2014
  20. 14/44 replace.c: use the ref transaction functions for updatesRonnie Sahlberg, May 16, 2014
  21. Michael HaggertyMay 17, 2014
  22. Ronnie SahlbergMay 19, 2014
  23. 15/44 commit.c: use ref transactions for updatesRonnie Sahlberg, May 16, 2014
  24. 16/44 sequencer.c: use ref transactions for all ref updatesRonnie Sahlberg, May 16, 2014
  25. 17/44 fast-import.c: change update_branch to use ref transactionsRonnie Sahlberg, May 16, 2014
  26. 18/44 branch.c: use ref transaction for all ref updatesRonnie Sahlberg, May 16, 2014
  27. Michael HaggertyMay 17, 2014
  28. Ronnie SahlbergMay 19, 2014
  29. 19/44 refs.c: change update_ref to use a transactionRonnie Sahlberg, May 16, 2014
  30. 20/44 refs.c: free the transaction before returning when number of updates is 0Ronnie Sahlberg, May 16, 2014
  31. 21/44 refs.c: ref_transaction_commit should not free the transactionRonnie Sahlberg, May 16, 2014
  32. 22/44 fetch.c: clear errno before calling functions that might set itRonnie Sahlberg, May 16, 2014
  33. Michael HaggertyMay 17, 2014
  34. Ronnie SahlbergMay 27, 2014
  35. 23/44 fetch.c: change s_update_ref to use a ref transactionRonnie Sahlberg, May 16, 2014
  36. 24/44 fetch.c: use a single ref transaction for all ref updatesRonnie Sahlberg, May 16, 2014
  37. Michael HaggertyMay 17, 2014
  38. Michael HaggertyMay 17, 2014
  39. 25/44 receive-pack.c: use a reference transaction for updating the refsRonnie Sahlberg, May 16, 2014
  40. Michael HaggertyMay 17, 2014
  41. Ronnie SahlbergMay 19, 2014
  42. Michael HaggertyMay 23, 2014
  43. Ronnie SahlbergMay 23, 2014
  44. Michael HaggertyMay 23, 2014
  45. Ronnie SahlbergMay 27, 2014
  46. 26/44 fast-import.c: use a ref transaction when dumping tagsRonnie Sahlberg, May 16, 2014
  47. 27/44 walker.c: use ref transaction for ref updatesRonnie Sahlberg, May 16, 2014
  48. 28/44 refs.c: make write_ref_sha1 staticRonnie Sahlberg, May 16, 2014
  49. 29/44 refs.c: make lock_ref_sha1 staticRonnie Sahlberg, May 16, 2014
  50. 30/44 refs.c: add transaction.status and track OPEN/CLOSED/ERRORRonnie Sahlberg, May 16, 2014
  51. 31/44 refs.c: remove the update_ref_lock functionRonnie Sahlberg, May 16, 2014
  52. 32/44 refs.c: remove the update_ref_write functionRonnie Sahlberg, May 16, 2014
  53. 33/44 refs.c: remove lock_ref_sha1Ronnie Sahlberg, May 16, 2014
  54. 34/44 refs.c: make prune_ref use a transaction to delete the refRonnie Sahlberg, May 16, 2014
  55. 35/44 refs.c: make delete_ref use a transactionRonnie Sahlberg, May 16, 2014
  56. 36/44 refs.c: pass the ref log message to _create/delete/update instead of _commitRonnie Sahlberg, May 16, 2014
  57. 37/44 refs.c: pass NULL as *flags to read_ref_fullRonnie Sahlberg, May 16, 2014
  58. 38/44 refs.c: pack all refs before we start to rename a refRonnie Sahlberg, May 16, 2014
  59. 39/44 refs.c: move the check for valid refname to lock_ref_sha1_basicRonnie Sahlberg, May 16, 2014
  60. 40/44 refs.c: call lock_ref_sha1_basic directly from commitRonnie Sahlberg, May 16, 2014
  61. 41/44 refs.c: add a new flag for transaction delete for refs we know are packed onlyRonnie Sahlberg, May 16, 2014
  62. 42/44 refs.c: pass a skip list to name_conflict_fnRonnie Sahlberg, May 16, 2014
  63. 43/44 refs.c: make rename_ref use a transactionRonnie Sahlberg, May 16, 2014
  64. 44/44 refs.c: remove forward declaration of write_ref_sha1Ronnie Sahlberg, May 16, 2014
  65. Jonathan NiederMay 16, 2014

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.