Bug 996939
Summary: | Clearing a TM while an import is in progress can fail (almost) silently. | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Damian Jansen <djansen> |
Component: | Component-UI | Assignee: | Sean Flanigan <sflaniga> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Zanata-QA Mailling List <zanata-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.0 | CC: | camunoz, sflaniga, zanata-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-27 03:31:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Damian Jansen
2013-08-14 10:22:19 UTC
I suggest we simply disable all activity (Delete, Clear or Upload) on a TM when there is an import or clearing going on. I'll take this. I'm introducing a pessimistic lock (as we have for copytrans), returning the owner's username if the lock is already taken, and returning a 503 response[1] if a client tries to POST to or DELETE from a locked translation memory. 503 isn't an exact match for semantics, but I think it's pretty close if you interpret "server/service" as "resource". [1] 503 Service Unavailable The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. -Wikipedia Verified at 6cffb1ba3ce14c4c5803c1e40556bd8d58a60363 Closing VERIFIED bugs which predate Zanata 3.1.2. |