How do updated logs work?

[Forty-Bot]

The current implementation assumes that logs are immutable, and are complete when first uploaded. However, logs.tf has a feature to update an existing log (which may? be used when e.g. a log is requested in the middle of a round). Since we poll for new logs every 5 minutes, we could be using stale data for some logs.

The proper response depends on the exact nature of how updating works:

• If updated logs just get a new logid and redirect, then the existing deduplication process will catch them just fine.
• If updated logs have their date updated when they are updated (but keep the same logid), then we can convert our inserts to upserts when the date is newer.
• If the logs get silently updated, but the date is not changed, then we have a problem :)

[Forty-Bot]

Ok, so as it turns out it is

If updated logs have their date updated when they are updated (but keep the same logid), then we can convert our inserts to upserts when the date is newer.