Since september if some action creates too long automatic comment (page protection, mass edits reverting...) in ruwiki, this comment not crops, but entirely removes, see https://ru.wikipedia.org/w/index.php?title=Википедия:Именование_статей/Иноязычные_названия&diff=prev&oldid=65843747 (page protection). Perhaps the reason is that the Cyrillic chars occupy 2 bytes in UTF-8 - before that this chars were cut off in the middle and turns into a "question mark in rhombus" symbol, since the beginning of the problems I have not seen this symbol. More examples on https://ru.wikipedia.org/w/index.php?title=Википедия:Форум/Архив/Технический/2014/09#Утеря_описания_правки_при_откате_изменений
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Umherirrender | T85700 Long edit comments get entirely removed instead of truncated (error in cutting multibyte chars?) | |||
Resolved | Umherirrender | T97883 Reject summary for FlaggedRevs gets cut of badly for multibyte chars | |||
Resolved | TTO | T95353 database side truncated comments not shown in history or diff |
Event Timeline
Proof: https://ru.wikipedia.org/w/index.php?title=Участник:Sealle/Специально_созданная_страница_для_проверки_работы_движка_в_описаниях_правок&action=history , in the last revision one digit have been added into comment before Cyrillic chars.
Not sure if this is still Core or already DB territory. Probably the former if MW does not cut properly and garbage ends up in the DB
Change 191971 had a related patch set uploaded (by Umherirrender):
Truncate protect reason on null revision for whole multibyte characters
Change 192001 had a related patch set uploaded (by Umherirrender):
Remove half bytes when showing comments
Change 191971 merged by jenkins-bot:
Truncate null revision comment for whole multibyte characters
With version 1.25wmf22 new long comments for revision will be truncated correctly, but still old comments are not shown.
Uh, 2nd patch still waiting (sorry didn't see that at my previous comment), hence putting Priority to normal.
Change 192001 abandoned by Umherirrender:
Remove half bytes when showing comments
Reason:
Too complicated
The problem with new too long comments is solved. For the existing log reasons I have created a new task T95353 to handle that.
This is a new issue (first was about protection summary, this is about flagged revs). I have created T97883 to track the issue and allow the right project assigned.
This is issue about entire problem, not about protection only (see OP post), why you close it and create duplicate ticket?
The original post includes page protection which was fixed. It is easier to have one task for one issue, because than a devoloper does not have to read the whole task and needs to look which is already fixed.
The feature behind "mass edits reverting" was unknown to me, why I have read over it, but it seems it is the reject feature of flagged revs, where I created an own task for the correct project.
Thats already tracked as T97883, see https://ru.wikipedia.org/w/api.php?action=query&prop=revisions&revids=82746538&format=xml for the reason, which is a FlaggedRevs summary text (message revreview-reject-summary-cur)