From: Junio C Hamano <firstname.lastname@example.org> To: "Han Xin" <email@example.com> Cc: "Git List" <firstname.lastname@example.org>, "蒋鑫(知忧)" <email@example.com> Subject: Re: [PATCH v3] send-pack: run GPG after atomic push checking Date: Sat, 19 Sep 2020 16:02:07 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Han Xin's message of "Sat, 19 Sep 2020 22:47:50 +0800") "Han Xin" <firstname.lastname@example.org> writes: > The refs update commands can be sent to the server side in two different > ways: GPG-signed or unsigned. We should run these two operations in the > same "Finally, tell the other end!" code block, but they are seperated > by the "Clear the status for each ref" code block. This will result in > a slight performance loss, because the failed atomic push will still > perform unnecessary preparations for shallow advertise and GPG-signed > commands buffers, and user may have to be bothered by the (possible) GPG > passphrase input when there is nothing to sign. The above sounds as if we care about the performace loss and that is the main motivation behind this change. Intended? I have an impression that it is a hard-sell as a "performance improvement" patch, as the saved cycles are negligible compared to everything else that is done in the flow, and more importantly, it optimizes for the wrong case (i.e. it fails more efficiently). > Add a new test case to t5534 to ensure GPG will not be called when the > GPG-signed atomic push fails. > > Signed-off-by: Han Xin <email@example.com> > --- ... > + test_must_fail env PATH="$TRASH_DIRECTORY:$PATH" git push \ > + --signed --atomic --porcelain \ > + dst noop ff noff >out 2>&1 && > + > + test_i18ngrep ! "gpg failed to sign" out && OK, that is much less brittle than the "output must match these lines exactly" test we saw earlier. > + sed -n -e "/^To dst/,$ p" out >actual && > + cat >expect <<-EOF && > + To dst > + = refs/heads/noop:refs/heads/noop [up to date] > + ! refs/heads/ff:refs/heads/ff [rejected] (atomic push failed) > + ! refs/heads/noff:refs/heads/noff [rejected] (non-fast-forward) > + Done > + EOF > + test_i18ncmp expect actual Didn't you mean to remove this part, which makes the whole test more brittle than necessary? Thanks.
next prev parent reply other threads:[~2020-09-19 23:02 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-15 9:58 [PATCH 1/2] t5534: new test case for atomic signed push Han Xin 2020-09-15 9:58 ` [PATCH 2/2] send-pack: check atomic push before running GPG Han Xin 2020-09-15 21:02 ` Junio C Hamano 2020-09-15 21:40 ` Junio C Hamano 2020-09-16 1:53 ` Jiang Xin 2020-09-16 4:37 ` Junio C Hamano 2020-09-16 11:49 ` Jiang Xin 2020-09-16 23:44 ` Junio C Hamano 2020-09-18 4:50 ` [PATCH v2] send-pack: run GPG after atomic push checking Han Xin 2020-09-19 0:02 ` Junio C Hamano 2020-09-19 14:47 ` [PATCH v3] " Han Xin 2020-09-19 23:02 ` Junio C Hamano [this message] 2020-09-20 6:20 ` [PATCH v4] " Han Xin 2020-09-16 17:35 ` [PATCH 2/2] send-pack: check atomic push before running GPG 韩欣(炽天) 2020-09-15 20:31 ` [PATCH 1/2] t5534: new test case for atomic signed push Junio C Hamano 2020-09-16 0:34 ` brian m. carlson 2020-09-15 20:34 ` Junio C Hamano
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v3] send-pack: run GPG after atomic push checking' \ /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
Code repositories for project(s) associated with this 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).