Bug 1063112
| Summary: | Client push in dryRun mode should not invoke CopyTrans | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Zanata | Reporter: | Sean Flanigan <sflaniga> | ||||
| Component: | Component-Maven, Component-zanata-client | Assignee: | Sean Flanigan <sflaniga> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Zanata-QA Mailling List <zanata-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | djansen, zanata-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 3.3.0-SNAPSHOT (20140218-0947) | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-03-20 05:47:28 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: | |||||||
| Attachments: |
|
||||||
https://github.com/zanata/zanata-client/pull/12 Also backported to client 3.2.1-SNAPSHOT as https://github.com/zanata/zanata-client/commit/76a3972f9ce89bcf91626105820f4e123de7c272 Verified at 1bf60cc19d6941929f586c3e8d62390fbb41644d Closing VERIFIED bugs for Zanata server 3.3.2. |
Created attachment 861225 [details] Screenshot showing CopyTrans invoked in dry run mode Description of problem: When copyTrans was split out into a separate REST call, we failed to disable copyTrans when the dryRun option is set. Dry run should skip all mutation operations (local or remote), so copyTrans should be skipped. Version-Release number of selected component (if applicable): Probably 3.2, but we should check when the REST call was first split out. How reproducible: 100% Steps to Reproduce: 1. push source documents, using the dryRun option 2. observe log messages Actual results: "Running Copy Trans for..." Expected results: "Skipping Copy Trans for..." (or similar) Additional info: