Restic with wasabi repository - Issues after init and first backup

[gm1]

@cdhowie

Given that

@gm1

I see that there is only one version of the lock and it was created at the time of initializing my last repo.

I wonder if you could expand on your advice given that there is only one version of the lock:

@cdhowie

For me, the fix was to go into the S3 console, enable showing versions, and delete all versions of that lock.

Should I try to delete it and see if that helps or should I be only do that if there were old versions?
And if I delete it, should I delete the file or file + directory?

I just found something interesting about the locks. It is the only file in the repository that when I toggle between enable showing versions and not enabling showing versions, there is a change in the way the file is presented.

When showing versions is not enabled:

When showing versions is enabled:

It is the only file where there is one version of a file that shows this behavior. All other files/directories where there is only one version only show a picture like the first picture even when toggling between enabling and not enabling showing versions. I do not know if this is completely relevant but wanted to add the information.

Thank you.