Julian Sommer 6d315de58e fix: make DeleteVolume idempotent when a concurrent sweep already removed an object ...

deleteS3Prefix returned on any DeleteObject error, so two overlapping deletes
for one volume left the loser reporting ServerInternal once the winner had
removed a chunk between the list and the delete. DeleteDBInstance surfaced that
as HTTP 500.

S3ObjectStore.DeleteObject now reports a missing key as NoSuchKeyError, matching
GetObject and HeadObject, and the sweep treats an already-deleted object as
done. S3 answers 204 here but Predastore answers 404, and both mean the same
thing to a delete sweep.

2026-08-12 13:37:51 +10:00

..

deleteobject_test.go

fix: make DeleteVolume idempotent when a concurrent sweep already removed an object

2026-08-12 13:37:51 +10:00

ensurebucket_test.go

feat(otel): full-stack telemetry — tracing, metrics, logs + per-VM guest metrics (#479)

2026-07-09 09:43:32 +10:00

objectstore_test.go

chore: enable testifylint

2026-07-16 09:36:22 +10:00

objectstore.go

fix: make DeleteVolume idempotent when a concurrent sweep already removed an object

2026-08-12 13:37:51 +10:00