Page MenuHomePhabricator

Edit conflict after deletion should not show a diff between contents and "missingarticle" message
Open, LowPublic

Description

I created the article and opened an edit window in which i added text while editing the page. Finally i deleted it and sent that edit, which thus had the edit parameters referring to the oldest version:
wpStartTime: 20070713204135
wpEditTime: 20070713204110
wpScrollTop: 106272

However, insted of confirmrecreate i got an editconflict with the MediaWiki:Missingarticle content!

Didn't the slave still know it was deleted? Has Missingarticle higher priority over confirmrecreate? Whatever, the behaviour is inconsistent.

PD: Going back and resending got it right, but with the resend delay and likely being different server & slave, not too significant.


Version: unspecified
Severity: minor
URL: http://es.wikipedia.org/wiki/Wikiproyecto:Wikificar/Por_fecha
See Also:
T44163: edit conflict sometimes does not show the current text - new text not loaded from master?
T25044: Edit conflicts when a page is moved with suppressredirect result in silent recreation of the page

Details

Reference
bz10573

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 9:50 PM
bzimport set Reference to bz10573.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #0)

I created the article and opened an edit window in which i added text while
editing the page. Finally i deleted it and sent that edit, which thus had the
edit parameters referring to the oldest version:
wpStartTime: 20070713204135
wpEditTime: 20070713204110
wpScrollTop: 106272

However, insted of confirmrecreate i got an editconflict with the
MediaWiki:Missingarticle content!

I don't understand the dynamics of the incident here.

Didn't the slave still know it was deleted? Has Missingarticle higher
priority
over confirmrecreate? Whatever, the behaviour is inconsistent.

PD: Going back and resending got it right, but with the resend delay and
likely
being different server & slave, not too significant.

This would make it look a bit like bug 42163.