Michael Kaufman

For our deployment we have curl commands setting up our collector groups which work alright but it becomes a real pain when new devices are added, as we have to...

I built this locally and it did now successfully return the future-dated (rounded up to the next whole second) object in our environment.

Seeing the same lack of strong consistency with script below, in the latest beta v2.1.0-beta.1-3e08061, v2.0.0, and v1.4.0-d7a0dda: ``` #!/bin/bash echo "### COPY" s5cmd --log debug --json --stat cp s3://bucket1/my.parquet...

So this seems tied to S3 having a fast clock. i.e. We did a copy at 16:27:27, failed a read at 16:27:28, and then succeeded a read at 16:27:33 showing...