https://bugzilla.wikimedia.org/show_bug.cgi?id=54935
--- Comment #5 from Krinkle <[email protected]> --- Contrary to what one might think, both scenarios do not automatically resolve themselves the next 5-minute window of the startup module. The next time the startup module is generated, 5 minutes later, the max() timestamp of a module will still be the same. Touching startup.js won't help either. You'd have to artificially touch the individual module that got corrupted in cache and sync it and hope the same race condition won't happen again. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
