Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receive/refresh keys in parallel #17

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

desultory
Copy link
Contributor

This should cut the runtime in half

@thesamesam
Copy link
Contributor

Could you rebase all of your PRs to pick up the CI fix? Thanks!

@thesamesam
Copy link
Contributor

@eli-schwartz

@thesamesam
Copy link
Contributor

Also, needs a rebase.

@desultory desultory force-pushed the parallel-fetch branch 2 times, most recently from 3790168 to fe47306 Compare February 4, 2025 23:36
getuto Outdated
@@ -159,14 +159,19 @@ if [[ ! -d ${GNUPGHOME} ]] ; then

# TODO: keys.openpgp.org lacks a UID for our keys, need to verify email
for keyserver in "${mykeyservers[@]}" ; do
gpg ${QUIET_GPG} --batch --keyserver "${keyserver}" --recv-keys ${myrelkeys} || true
einfo "Importing release engineering keys from: ${keyserver}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is adding unconditional status messages. Currently getuto only prints the major action being done (initializing, or updating, the keyring as a whole). I'm of two minds about this change, but either way, it deserves to be a distinct commit with distinct rationale, not "do it in parallel".

getuto Outdated
@@ -159,14 +159,19 @@ if [[ ! -d ${GNUPGHOME} ]] ; then

# TODO: keys.openpgp.org lacks a UID for our keys, need to verify email
for keyserver in "${mykeyservers[@]}" ; do
gpg ${QUIET_GPG} --batch --keyserver "${keyserver}" --recv-keys ${myrelkeys} || true
einfo "Importing release engineering keys from: ${keyserver}"
gpg ${QUIET_GPG} --batch --keyserver "${keyserver}" --recv-keys ${myrelkeys} || true &
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using & means that we inherently discard the exit status -- and wait without any options always returns true, not the exit status of the failed command. So it's really a replacement for || true...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants