Page MenuHomePhabricator

Was able to save without edit conflict, but diff shows there should have been one.
Closed, ResolvedPublic

Description

Author: dzonatas

Description:
One of my edits was questioned, and I found that the system didn't give me an edit conflict notice when it should. I searched bugzilla and found this may be related to BUG-1150 with the comment about replication lag.

See the noted history URL: http://en.wikiversity.org/w/index.php?title=Wikiversity:Candidates_for_Custodianship&offset=2008091222&limit=5&action=history

The middle three edits are what reveals the error. When I made the one at 21:19, the software didn't recognize an 'edit conflict' with the edit by Salmon of Doubt at 21:12.

It was pointed out to me with this diff: http://en.wikiversity.org/w/index.php?title=Wikiversity:Candidates_for_Custodianship&curid=2038&diff=325819&oldid=325817

Which made it questionable as if I edited someone else's comments. If I was careless, it would have defaulted to undo my edits.

The changes I made are revealed in this diff: http://en.wikiversity.org/w/index.php?title=Wikiversity%3ACandidates_for_Custodianship&diff=325819&oldid=325812

As you see, the comments that got changed are outside the range of the last diff.

I'm not sure how to reproduce this one, but there have been reports of database errors showing up: http://en.wikiversity.org/w/index.php?title=Wikiversity:Colloquium&oldid=325963#Database_error


Version: unspecified
Severity: normal
URL: http://en.wikiversity.org/w/index.php?title=Wikiversity:Candidates_for_Custodianship&offset=2008091222&limit=5&action=history

Details

Reference
bz15593

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:20 PM
bzimport set Reference to bz15593.
bzimport added a subscriber: Unknown Object (MLST).

ayg wrote:

I'm going to guess this was fixed by Tim in r41244. If this keeps happening, reopen.