FIX: Gap Of Uploading The Same File Key Twice

2026-08-27 18:56:08 +03:00
parent b68086eea4
commit 88c64adf38
8 changed files with 62 additions and 29 deletions
@@ -66,20 +66,8 @@ Both steps of the upload flow, end to end:
  category, and a storage key this API never issued
 - answering 404 for a category id no category has, kept distinct from the 500
  the category lookup itself failing produces
-
-## `@known-gap`
-
-One scenario is tagged `@known-gap`. It passes — it pins down what the service
-does **today**, where that differs from what it is documented to do:
-
- **registering the same upload twice answers 500.** `videos.storage_key` is
-  `UNIQUE`, so the retry the API's own error message invites ("retry this
-  request with the same 'key'") fails the insert — after a second MediaConvert
-  job has already been queued for the same file.
-
-Fixing it means changing the scenario alongside the handler. It is tagged so it
-is easy to find, and so it can be excluded with
-`gobdd.WithIgnoredTags("@known-gap")` if that is ever wanted.
+- answering 409 for a key that was already registered, rather than queueing a
+  second transcoding job for the same file

 ## Adding a scenario