Page MenuHomePhabricator

module changes sometimes do not invalidate cache
Open, Needs TriagePublicBUG REPORT

Description

It seems to me that certain changes on transcluded modules do not trigger cache invalidation properly on the stuff these modules are transcluded in.

See https://commons.wikimedia.org/wiki/Special:WantedCategories with a list of non existing categories following scheme 'Files with coordinates missing SDC location of creation (g° N, g°E)‏‎'. These cats contain altogether 1390000 Files that are not categorized correctly. The miscategorization was caused by changes in Module:Coordinates (see https://commons.wikimedia.org/w/index.php?title=Module:Coordinates&action=history) in May 2024, the first change it seems did trigger recategorization, while consecutive changes didn't. I would expect that the cache invalidation runs through these some million files in some days at most.

Proper categorization is done via Template:Location and Module:Coordinates, but is not reflected in the content of those categories. Touching files will solve the problem, but is quite tedious.

Something seems to be blocked.

Two requests:

  1. Can somebody invalidate cache directly on the database (for the files in the above mentioned categories)
  2. Fix the problem in the core software so that it works properly for future changes.

Event Timeline

I'm pretty sure we have a very old task for this one, maybe even from Bugzilla times. I'll do a bit of touching to empty out that list of junk.

FWIW, given the size and amount of writes in commons. It usually takes a very long time, sometimes months for the changes to propagate to all pages that use a template/module. It's normal since your wiki has 100M pages.

FWIW, given the size and amount of writes in commons. It usually takes a very long time, sometimes months for the changes to propagate to all pages that use a template/module. It's normal since your wiki has 100M pages.

can somebody check the queue? Whether these propagations are still in the queue?

Due to the nature of how it works, it's not really feasible to check them. If you have specific case you need it to get the change, just purge it (action=purge).