This was discovered while working on getting the RevisionSlider extension selenium tests on Catalyst. RevisionSlider has a test that passes every time on retry, but fails on the initial run each time. This is because the tag is not correctly applied the first time it's used on a new wiki. On retries, the tag isn't new any more, so it works.
Steps to replicate the issue (include links if applicable):
- Create a new Catalyst env (for example the mediawiki chart with Vector, like the catalyst-daily jobs) and log in as admin
- Test A, the wiki's first blanking:
- a. Open Test_A?action=edit, type one, and save.
- b. Edit it again, change the text to two, and save.
- c. Edit it again, delete all the text, and save. The page is now blank.
- Test B, the second blanking, do the same three edits on Test_B?action=edit.
What happens?:
The first edit using each tag is saved, but without adding its tag
Also, Special:RecentChanges does not show the blanking of the first page
What should have happened instead?:
The tag should display the first time, as well as all subsequent times that it should be applied.
Also, the edit should appear in Special:RecentChanges.
Other information (browser name/version, screenshots, etc.):
| gif of test | Test A, no blanking tag | Test B showing the blanking tag | First blanking not showing in Special:RecentChanges |
Likely cause:
envdb (MariaDB 11.8.2) has innodb_snapshot_isolation on by default. With it on, MediaWiki loses the tag and the Recent changes entry for the first edit that uses each tag. The edit itself is saved. This is why RevisionSlider's daily test fails on its first try. Link to mariaDB doc that shows defaults
Production (MariaDB 10.11.16) and Jenkins (search log for 10.11.18-MariaDB) run older versions where it is off by default, so they don't hit this.
To confirm on catalyst: run SELECT @@global.innodb_snapshot_isolation; on envdb (1 = on).
Potential fix, if the above is confirmed to be true: add innodb_snapshot_isolation=OFF to myCnf in catalyst-api helm/env-db/values.yaml.



