On beta.wmflabs.org it is currently not possible to edit a Lua module page. Both &action=edit and &action=submit fail, but content model wikitext works as usual.
This should not be deployed.
It is resulting in a page sectioneditnotsupported-title with sectioneditnotsupported-text content.
Needless to mention that no section= in URL.
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/core | master | +69 -69 | Revert "Pedantic strict equals." |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Release | zeljkofilipin | T191059 1.32.0-wmf.13 deployment blockers | ||
| Resolved | daniel | T199504 Editing of content model other than wikitext fails |
Preventively adding MCR (please remove if that doesn't apply) in case there is some ongoing experiment on beta- apologies if my guess is wrong.
Update more than six hours later:
I don't think this is caused by MCR, but until we are sure, I moved it to the storage layer workboard.
Change 445658 had a related patch set uploaded (by Daniel Kinzler; owner: Daniel Kinzler):
[mediawiki/core@master] Revert "Pedantic strict equals."
Unrelated to MCR.
Caused by https://gerrit.wikimedia.org/r/c/mediawiki/core/+/443964, I made a revert, see https://gerrit.wikimedia.org/r/c/mediawiki/core/+/445658.
Change 445658 merged by jenkins-bot:
[mediawiki/core@master] Revert "Pedantic strict equals."
Not reopening, but I was asked to provide more explanation about what happened.
As part of my work on T58849, in which I'm trying to deprecate the dangerous "edittime" conflict detection parameter, I cleaned up some low-hanging fruit in EditPage.php. Specifically, in the patch https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/443964/ I replaced some loose equality == with strict equality ===.
The fact that this change caused a production outage suggests two things, that we should write unit tests to cover the use case, and that strict equality changed behavior because we're using false where some code expects an empty string. Once the unit test is written, we can find the offending code, include better documentation for hook or function parameters, then reintroduce strict equality to catch other integration mistakes in the future.