WARNING No key matching fingerprint ... found in the GPG keyring.

Having problem with keybase pgp update.

$ keybase pgp update
▶ WARNING No key matching fingerprint 3cb0ebcdd92ee39c6d1ec95f5f65de645f04b983 found in the GPG keyring.

Keybase: https://keybase.io/blueskyjunkie

I've tried to do keybase log send but it fails ERROR API network error: Post https://api-0.core.keybaseapi.com/_/api/1.0/logdump/send.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers).

Previous issues experiencing this are are pretty old, but seem to suggest a bug of some kind:

https://github.com/keybase/client/issues/6612

I can't find it now, but one issue suggest a bug that was resolved several years ago, so I assume I'm experiencing a new bug.

$ keybase --version
keybase version 5.1.1-20191211223501+15bbb94c23

$ gpg --version
gpg (GnuPG) 2.2.4
libgcrypt 1.8.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/russell/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Start by reproducing keybase pgp update with Keybase 5.1.1 and GnuPG 2.2.4, then compare the reported fingerprint with the local GPG keyring. Investigate the related keybase log send timeout and issue 6612; done means the update no longer warns about the missing matching key or the required behavior is documented.