Debugging a problem with S3 (presigned URLS) that looks like we're outrunning eventual consistency. Reminded of the time a decade ago that we got faster desktops and tests started breaking because MSSQL would round timestamp fields to the nearest 1/200th of second, where the nearest might be in the future. Before the faster desktops, we never noticed.