Fork me on GitHub

Wikimedia IRC logs browser - #wikimedia-tech

Filter:
Start date
End date

Displaying 227 items:

2017-09-20 07:38:34 <DaneGeld> Good morning, or possibly sorry for waking you up if it's the middle of the night!
2017-09-20 07:39:16 <DaneGeld> Foundation errors popping up again I'm afraid, backend fetch from simple.wiktionary this time.
2017-09-20 07:39:20 <DaneGeld> Request from 86.187.160.205 via cp3032 cp3032, Varnish XID 72810611 Error: 503, Backend fetch failed at Wed, 20 Sep 2017 07:36:54 GMT
2017-09-20 08:04:33 <Stryn> last 40 minutes not possible to edit ,getting error
2017-09-20 08:05:15 <TheresNoTime> Stryn: known issues, should be working again soon (Varnish, T175803)
2017-09-20 08:05:15 <stashbot> T175803: Text eqiad varnish 503 spikes - https://phabricator.wikimedia.org/T175803
2017-09-20 08:05:49 <TheresNoTime> 's gonna be intermittent though :(
2017-09-20 08:06:23 <DaneGeld> Not intermittent here, getting it constantly now trying to view anything on simple.wiktionary
2017-09-20 08:06:31 <DaneGeld> can't do anything
2017-09-20 08:06:37 <TheresNoTime> https://grafana.wikimedia.org/dashboard/file/varnish-http-errors.json?refresh=1m&orgId=1&from=now-12h&to=now
2017-09-20 08:07:13 <TheresNoTime> we're currently in a spike, and a rather large one at that, but it /should/ be resolving soon (ops to restart varnish/depool)
2017-09-20 08:12:04 <DaneGeld> Edits are going through, but only after re-sending them several times. Is this affecting all of wiki(p/m)edia?
2017-09-20 08:12:48 <TheresNoTime> DaneGeld: you should soon be routed to a different datacenter, so it'll seem resolved - this is affecting multiple projects
2017-09-20 08:13:33 <DaneGeld> ok, thanks TheresNoTime - I'll go and grab a coffee and develop some patience! ;)
2017-09-20 09:13:38 <jeblad> nnwiki down?
2017-09-20 09:13:48 <jeblad> nn.wikipedia.org
2017-09-20 09:14:06 <jeblad> it is back! =)
2017-09-20 09:21:33 <jeblad> Now fr is dead?
2017-09-20 09:21:54 <jeblad> It could be a good idea to provide some info…
2017-09-20 09:23:35 <NotASpy> jeblad: just refresh, there's some transient issues at the moment, but nothing is down completely.
2017-09-20 09:24:08 <jeblad> I would say it is down when the page dosn't load
2017-09-20 09:25:25 <TheresNoTime> T175803
2017-09-20 09:25:25 <stashbot> T175803: Text eqiad varnish 503 spikes - https://phabricator.wikimedia.org/T175803
2017-09-20 09:25:31 <TheresNoTime> Known and will recover soon
2017-09-20 09:27:52 <jeblad> Just lie a visit in a bar, "I will recover…"
2017-09-20 09:27:57 <jeblad> like
2017-09-20 09:33:11 <thedj> this is disconcerting though
2017-09-20 09:35:55 <thedj> let's hope ops figures out what's triggering this. 3 times within several hours is definetly a pattern :)
2017-09-20 11:17:04 <Jonas_WMDE> anyone from CirrusSearch around?
2017-09-20 11:18:14 <gehel> Jonas_WMDE: you usually have more success finding CirrusSearch people in #wikimedia-discovery
2017-09-20 11:18:43 <gehel> Jonas_WMDE: that being said, dcausse should be around (or back soon-ish) and I'm around if you have an easy question...
2017-09-20 11:18:54 <dcausse> o/
2017-09-20 11:20:04 <Jonas_WMDE> thanks gehel
2017-09-20 13:48:24 <primefac> today's stupid question, brought to you by primefac:
2017-09-20 13:48:38 <primefac> there's no way to disable/block animated gifs from being used on the Main Page, is there?
2017-09-20 13:48:58 <primefac> like, from a "new feature to implement" perspective
2017-09-20 13:53:42 <NotASpy> I don't know, could you blacklist all *.GIF files, then whitelist them for everything except the Main Page ?
2017-09-20 13:55:25 <primefac> would that work for transclusions, though? The main page doesn't actually *host* material
2017-09-20 13:55:37 <primefac> (or were you talking client-side)
2017-09-20 13:59:47 <NotASpy> oh yeah, transclusions would be an issue.
2017-09-20 14:01:35 <Esther> primefac: Why?
2017-09-20 14:02:44 <primefac> someone's requesting that gifs be disabled on the Main Page because they're distracting
2017-09-20 14:03:07 <Esther> They're distracting on other pages too.
2017-09-20 14:03:08 <primefac> I told them (politely) to bugger off but they're being quite insistent
2017-09-20 14:03:13 <Esther> We should have a play button for them.
2017-09-20 14:03:21 <Esther> I think Twitter does that.
2017-09-20 14:04:10 <NotASpy> and imgur
2017-09-20 14:04:29 <jeblad> A lot of people has problems with flickering
2017-09-20 14:05:02 <jeblad> All kinds of animations should be under user control
2017-09-20 14:05:20 <Esther> GIF doesn't really support that natively.
2017-09-20 14:05:30 <Esther> But we could do that with a layer on top.
2017-09-20 14:06:20 <Esther> https://www.pcworld.com/article/3143574/software/how-to-stop-animated-gifs-in-chrome-and-firefox.html
2017-09-20 14:06:46 <primefac> thanks, I'll send them the link
2017-09-20 14:07:09 <yeryry> I don't see why non-animated gifs would need to be on the main page at all? So the distinction between animated/non-animated could be ignored, and block all gifs?
2017-09-20 14:10:24 <Esther> yeryry: Seems pretty extreme and silly to block all GIFs.
2017-09-20 14:10:41 <Esther> I don't think making a distinction between the main page and other pages is very useful.
2017-09-20 14:10:46 <DanielK_WMDE> how would "blocking" work for a single page?
2017-09-20 14:11:02 <DanielK_WMDE> how is that configured? how does that interact with template transclusion?
2017-09-20 14:11:11 <DanielK_WMDE> what would be shown instead?
2017-09-20 14:11:52 <DanielK_WMDE> this seems like a question of either a) local wiki policy or b) client side user preference (i.e. a browser plugin)
2017-09-20 14:11:58 <jeblad> Dancing norwegian trolls!
2017-09-20 14:12:05 <DanielK_WMDE> also, why are animated gifs distracting on the main page, but not on other pages?
2017-09-20 14:12:12 <Reedy> imagines jeblad dancing
2017-09-20 14:12:18 <DanielK_WMDE> jeblad: featuring you?
2017-09-20 14:12:36 <DanielK_WMDE> Reedy: in a green tutu ;)
2017-09-20 14:12:38 <Esther> DanielK_WMDE: MediaWiki should probably have an option to stop/pause animated GIFs.
2017-09-20 14:12:43 <jeblad> Yes!! On the frontpage!!
2017-09-20 14:12:58 <DanielK_WMDE> Esther: an option where? mediawiki isn't "running" them. so it can't stop them.
2017-09-20 14:13:00 <Esther> Though they've got to be less common on Wikimedia wikis than on Facebook/Twitter.
2017-09-20 14:13:07 <primefac> apparently watching them "day after day" is distracting and makes them nauseous
2017-09-20 14:13:31 <DanielK_WMDE> primefac: but only on the wikipedia main page, not anywhere else?...
2017-09-20 14:13:32 <Esther> DanielK_WMDE: Special:Preferences of course. MediaWiki is storing the GIFs, outputting the GIFs, sometimes thumbnailing the GIFs.
2017-09-20 14:13:39 <primefac> DanielK_WMDE, apparently
2017-09-20 14:13:43 <yeryry> Is there ever animated gifs on the main page anyway?
2017-09-20 14:13:46 <primefac> yeah
2017-09-20 14:13:47 <Esther> I think it's kind of silly to suggest that MediaWiki is an uninvolved party here.
2017-09-20 14:13:49 <primefac> Cassini was on it
2017-09-20 14:13:51 <primefac> yesterday
2017-09-20 14:13:58 <DanielK_WMDE> Esther: yea, but mediawiki is not animating gifs. the browser does that. mw has no control over that whatsoever.
2017-09-20 14:14:01 <yeryry> Oh yeah
2017-09-20 14:14:04 <Esther> yeryry: Sometimes the featured image is an animated GIF.
2017-09-20 14:14:21 <Esther> DanielK_WMDE: MediaWiki could add a layer on top for accessibility.
2017-09-20 14:14:23 <primefac> https://en.wikipedia.org/wiki/File:Cassini-huygens_anim.gif
2017-09-20 14:14:34 <DanielK_WMDE> Esther: technically, mw is not involved. it would actually be quite hard (and resource intensive) to change that
2017-09-20 14:14:35 <Esther> DanielK_WMDE: The same way we support Ogg Vorbis?
2017-09-20 14:14:47 <Esther> It's not unprecedented to have a media player.
2017-09-20 14:14:57 <DanielK_WMDE> Esther: sure, could. complicated, unstable, using lots of resources. not worth the pain.
2017-09-20 14:15:21 <Esther> You could maybe re-use the media player to work with GIFs?
2017-09-20 14:15:23 <Esther> That'd be kind of neat.
2017-09-20 14:15:32 <DanielK_WMDE> yes, we could in theory treat animated gifs as timed media, instead of images. that would be a pretty massive breaking change
2017-09-20 14:15:39 <TheresNoTime> Ease of using a browser extension vs ease of implementing a media control layer for GIF
2017-09-20 14:15:42 <Esther> The ability to pause GIFs at a specific frame or walk through GIFs would be useful.
2017-09-20 14:15:42 <yeryry> Could have CSS that replaces a static frame from the animation with the original gif when hovered?
2017-09-20 14:16:02 <Esther> DanielK_WMDE: Breaking for whom?
2017-09-20 14:16:06 <DanielK_WMDE> Esther: i support the idea of using a mediaplayer for gifs in theory, but not in practice :)
2017-09-20 14:16:27 <DanielK_WMDE> Esther: breaking the expectations that animated gifs play immediatly when loading a page.
2017-09-20 14:16:38 <Esther> Yeah, that's fine.
2017-09-20 14:16:39 <yeryry> As a user-preference.
2017-09-20 14:16:40 <DanielK_WMDE> sore, that'S exactly what these pople want to avoid
2017-09-20 14:16:49 <DanielK_WMDE> but then there are others wo want exaqctly that to happen
2017-09-20 14:16:55 <Esther> Some people? Lots of people hate auto-playing videos.
2017-09-20 14:17:06 <Esther> And animated GIFs are just silent auto-playing videos.
2017-09-20 14:17:08 <Esther> Without user controls.
2017-09-20 14:17:21 <TheresNoTime> I think it'd be more reasonable for the one user affected to install an extension (such as https://addons.mozilla.org/en-GB/firefox/addon/toggle-animated-gifs/) than for mw to implement this
2017-09-20 14:17:30 <primefac> ^
2017-09-20 14:17:34 <Esther> If you're going to output animated content, I think supporting a pause or stop feature is reasonable. Shifting blame to the browser/client is kind of a cop-out.
2017-09-20 14:17:35 <yeryry> Yup
2017-09-20 14:17:47 <primefac> Esther, it's kind of a question of necessity
2017-09-20 14:17:50 <jeblad> Before doing anything, figure out how important this is. Only complaining isn't a good reason for doing something.
2017-09-20 14:17:54 <primefac> if there's only one person in the world who finds it annoying, why bother
2017-09-20 14:18:04 <DanielK_WMDE> Esther: yep. for better or worse. that can in theory be changed. it's not easy, it's not cheap, and it may not be desirable to all users. needs community discussion and technical assessment.
2017-09-20 14:18:11 <primefac> I told them to start a VPP thread if they were that concerned
2017-09-20 14:18:20 <Esther> I'm not taking up this fight.
2017-09-20 14:18:41 <Esther> But I also don't support a bunch of "think about the costs!!!" arguments.
2017-09-20 14:18:50 <Esther> This isn't new or novel. Other sites have already worked on this.
2017-09-20 14:19:06 <Esther> Including ours!
2017-09-20 14:19:15 <jeblad> Only people I know with real problems with animated gifs are people with some kind of epilepsy and ... err.. what is it acalled in english …… kind of headache that is induced by flickering
2017-09-20 14:19:32 <DanielK_WMDE> Esther: the fact is that gifs are treated as images by mw and html. not like timed media. that has historical reasons, and is not ideal, but it'S not trivial to change, and we shouldn't try without having a very giid reason, and we are sure we don't break anything.
2017-09-20 14:19:57 <Esther> DanielK_WMDE: The ability to stop an animation is a pretty good reason.
2017-09-20 14:20:17 <Esther> Like the premise that you should have unstoppable animations on a page is a non-starter, IMO.
2017-09-20 14:20:36 <DanielK_WMDE> as i said - i support this notion in theory. i see a bunch of practical issues
2017-09-20 14:21:11 <DanielK_WMDE> start a community discussion, get technical assessment going (or find someone else to do those things), then we can do a cost/benefit analysis.
2017-09-20 14:21:17 <Esther> It also wouldn't be terribly complicated to bake an option into MediaWiki's image syntax.
2017-09-20 14:21:22 <DanielK_WMDE> i'm not a fan of gifs as they are.
2017-09-20 14:21:29 <Esther> [[File:Animated.gif|autoplay]]
2017-09-20 14:21:53 <DanielK_WMDE> sure, could be done via the timed media handler. i like the idea in theory.
2017-09-20 14:32:24 <DanielK_WMDE> anomated gif of the day: https://giphy.com/gifs/animated-the-beatles-QpWDP1YMziaQw/fullscreen
2017-09-20 14:33:50 <jeblad> Funny walks…
2017-09-20 14:52:09 <Nudin> Technical Advice IRC meeting in 10 minutes in channel #wikimedia-tech, hosts: @addshore & @Tobi_WMDE_SW - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
2017-09-20 14:52:28 <MichaelSchoenitz> Technical Advice IRC meeting in 10 minutes in channel #wikimedia-tech, hosts: @addshore & @Tobi_WMDE_SW - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
2017-09-20 14:54:49 <ShakespeareFan00> Is there a set of notes for this?
2017-09-20 14:55:41 <ShakespeareFan00> Also is this about specifc topic or are general questions allowed?
2017-09-20 14:55:55 <andre__> did you read the link?
2017-09-20 14:56:33 <ShakespeareFan00> I was reading - https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting#Next_meeting_on_September_20th.2C_3_pm_UTC
2017-09-20 14:57:09 <ShakespeareFan00> which didn't answer my question :(
2017-09-20 14:57:25 <andre__> It says "All questions are welcome!"
2017-09-20 14:57:31 <andre__> regarding your second question
2017-09-20 14:57:34 <ShakespeareFan00> On the page or in channel?
2017-09-20 14:57:41 <kolbert> On the page
2017-09-20 14:57:41 <andre__> on https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
2017-09-20 14:57:48 <ShakespeareFan00> Okay...
2017-09-20 14:58:03 <ShakespeareFan00> I will proably just wait for a transcript then...
2017-09-20 14:58:27 <kolbert> that's a sure way to get a question answered...
2017-09-20 15:00:19 <addshore> Hi all! o/
2017-09-20 15:00:32 <DanielK_WMDE> kolbert: the best way to get a question answered on the itnernet is to post a wrong answer. someone is sure to correct you.
2017-09-20 15:00:51 <Aguyintobooks> are you sure?
2017-09-20 15:01:11 <kolbert> Haha, that is fair
2017-09-20 15:01:27 <DanielK_WMDE> https://meta.wikimedia.org/wiki/Cunningham%27s_Law
2017-09-20 15:02:08 <addshore> So we are here for another installment of the Technical Advice IRC!
2017-09-20 15:02:14 <kolbert> Is it possible to access Wikipedia through a non-TLS connection?
2017-09-20 15:02:21 <addshore> As always all questions welcome!
2017-09-20 15:02:44 <kolbert> and by extension, does that make relative linking no longer useful
2017-09-20 15:03:14 <addshore> kolbert: as far as I know no, all connections are https
2017-09-20 15:03:16 <psychoslave> Technical Advice IRC Meeting time ?
2017-09-20 15:03:19 <addshore> psychoslave: indeed
2017-09-20 15:03:30 <psychoslave> :)
2017-09-20 15:03:35 <smartyrad> Hey everyone, I was working on a beginner task located here https://phabricator.wikimedia.org/T173434
2017-09-20 15:04:00 <addshore> Hi smartyrad!
2017-09-20 15:04:14 <addshore> wonders if CFisch_WMDE is here
2017-09-20 15:04:50 <smartyrad> Since I am new to this community, I wanted to take up something relatively simple. My query is as to whether the only changes to be made are the ones described in the 3 *.js files
2017-09-20 15:05:36 <smartyrad> addshore : Hello :)
2017-09-20 15:06:11 <Freddy2001> hi
2017-09-20 15:06:26 <addshore> smartyrad: looking at the task it looks like that is correct, but best to ask in a comment on the task for that one to be sure :)
2017-09-20 15:08:44 <smartyrad> addshore: Thanks, will do so! I was hesitant to comment there as I didn't have any specific blocker as such
2017-09-20 15:09:39 <addshore> =], yeh just go for it! :)
2017-09-20 15:09:56 <psychoslave> So, as stated here https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting my current wonder is about "Saving data in a Scribunto data module through a Scribunto script execution. "
2017-09-20 15:10:32 <psychoslave> and more information about what I'm trying to do and why is here : https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088773.html
2017-09-20 15:11:12 <andre__> kolbert: https://meta.wikimedia.org/wiki/HTTPS#2015
2017-09-20 15:11:28 <psychoslave> I'm reading the last answer of anomie on tech-l.
2017-09-20 15:14:04 <psychoslave> He gave feedback about his concerns with such a feature
2017-09-20 15:14:37 <smartyrad> I also wanted some of your suggestions on a proposed set of measures we could take to fix this https://phabricator.wikimedia.org/T158909 before I comment my thoughts there
2017-09-20 15:15:04 <smartyrad> Would that be okay?
2017-09-20 15:18:19 <addshore> hmm, smartyrad it's probably just best to comment / discuss directly on the ticket so that the relevant / interested parties are included
2017-09-20 15:19:53 <smartyrad> addshore: True. Sure thing, thanks for all the help :)
2017-09-20 15:19:55 <psychoslave> Well, I'm not sure I really get all the extent of the "parse time" issue.
2017-09-20 15:20:38 <addshore> psychoslave: all I can suggest is to follow up in the email thread for that one
2017-09-20 15:21:50 <psychoslave> ok
2017-09-20 15:24:07 <psychoslave> Now actually, I do then have a more specific, but related, question. Since SemanticScribunto do provide what I'm looking for (actually far more) would there be any issue regarding it's deployement on a wikimedia production website?
2017-09-20 15:25:20 <psychoslave> https://github.com/SemanticMediaWiki/SemanticScribunto and https://upload.wikimedia.org/wikipedia/mediawiki/7/75/EMWCon_Spring_2017_-_Introducing_SemanticScribunto_Extension.pdf for more information on this extension
2017-09-20 15:26:27 <addshore> psychoslave: so, extensions have to go through various stages of review to get deployed (security review, performance review) and generally there also have to be a team willing to maintain it
2017-09-20 15:26:30 <addshore> goes to find a link
2017-09-20 15:26:56 <bawolff> I can tell you about security review if you have any questions about that stage
2017-09-20 15:27:15 <addshore> psychoslave: see https://www.mediawiki.org/wiki/Review_queue :)
2017-09-20 15:28:06 <bawolff> reads logs
2017-09-20 15:28:11 <addshore> :D
2017-09-20 15:28:23 <psychoslave> thank you
2017-09-20 15:28:25 <bawolff> The fact it has "semantic" in the extension name is generally not a good sign for WMF deployment
2017-09-20 15:28:37 <anomie> psychoslave: Regarding enabling anything requiring SemanticMediaWiki on WMF production sites, see https://phabricator.wikimedia.org/T10390
2017-09-20 15:29:02 <addshore> bawolff: indeed
2017-09-20 15:29:04 <psychoslave> Great, thank yo, anomie
2017-09-20 15:31:04 <kolbert> So because HTTPS is used throughout wikimedia sites - is there a point to using relative links?
2017-09-20 15:31:34 <bawolff> I don't really think there's much point using protocol relative links to wikimedia sites
2017-09-20 15:31:53 <bawolff> It seems extraordinarily unlikely we will ever go back to plain HTTP
2017-09-20 15:34:16 <kolbert> It also clogs up Special:LinkSearch if you're looking for HTTP-only results
2017-09-20 15:37:05 <bawolff> yeah, that's kind of unfortunate. Although really that seems more like an issue with Special:Linksearch than a fault with protocol relative urls
2017-09-20 15:42:28 <psychoslave> anomie: are you aware of any plane to allow writing data into wikidata from mediawiki instances ?
2017-09-20 15:43:42 <anomie> psychoslave: I'd be similarly skeptical of something that allowed wikitext constructs to write to wikidata during the parse. You can use the action API to do it from JavaScript while editing with a CORS call to wikidata.org.
2017-09-20 15:46:59 <DanielK_WMDE> psychoslave: using a JS based interactive UI, yes. definitly not during parse.
2017-09-20 15:56:30 <bawolff> Writing anything during parse, other then links table type stuff is a recipe for disaster
2017-09-20 15:59:59 <addshore> Right, that just about wraps up this hour!
2017-09-20 16:03:26 <psychoslave> I have to look at what CORS it, sorry for my ignorance :/
2017-09-20 16:03:55 <Reedy> it's a light tasting beer
2017-09-20 16:03:59 <bawolff> psychoslave: It just lets you make api requests cross domain
2017-09-20 16:04:19 <bawolff> Using the origin paramter of the api
2017-09-20 16:05:00 <psychoslave> well, I'm not looking for such a wide scope, but it's worth knowing it's possible
2017-09-20 16:06:01 <thedj> Reedy: you troll :)
2017-09-20 16:10:41 <psychoslave> So, let me sum up what I understood from the suggestion. The idea would be that, "on publish", javascript would extract relevant data from the current state of the wikicode to save them in a Scribunto module, remove this data from the wikitext, and let resulting wikicode be posted. It that the idea suggested anomie ?
2017-09-20 16:11:51 <anomie> psychoslave: I'd personally be wary of JS that tried to alter the wikitext before submitting without letting the human verify it didn't screw up. But if your wiki's community is fine with that, feel free.
2017-09-20 16:13:59 <psychoslave> Well, I'll see that with them, once I prototyped something. My main concern for now was that I wasn't sure anything like that was possible with current production features.
2017-09-20 16:17:47 <psychoslave> But it seems it is from what I understand, so that's already an important step. :)
2017-09-20 19:55:03 <Krinkle> jQuery 3 upgrade was deployed to meta.wikimedia.org yesterday. Anyone noticed any problems with gadgets/user scripts, or warnings in the console?
2017-09-20 20:37:14 <quiddity> Krinkle, yes warnings in console. https://pastebin.com/raw/CErGxTMd and screenshot http://storage9.static.itmages.com/i/17/0920/h_1505939731_8916324_3271bfdd5f.jpeg
2017-09-20 20:37:58 <quiddity> (I have a lot of gadgets and userscripts... But let me know if/how I can help further diagnose the root causes.)
2017-09-20 20:50:16 <James_F> quiddity: Warnings are fine, we care about actual brokenness. :-)
2017-09-20 20:56:23 <Krinkle> quiddity: Indeed, those are worth solving, but not blocking.
2017-09-20 20:56:45 <Krinkle> quiddity: For the first one, could you try reproduce the fn.load() warning in debug mode to see where it comes from?
2017-09-20 20:56:52 <Krinkle> (the second seems to be from a gadget)
2017-09-20 20:57:04 <quiddity> Ok. You did ask for warnings, so I provided! (and sure, will do..)
2017-09-20 20:57:10 <Krinkle> Yeah, my bad :)
2017-09-20 20:59:04 <quiddity> Krinkle, that adds 1 line: https://pastebin.com/raw/0MiHZ3Jv or http://storage3.static.itmages.com/i/17/0920/h_1505941132_4850987_02922fabd3.jpeg
2017-09-20 20:59:53 <quiddity> ah, that's from the gadget though.
2017-09-20 21:00:59 <TimStarling> RFC meeting starting now in #wikimedia-office: Introduce InterruptMutexManager
2017-09-20 21:04:53 <quiddity> Krinkle, Ah, and the 1st one leads to the top item in my https://meta.wikimedia.org/wiki/User:Quiddity_(WMF)/global.js
2017-09-20 21:05:08 <quiddity> (which I love...)
2017-09-20 21:10:14 <Krinkle> quiddity: Aye, yeah, that should be on('load', fn) instead of load(fn) but also beware that this code will sometimes not work (both before and now) because if 'load' already happened, it runs too late.
2017-09-20 21:10:27 <Krinkle> I think $(document).ready(fn) or simply $(fn) should work fine for that case.
2017-09-20 21:54:07 <quiddity> I tried 6 variations, and only 1 worked. Documented at https://phabricator.wikimedia.org/T109103 (the related feature request)

This page is generated from SQL logs, you can also download static txt files from here