Error
MediaWiki version: 1.35.0-wmf.10
Unable to load history for sktjhlr236mrc7ph
| Etonkovidova | |
| Dec 11 2019, 12:32 AM |
| F58387927: Screen Shot 2025-02-11 at 3.43.08 PM.png | |
| Feb 11 2025, 11:44 PM |
MediaWiki version: 1.35.0-wmf.10
Unable to load history for sktjhlr236mrc7ph
#0 /srv/mediawiki/php-1.35.0-wmf.10/extensions/Flow/includes/Block/BoardHistory.php(60): Flow\Data\Pager\HistoryPager->doQuery()
#1 /srv/mediawiki/php-1.35.0-wmf.10/extensions/Flow/includes/View.php(234): Flow\Block\BoardHistoryBlock->renderApi(array)
#2 /srv/mediawiki/php-1.35.0-wmf.10/extensions/Flow/includes/View.php(71): Flow\View->buildApiResponse(Flow\WorkflowLoader, array, string, array)
#3 /srv/mediawiki/php-1.35.0-wmf.10/extensions/Flow/includes/Actions/Action.php(112): Flow\View->show(Flow\WorkflowLoader, string)
#4 /srv/mediawiki/php-1.35.0-wmf.10/extensions/Flow/includes/Actions/Action.php(50): Flow\Actions\FlowAction->showForAction(string)
#5 /srv/mediawiki/php-1.35.0-wmf.10/includes/MediaWiki.php(514): Flow\Actions\FlowAction->show()
#6 /srv/mediawiki/php-1.35.0-wmf.10/includes/MediaWiki.php(304): MediaWiki->performAction(Article, Title)
#7 /srv/mediawiki/php-1.35.0-wmf.10/includes/MediaWiki.php(967): MediaWiki->performRequest()
#8 /srv/mediawiki/php-1.35.0-wmf.10/includes/MediaWiki.php(530): MediaWiki->main()
#9 /srv/mediawiki/php-1.35.0-wmf.10/index.php(46): MediaWiki->run()
#10 /srv/mediawiki/w/index.php(3): require(string)
#11 {main}If I recall correctly, some months ago in a different task the root cause of this was investigated and the short to medium term fix was to "catch" the error and report to the user in localised form what the issue is. In this case "Unable to load history" which is a lot more helpful than "Internal error".
Also, as part of that, with the error now acknowledged and reported as localised message to the user, it is no longer causing a fatal error or uncached/risky HTTP 500 response. Instead, it is now a cachedable 200 OK response with a localised message and error.
Still a bug in the feature about something not working, but no longer a prod error. This is a very rare subcategory, I wouldn't worry about distingishing the two per se, but one can tell from there being a message above the red box, and from the network response having HTTP 200 OK instead of 500 Error.
Still an issue in 1.44.0-wmf.16, updated stacktrace:
==== Error ====
* service.version: 1.44.0-wmf.16
* trace.id: `44a26bc1-75f8-4f5a-a6ac-34aff70d5b68`
* [[ https://logstash.wikimedia.org/app/dashboards#/view/AXFV7JE83bOlOASGccsT?_g=(time:(from:'2025-02-10T09:51:29.018Z',to:'2025-02-11T10:16:54.503Z'))&_a=(query:(query_string:(query:'reqId:%2244a26bc1-75f8-4f5a-a6ac-34aff70d5b68%22'))) | Find trace.id in Logstash ]]
```name=labels.normalized_message,lines=10
[{reqId}] {exception_url} Flow\Exception\InvalidDataException: Unable to load history for rl7iby6wgksbpfnoThe error rate is low, ~ 1 per day.
The majority of errors come from mediawiki, but zhwiki and lvwiki show the error too - e.g. ttps://zh.wikipedia.org/w/index.php?action=history&offset=20241227063358&title=User_talk:蟲蟲飛/Flow: