Topic on Extension talk:CirrusSearch

Converted database collision to Latin1_bin

MediaWiki   1.31.7
PHP 7.3.17 (apache2handler)
MySQL   8.0.18
Elasticsearch   5.6.16

I updated from mediawiki 1.31.1 to mediawiki 1.31.7 and now I'm seeing this error with elastic search. I added to ParserOutput.php to display the page name, however I can't find the page with "GTS" or "Standard Kanban Board in Leankit", that makes sense. I also searched for https://server/api.php?action=query&prop=info&pageids=5716 and did not see anything like what is displayed.

[ mykaidevdb] Indexed 10 pages ending at 5716 at 13/second [166e71ff89c6a092549ca318] [no req] MWException from line 310 of D:\Bitnami\wampstack\apps\mediawiki\includes\parser\ParserOutput.php: Bad parser output text. 5. GTS’ Standard Kanban Board in Leankit Backtrace:

1. 0 [internal function]: ParserOutput->{closure}(array)
2. 1 D:\Bitnami\wampstack\apps\mediawiki\includes\parser\ParserOutput.php(320): preg_replace_callback(string, Closure, string)
3. 2 D:\Bitnami\wampstack\apps\mediawiki\includes\content\WikiTextStructure.php(152): ParserOutput->getText(array)
4. 3 D:\Bitnami\wampstack\apps\mediawiki\includes\content\WikiTextStructure.php(225): WikiTextStructure->extractWikitextParts()
5. 4 D:\Bitnami\wampstack\apps\mediawiki\includes\content\WikitextContentHandler.php(150): WikiTextStructure->getOpeningText()
6. 5 D:\Bitnami\wampstack\apps\mediawiki\extensions\CirrusSearch\includes\Updater.php(366): WikitextContentHandler->getDataForSearchIndex(WikiPage, ParserOutput, CirrusSearch)
7. 6 D:\Bitnami\wampstack\apps\mediawiki\extensions\CirrusSearch\includes\Updater.php(204): CirrusSearch\Updater->buildDocumentsForPages(array, integer)
8. 7 D:\Bitnami\wampstack\apps\mediawiki\extensions\CirrusSearch\maintenance\forceSearchIndex.php(218): CirrusSearch\Updater->updatePages(array, integer)
9. 8 D:\Bitnami\wampstack\apps\mediawiki\maintenance\doMaintenance.php(94): CirrusSearch\ForceSearchIndex->execute()
10. 9 D:\Bitnami\wampstack\apps\mediawiki\extensions\CirrusSearch\maintenance\forceSearchIndex.php(679): require_once(string)
11. 10 {main}

Figured out the issue! I was using utf8 for the database and converted it to latin_bin and everything started working.