Is -timestamp broken when restoring?

[xrd]

Is this a bug or am I misunderstanding the -timestamp switch?

I have a database stored on s3 (actually minio, but it works).

Restore works and I see items in the database on 1-29-2024 and 1-31-2024.

But, when I re-run the restore command adding the -timestamp 2024-01-30T18:00:00Z switch, litestream complains with no matching backups found.

(Also, just an aside, but if I look at the files stored inside s3 (minio), I only see a 10MB file and then a 119 byte WAL file. I'm wondering if I am not looking at all the files, because how can that expand to 369MB when the db file is restored?)

chrisdawson@nixos:~/litestream-tmp$ cat event.yml 
dbs:
  - path: blah.db
    replicas:
      - url: s3://xxx/xxx
        endpoint: https://examplecom
        access-key-id: xxx
        secret-access-key: xxx

chrisdawson@nixos:~/litestream-tmp$ ./litestream restore -config event.yml ./blah.db
time=2024-02-01T12:28:58.343-05:00 level=INFO msg="restoring snapshot" db=/home/chrisdawson/litestream-tmp/blah.db replica=s3 generation=b5f5868887f877ae index=1594 path=/home/chrisdawson/litestream-tmp/blah.db.tmp
time=2024-02-01T12:29:00.183-05:00 level=INFO msg="restoring wal files" db=/home/chrisdawson/litestream-tmp/blah.db replica=s3 generation=b5f5868887f877ae index_min=1594 index_max=1594
time=2024-02-01T12:29:00.266-05:00 level=INFO msg="downloaded wal" db=/home/chrisdawson/litestream-tmp/blah.db replica=s3 generation=b5f5868887f877ae index=1594 elapsed=83.115207ms
time=2024-02-01T12:29:00.278-05:00 level=INFO msg="applied wal" db=/home/chrisdawson/litestream-tmp/blah.db replica=s3 generation=b5f5868887f877ae index=1594 elapsed=11.732843ms
time=2024-02-01T12:29:00.278-05:00 level=INFO msg="renaming database from temporary location" db=/home/chrisdawson/litestream-tmp/blah.db replica=s3
chrisdawson@nixos:~/litestream-tmp$ ls -lah blah.db 
-rw------- 1 chrisdawson users 369M Feb  1 12:29 blah.db
chrisdawson@nixos:~/litestream-tmp$ rlwrap sqlite3 ./blah.db 'select created from logs order by created desc limit 1'
2024-01-31 16:25:36.484Z
chrisdawson@nixos:~/litestream-tmp$ rlwrap sqlite3 ./blah.db 'select created from logs order by created asc limit 1'
2024-01-29 00:11:06.279Z
chrisdawson@nixos:~/litestream-tmp$ mv blah.db old.db
chrisdawson@nixos:~/litestream-tmp$ ./litestream restore -timestamp 2024-01-30T18:00:00Z -config event.yml ./blah.db
time=2024-02-01T12:29:44.983-05:00 level=ERROR msg="failed to run" error="no matching backups found"

[xrd]

I created an issue (#564) for this and believe this was probably a configuration issue with litestream.