Bug 1147364 - [REGRESSION] Editor history not populated on concurrent access
Summary: [REGRESSION] Editor history not populated on concurrent access
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5
Assignee: Patrick Huang
QA Contact: Damian Jansen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-29 06:42 UTC by Damian Jansen
Modified: 2015-01-26 23:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-01-26 23:28:03 UTC
Embargoed:


Attachments (Terms of Use)
Screenshot of error (53.76 KB, image/png)
2014-09-29 06:42 UTC, Damian Jansen
no flags Details

Description Damian Jansen 2014-09-29 06:42:31 UTC
Created attachment 942180 [details]
Screenshot of error

Description of problem:
If two users encounter a concurrency / conflict issue on translating the same target, the user who needs to resolve the conflict is given an empty dialog.
This disallows them from resolving the conflict and generates errors when they attempt to save/edit the target.

Version-Release number of selected component (if applicable):
3.5.0-SNAPSHOT (git-jenkins-zanata-server-build+verify-nightly-release-1167-296-g18385b6)

How reproducible:
Easy always

Steps to Reproduce:
1. Two users sign in, go to the same project,version,document,target
2. User 1 edits the field, but does not save
3. User 2 edits the field and saves

Actual results:
User 1 is presented with a conflict resolution (history) dialog that is empty. They cannot use this to repair the concurrent change.

Expected results:
A populated dialog with copy etc buttons

Additional info:

Comment 1 Patrick Huang 2014-09-30 00:42:56 UTC
https://github.com/zanata/zanata-server/pull/592

Comment 2 Damian Jansen 2014-10-01 05:40:56 UTC
An issue with the current view is the popup will close on a "click elsewhere" action.  There's an error notification right in front of it that, when clicked, causes this to occur.
https://bugzilla.redhat.com/show_bug.cgi?id=1148259

Comment 3 Damian Jansen 2014-10-01 05:41:51 UTC
Verified on 3.5.0-SNAPSHOT (git-jenkins-zanata-server-build+verify-nightly-release-1167-299-ga85e7f8)


Note You need to log in before you can comment on or make changes to this bug.