← Back to team overview

hockeypuck-dev team mailing list archive

import key counts coming up short?

 

Casey (and future subscribers!),

I think hockeypuck-import could have some state machine/logic errors
in io.go.  Importing a keyring with a single key, my 0xd39da0e3,
never added a row to the openpgp_pubkey table!

I also instrumented hockeypuck-import to give me some simple stats
(every 100 keys, and when done with each file):

  hockeypuck-import2013/09/15 10:40:47 main.go:137: Loaded 14000 keys (with 0 errors) from sks-
+dump-0025.pgp
  hockeypuck-import2013/09/15 10:40:49 main.go:137: Loaded 14100 keys (with 0 errors) from sks-
+dump-0025.pgp
  hockeypuck-import2013/09/15 10:40:50 main.go:140: Loaded 14157 keys (with 0 errors) from sks-
+dump-0025.pgp

and I'm concerned that it doesn't report all 15,000 keys each time,
usually "counting" 800+ keys less.

"SELECT COUNT (*) FROM openpgp_pubkey;" - when less keydumps were loaded -
wasn't helpful because there were always somewhat _more_ than n * 15,000
keys being reported.  (I didn't look for duplicate uuids or compare the
uuids against the short/long keyids in each keydump file, however.)

What do you think?

In other news, I'm loading ~100 keys/second on an old laptop (FreeBSD 9.1).

-- 
Jason Harris           |  PGP:  This _is_ PGP-signed, isn't it?
jharris@xxxxxxxxxxxxx _|_ Got photons? (TM), (C) 2004

Attachment: pgpQJOKLltPPy.pgp
Description: PGP signature


Follow ups