https://bugzilla.wikimedia.org/show_bug.cgi?id=34706
Roan Kattouw <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Roan Kattouw <[email protected]> 2012-02-26 00:16:24 UTC --- The core error is 'mw.loader.addSource is not defined', and that was quite clearly caused by the 1.18 version of mw.loader being served from cache. For some reason the cache for mediawiki.js wasn't invalidated on enwikisource, I don't know exactly why, or why this didn't happen to the other wikis that we deployed 1.19 to. My best guess is that not all servers switched enwikisource to 1.19 at the exact same time, so that the following sequence of events could happen: 1) client requests startup module for enwikisource 2) server running 1.19 serves response, Varnish caches it 3) client requests mediawiki module with the updated timestamp in the URL 4) server running 1.18 serves response, Varnish caches it 5) a little while later, all servers run 1.19 for enwikisource, but Varnish is still caching 1.18 versions of modules with 1.19 URLs I ran purge-varnish en.wikisource.org , which purges all URLs with 'en.wikisource.org' anywhere in them from Varnish (in practice that's all http://bits.wikimedia.org/en.wikisource.org/load.php URLs). After doing that, a hard refresh fixed the issue for me. I guess we should probably do a Varnish purge for a wiki every time we deploy a completely new version of MediaWiki to it, to prevent this kind of bug from happening. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- 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
