-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Just a quick note -- we encountered an interesting bit of cache pollution today, where an article on de.wikipedia.org was reported as having bogus article links URLs in the form used by the DumpHTML static dumps.
This was unexpected, as DumpHTML disables $wgEnableParserCache while it's working; it thus shouldn't save anything to the parser cache.
This may have been caused by some overaggressive parser-cache work in FlaggedRevisions, which Aaron has fixed by adding a $wgEnableParserCache check to FlaggedRevs::updatePageCache().
It's possible some bad pages remain in cache; they can be flushed with an ?action=purge or null edit.
(If it's safe to do an epoch update or something to force them all out, we could try to do that just in case, but we've had only one report of a bad entry so far.)
- -- brion
Brion Vibber wrote:
(If it's safe to do an epoch update or something to force them all out, we could try to do that just in case, but we've had only one report of a bad entry so far.)
And another parser cache regression too -- r36093 changed how pages were saved into the parser cache on edit, but in a way which didn't properly take all settings into account. At least the stub threshold setting was being taken from the active user session, while the result was saved with a hash key for default settings -- and thus served back to visitors.
Fixed in r36185; but again there may be bad cache entries floating around.
-- brion
wikitech-l@lists.wikimedia.org