temporary write-ahead log after restore

[gugray]

I have a DB that is being replicated into an S3 bucket.
I restore the DB at a different location using the following command:

litestream restore -o beepdb.db s3://buck.localhost:3100/beepb.db.repl

I get three files as a result:

beepdb.db
beepdb.db.tmp-shm
beepdb.db.tmp-wal

Why are the write-ahead logs tmp-shm and tmp-wal, and not -shm and -wal? SQLite ignores these files, and my quick test shows that the single .db file contains the data's most up-to-date version without any write-ahead log. Why are the tmp- files there?

[hifi]

That was fixed in #529 but there's no release yet with the fix.

[gugray]

Perfect, thank you! I wonder why I didn't find that issue (I did search). This both explains it, and is reassuring.
Thanks for the work on Litestream!