Now that REVISIONTIMESTAMP uses a different flag in master, the only thing left to cause vary-revision is self-transclusion (core or via Lua). Once that change goes out, any remaining use should be investigated if it is still problematic. It might be useful to add a vary-revision-hash option to handle race conditions where a page gets auto-merged and thus the self-transclusion is different than the text proposed in the save operation. Normally, I don't see why a reparse would be needed.
Description
Description
Details
Details
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 519574 had a related patch set uploaded (by Aaron Schulz; owner: Aaron Schulz):
[mediawiki/extensions/Scribunto@master] Add debug logging to getContentInternal() for vary-revision flag
Comment Actions
Change 519574 had a related patch set uploaded (by Aaron Schulz; owner: Aaron Schulz):
[mediawiki/extensions/Scribunto@master] Use "vary-revision-sha1" over "vary-revision" in getContentInternal()
Comment Actions
Change 519574 merged by jenkins-bot:
[mediawiki/extensions/Scribunto@master] Use "vary-revision-sha1" over "vary-revision" in getContentInternal()
Comment Actions
The remaining vary-revision instances are basic self-transclusions (https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/526157/ should handle those).