Output of restic version

• restic 0.17.0 compiled with go1.23rc2 on linux/amd64

What backend/service did you use to store the repository?

BackUpscale

Problem description / Steps to reproduce

When running in append-only mode, snapshots can't be deleted. However, restic forget reports that they have been, even though they haven't.

Expected behavior

Shouldn't the last line here say that "0 / 1" files have been deleted?

repository 19897fd5 opened (version 2, compression level auto)
Remove(<snapshot/2eccde165a>) failed: unexpected HTTP response (403): 403 Forbidden
unable to remove snapshot/2eccde165a030dc068e4ec4a092e47da136f0baeb98313925e562f5c095b91fa from the repository
[0:00] 100.00%  0 / 1 files deleted

Actual behavior

Instead, the last line says, "1 / 1 files deleted". So why it saying something was deleted when it wasn't? Earlier in the output it says "Forbidden" and the snapshot is still there. This is a UX hit because users will think that it's actually happening, when it can't be. And then we all start getting more support requests. :)

repository 19897fd5 opened (version 2, compression level auto)
Remove(<snapshot/2eccde165a>) failed: unexpected HTTP response (403): 403 Forbidden
unable to remove snapshot/2eccde165a030dc068e4ec4a092e47da136f0baeb98313925e562f5c095b91fa from the repository
[0:00] 100.00%  1 / 1 files deleted

Do you have any idea what may have caused this?

My guess is that it's reporting that number of things that are supposed to be deleted as per the user request, not the number of things that actually have been deleted after the request has been processed.

Did restic help you today? Did it make you happy in any way?

If it weren't for Restic, I wouldn't be able to work on BackUpScale! So thank you all!!