ParamInfo for view-topic-history and view-post-history are causing HTTP status 503.
This breaks Pywikibot 100% since it loads paraminfo for all modules during startup, and a 503 kills the startup sequence.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix api-flow-topic-history and api-flow-post-history | mediawiki/extensions/Flow | master | +2 -0 |
Related Objects
Related Objects
- Mentioned In
- rMEXT2c89859fc6da: Updated mediawiki/extensions Project: mediawiki/extensions/Flow…
rEFLW382c0376a732: Fix api-flow-topic-history and api-flow-post-history
T108322: prevent modules with broken paraminfo being deployed to production wikis - Mentioned Here
- T100779: pywikibot api paraminfo should to recover from defective API modules
Event Timeline
Comment Actions
If this happens often we might really need something for T100779: pywikibot api paraminfo should to recover from defective API modules.
Comment Actions
Change 230098 had a related patch set uploaded (by Sbisson):
Fix api-flow-topic-history
Comment Actions
Change 230098 merged by jenkins-bot:
Fix api-flow-topic-history and api-flow-post-history
Comment Actions
hmm. the two paraminfo queries are now returning valid JSON, so it appears this bug fix has been deployed to beta wiki.
Is @Forrestbot indicating that this bug fix will be part of the production deploy on the 11th August?
Comment Actions
Checked on betalabs - no 503 status requests were observed for history actions(view-topic-history and view-post-history).