The new config var wgPageParseReport is empty on preview or section preview. The old new limit report inside the html as hidden comment was also added on preview or section preview.
This was helpful, if you try to get the counts down and just check if your changes help something by pressing preview instead of save the changes.
Change 303309 had a related patch set uploaded (by Aaron Schulz):
Show wgPageParseReport on page previews too
If I understand correctly, Parser profiling data is now a JavaScript variable that can be found within the HTML source of the page. Is there still a way to access this normally from a Page preview without cracking open the source?
(Also, it seems like this change was made too discreetly, as besides myself@Wiktionary I have found at least two other queries as to the whereabouts of Parser profiling data on Wikipedia: 1, 2)
This has been marked for inclusion in Tech News. How would you best explain this in one to three sentences?
Is anything happening with this? The parser profiling box also allowed the mw.log() feature in Lua to output from usage on actual pages via the regular page previewing function. This seems impossible now, making the debugging and development of Scribunto modules much more inconvenient.
I've also been asked about this and had to track down the code changes to reach here. I am very confused about why the human-readable limit report was removed. @aaron Was this actually intentional?
Apparently it was not intentional. Aaron committed one change (299693) which caused the limit report box to be empty, and then another one, referencing this bug (303309) which caused the box to be removed entirely. Neither change mentioned the removal of the limit report in the commit message or release notes. Legoktm, who merged the second change, confirms that he did not realise that the feature was totally broken. Aaron probably neglected to test it with the PerformanceInspector extension disabled (it is disabled in production).
Change 316207 had a related patch set uploaded (by Legoktm):
Re-add human readable parser limit report
thanks for re-adding the human readable parser limit report :)
unfortunately, in the restored version of the report, the scribunto(Lua) limit report is still missing, which are also written as a js variable, eg:
(window.RLQ=window.RLQ||[]).push(function(){mw.config.set( {
"wgPageParseReport": {
(...)
"scribunto":{
"limitreport-timeusage": {
"value": "0.026",
"limit": "10.000"
},
"limitreport-memusage": {
"value": 626231,
"limit": 52428800
},
"limitreport-logs": "'''æsthetic''' (''esthe′tyk'') estetyczny.\n"
},
}
} );});is it possible to restore also the scribunto(Lua) report limits?? - This is very useful info.
Z.
Change 320237 had a related patch set uploaded (by Bartosz Dziewoński):
Allow extensions to use ParserLimitReportPrepare/ParserLimitReportFormat again
Change 320461 had a related patch set uploaded (by Bartosz Dziewoński):
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320237 abandoned by Bartosz Dziewoński:
Allow extensions to use ParserLimitReportPrepare/ParserLimitReportFormat again
Reason:
Reverting in https://gerrit.wikimedia.org/r/320461 instead.
Change 320461 merged by Bartosz Dziewoński:
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320522 had a related patch set uploaded (by Bartosz Dziewoński):
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Change 320522 merged by Bartosz Dziewoński:
Revert "Move NewPP limit report HTML comments to JS variables" and followups
Reverted on master, and backported the revert to MW 1.28. I don't think that this loss of functionality is acceptable, especially caused by a patch aiming to add support for a new beta extension. I've reopened T110763 so that it will be reimplemented properly.
@Suzukaze-c @Njardarlogar @Zdzislaw @Ankry I am not working on a backport to wmf branches, because this is a non-trivial change, so this will be deployed to Wikimedia wikis per the usual schedule next week, 15-17 November 2016. In the meantime, please verify that the limit report behaves as expected again on https://en.wikipedia.beta.wmflabs.org/.
@matmarex I have done some tests on betawiki - the limit report is generated properly (with scribunto limits and logs ) - thank you!
Z.