Page MenuHomePhabricator

MediaWiki\Linter\MissingCategoryException: Cannot find id for 'night-mode-unaware-background-color'
Closed, ResolvedPublicPRODUCTION ERROR


[{reqId}] {exception_url}   MediaWiki\Linter\MissingCategoryException: Cannot find id for 'night-mode-unaware-background-color'
from /srv/mediawiki/php-1.42.0-wmf.22/extensions/Linter/includes/CategoryManager.php(223)
#0 /srv/mediawiki/php-1.42.0-wmf.22/extensions/Linter/includes/Database.php(182): MediaWiki\Linter\CategoryManager->getCategoryId(string, NULL)
#1 [internal function]: MediaWiki\Linter\Database->buildErrorRow(MediaWiki\Linter\LintError)
#2 /srv/mediawiki/php-1.42.0-wmf.22/extensions/Linter/includes/Database.php(289): array_map(array, array)
#3 /srv/mediawiki/php-1.42.0-wmf.22/extensions/Linter/includes/RecordLintJob.php(60): MediaWiki\Linter\Database->setForPage(array)
#4 /srv/mediawiki/php-1.42.0-wmf.22/extensions/EventBus/includes/JobExecutor.php(80): MediaWiki\Linter\RecordLintJob->run()
#5 /srv/mediawiki/rpc/RunSingleJob.php(60): MediaWiki\Extension\EventBus\JobExecutor->execute(array)
#6 {main}

Thousands of hits for this error when promoting the 1.42.0-wmf.23 train to group1 today.

I'm rolling back the train.


Event Timeline

dancy triaged this task as Unbreak Now! priority.Mar 20 2024, 6:44 PM
dancy created this task.
dancy removed Release Version.

Note that though I rolled 1.42.0-wmf.23 to group1, the errors are being reported against .22

And rolling back the train did not fix the problem. :-(

And rolling back the train did not fix the problem. :-(

Correction. The error rate did drop off eventually after the rollback process reached more servers.

Kim is on PTO this week, but our team is looking at this now! Apologies for the disruption

Change 1012780 had a related patch set uploaded (by Jdrewniak; author: Jdrewniak):

[mediawiki/extensions/Linter@master] Revert "Add inline background color"

This might be a transient; I don't think reverting the Linter extension patch is the solution, I think you need to turn off the lint error in Parsoid. Parsoid is reporting the lint to Linter, and Linter (transiently?) doesn't recognize the category name being given.

Rather than revert that patch, it could be backported to .22

Change 1012780 merged by jenkins-bot:

[mediawiki/extensions/Linter@master] Revert "Add inline background color"

I think both Scott and Arlo are right ... we just need to confirm that the names in Parsoid and linter are the same and there is no typo in the names that we overlooked.

Change 1012781 had a related patch set uploaded (by Zabe; author: Kimberly Sarabia):

[mediawiki/extensions/Linter@wmf/1.42.0-wmf.22] Add inline background color

On group 0 ( shows lint errors which means this is working right .. and so the errors may have been transient. @Arlolra's suggestion is right.

Parsoid servers get 700 reqs / sec ... so, even if a fraction of those have these new lint error, and if there is a delay in how code is updated / services restarted, you would get these errors. So, backporting to wmf.22 should avoid this.

We've agreed to backport to .22 - thank you so much everybody for all of your help!

Change 1012781 merged by jenkins-bot:

[mediawiki/extensions/Linter@wmf/1.42.0-wmf.22] Add inline background color

Mentioned in SAL (#wikimedia-operations) [2024-03-20T20:20:01Z] <catrope@deploy2002> Started scap: Backport for [[gerrit:1012781|Add inline background color (T359205 T360565)]]

Mentioned in SAL (#wikimedia-operations) [2024-03-20T20:45:34Z] <catrope@deploy2002> catrope and zabe: Backport for [[gerrit:1012781|Add inline background color (T359205 T360565)]] synced to the testservers (

Backport complete and looks good, so this ought to unblock the train.

Mentioned in SAL (#wikimedia-operations) [2024-03-20T21:02:59Z] <catrope@deploy2002> Finished scap: Backport for [[gerrit:1012781|Add inline background color (T359205 T360565)]] (duration: 42m 57s)

dancy lowered the priority of this task from Unbreak Now! to Medium.Mar 20 2024, 9:50 PM
cscott claimed this task.
cscott added a project: Essential-Work.

Given that the group1 train rolled forward without further errors of this sort, I'm going to say this is closed.