Page MenuHomePhabricator

Investigation: Check core's conflict detection for changes possibly causing more conflicts
Open, Needs TriagePublic

Description

We keep getting reports where users claim they would run into more edit conflicts recently. These reports are not about "conflicts with myself" (see T222805 as well as T72163 for that). More than one user said the conflict was with an edit that was made hours before.

Collection of possibly related user reports (please expand):

To do:

  • Check tickets in T72163 and MediaWiki-Page-editing (there is an "Edit conflict" column) for closed or in-progress tickets that might be related to conflict detection.
  • Check the Git logs for the relevant code. Are there recent changes that could be related?
  • Check the conflict audit logs for any clues.

Event Timeline

@daniel I vaguely remember something popping up about changes to the edit conflict detection lately in combination with you - can you confirm / deny? :-)

I remember some talk about removing the "suppress edit conflict with self" logic but I see it's still there.

Other changes of interest, probably not at fault:

@daniel I vaguely remember something popping up about changes to the edit conflict detection lately in combination with you - can you confirm / deny? :-)

See discussion on T175745: Do not overwrite edits when conflicting with self. There seems to be rough consensus among tech folks that this should go away, but there's nobody driving this from the product side. OTOH, this can be fixed by simply deleting 100 lines of code in two files or so, maybe someone (tm) can JFDI...

Thanks for the note @daniel. Unfortunately it's not in the scope of this project to work on the conflict detection algorithm, so we'll have to pass on that as well.

TechWish team, please note that making the following change is explicitly not in scope for the work on TwoColConflict.

See discussion on T175745: Do not overwrite edits when conflicting with self. There seems to be rough consensus among tech folks that this should go away, but there's nobody driving this from the product side. OTOH, this can be fixed by simply deleting 100 lines of code in two files or so, maybe someone (tm) can JFDI...

If changes like this have happened or will happen, they are interesting to note here though since it would result in more conflicts occurring.