sub-second time strings dropping leading zeros

As Jacob Lange reports on the CBC list, the event time in the event.log on Gracedb is wrong for 170818/G298171. The event time should be 1187058327.0815086 but the event.log says 1187058327.815086. It looks like the leading zero of the sub-second string is being dropped somewhere.

I've checked into this and the issue is arising from here: https://git.ligo.org/lscsoft/gracedb/blob/eb7a358e21e250b150fb760c395bfee342f6e8dc/gracedb/events/translator.py#L106

mentioned in commit 3adf8911

I submitted an event after implementing this patch on gracedb-test and all appears good. I will add this patch to the server code update which is going to be deployed in production tomorrow.

closed

mentioned in issue #11 (closed)

I went back and edited the event.log file for all affected events. There were several that were OK because they were test events with the nanoseconds portion just set to 0. Also, many events with IDs less than ~120000 had a different format for the event.log file, and it looks as though nanoseconds were handled properly in that format.