Continuing from T315383, where we fixed a much more common error similar to this one.
https://logstash.wikimedia.org/goto/70928236a46a29b25aaf344e9b8b25a6
• matmarex | |
Aug 19 2022, 5:11 PM |
F35601968: logstash.wikimedia.org_app_discover.png | |
Oct 20 2022, 2:19 AM |
F35479749: image.png | |
Aug 19 2022, 5:11 PM |
Continuing from T315383, where we fixed a much more common error similar to this one.
https://logstash.wikimedia.org/goto/70928236a46a29b25aaf344e9b8b25a6
In addition to private wikis, this error also occurs on Commons. for a different reason – we get a 403 for some huge pages with lots of images, such as https://commons.wikimedia.org/wiki/Commons:WikiProject_Aviation/recent_uploads/2014_April_1 (there are hundreds of daily pages like this one). I was able to reproduce that when trying to open them in VE as well, where the RESTBase response sometimes is a 403 and has an error like this:
{"type":"https://mediawiki.org/wiki/HyperSwitch/errors/bad_request#rerenders_disabled","method":"get","detail":"Rerenders for this article are blacklisted in the config.","uri":"/commons.wikimedia.org/v1/page/html/Commons%3AWikiProject_Aviation%2Frecent_uploads%2F2014_February_16"}
@ppelberg With the task on your team's tracking board - has this been passed on or escalated to a different team to investigate further?
In rEVEDf2df5dc7b98a: Improve error messages for RESTBase errors I added more details to these errors, and we can distinguish these easily now in the logs, so I filed separate task T316914 about these.
I raised it at https://wikimedia.slack.com/archives/C038KHX5YN6/p1661444483203539 (after the triage meeting where we moved this to tracking), and received a collective shrug.
I'll try to use ParsoidOutputAccess on those wikis instead. Whatever caching issues it has, our private wikis get so little traffic, it'll probably be fine.
Change 829254 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
[mediawiki/extensions/DiscussionTools@master] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
Change 829254 merged by jenkins-bot:
[mediawiki/extensions/DiscussionTools@master] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
Change 843549 had a related patch set uploaded (by Bartosz Dziewoński; author: Bartosz Dziewoński):
[mediawiki/extensions/DiscussionTools@wmf/1.40.0-wmf.5] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
Change 843549 merged by jenkins-bot:
[mediawiki/extensions/DiscussionTools@wmf/1.40.0-wmf.5] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
Change 885310 had a related patch set uploaded (by Paladox; author: Bartosz Dziewoński):
[mediawiki/extensions/DiscussionTools@REL1_39] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
This is happening on 1.39 as well. I'm not sure which changes need to be backported as https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/829254 doesn't cleanly apply to the REL1_39 branch.
It might not be feasible to backport this. The change above depends on some changes in MediaWiki core and in VisualEditor (and maybe in Parsoid) that were being developed around the same time, but we didn't carefully keep track of what depends on what. It would probably be a fair bit of work to track down all of the changes and then test them. I don't think we have the time to help with that, sorry :(
Change 885310 abandoned by Paladox:
[mediawiki/extensions/DiscussionTools@REL1_39] Use ParsoidOutputAccess when RESTBase is not set up (WMF private wikis)
Reason: