[00:18] thumper: ping? [00:18] otp [00:18] thumper: kk [00:21] anastasiamac_: ping [00:59] menn0: ok, back but need food [00:59] whazzup? [00:59] * thumper finds the tag "fallout" amusing [01:00] * thumper needs food badly [01:20] thumper: I just finished lunch. let me know when you're available [01:20] can anyone tell me if wwitzel3 and I need to implement storage for the new GCE provider? [01:20] my understanding is that we don't [01:22] menn0: my lunch is cooking but I have a few minutes now [01:23] thumper: ok [01:23] thumper: so this maas issue is that since dimiter's big address handling change [01:23] thumper: no state server thinks it is the master any more [01:23] hahaha [01:23] oops [01:24] why? [01:24] in mongo.IsMaster [01:24] the address for the replicaset master is compared against the machine's internal address [01:24] if they match then IsMaster returns true [01:24] but they no longer match [01:25] can we compare across all addreses for the machine? [01:25] it seems on maas the replicaset master address comes back as the DNS address of the host. e.g. juju-qa-maas-node-29.maas [01:26] but the "best" internal address that it gets compared against is an IP [01:26] I have a fix which does just that [01:26] I just wanted to check that you thought it was a sane idea [01:27] I guess there's a risk of 2 machines thinking they are master [01:27] a fix which compares against all? [01:27] yes [01:27] it is unlikely to cause two to think they are master will it? [01:27] if the replicaset master addr comes back as say "localhost" or some machine/link local address [01:27] and the machine also has that in it's list [01:28] but I don't think that's likely because I think link local addresses are already being filtered out [01:28] * thumper thinks [01:28] I say "it may well fix it and doesn't look like it'll hurt, and whoever is up next can back it out and fix another way if they are so inclined" [01:29] so do it [01:29] cool [01:29] i'll make sure dimiter knows what i've done so that he can verify [01:29] * thumper nods [01:29] there might also be another way to skin this cat that he knows about [01:30] * menn0 thought he might actually be able to commit something today... [01:30] (that wasn't a CI unblocker) [01:31] menn0: the mover of blocks [01:31] my 1 year old son is good at moving blocks [01:32] must be in the genes [01:32] ha [01:40] menn0: take "the mover of blocks", my one would have been "meen0: the unblocker" :) [01:55] thumper: here's that fix: http://reviews.vapour.ws/r/647/ [01:55] * thumper looks [01:56] the unblockenator [01:56] unblockenologist [01:56] thumper: this fix is for 1.21 [01:57] thumper: i'll forward port it once it's in [01:57] shipit [01:59] menn0: i think that u r certainly turning unblocking into an art more than a science :-) of course, if u r happy with the title.. [01:59] thumper: menn0: there should be a reward for unblocking CI the most.. [01:59] beer! [01:59] actually scotch might be more appropriate... [02:00] menn0: as suprising as it may be, not everyone will be encouraged by beer ... [02:00] menn0: or scotch [02:00] menn0 will be [02:00] menn0: but certainly a start [02:00] menn0: what sort of scotch? [02:00] * thumper is not a fan [02:01] thumper: I like less challenging single malts [02:01] thumper: I don't really go for the really smoky/peaty ones [02:02] menn0: how is scotch different from whiskey?> [02:03] thumper: scotch is "scotch whiskey" ... whiskey from Scotland [02:04] ah [02:27] thumper: hey thank you again for green-lighting that branch. i'll have more things landing in the coming days to get it into shape. [02:27] katco: ack [02:27] thumper: ? [02:28] thumper: ack as in TCP/IP ack? [02:28] katco: that is a general positive response "ok, got it" [02:28] yes [02:28] thumper: ah ok :) [02:28] sorry, more irc specific geekiness [02:28] thumper: you'll be happy to know that the stderr flag is coming back out now that machine agent is refactored [02:28] * katco enjoys geekiness, just wanted to make sure ;) [02:31] * thumper nods [02:32] I can hear the girls watching avengers... again... [02:38] anyone could have a look at https://github.com/juju/names/pull/35?... with a pretty plz? [02:38] waigani: ^^ [02:40] thumper: i've heard avangers r beta than lion king :) [02:44] anastasiamac: I'm a little cautious about reusing the validUserPart regex if it just *happens* to co-incide with the charm usage [02:44] anastasiamac: is that usage semantically correct too? [02:46] * jw4 breaks for supper - sorry :) [02:46] jw4: it's not exported so not intended for reuse, right? anastasiamac? [02:46] waigani: I just mean reusing it in charm.go from user.go [02:47] * jw4 leaves for real this time [02:48] waigani: not intented for re-use outside but m re-using it in names itself [02:48] waigani: should I not? [02:49] waigani: if user reg ex changes for whatever reason, i'd like my part to still identify valid user [02:49] ah right, well, the definition of schema in the code is // schema:~user/series/name-revision [02:54] ok fixes for the CI blocker merged into 1.21 and master [02:54] re-enabling the build-revision jenkins job now [02:54] morning all [02:54] anastasiamac: so there would be an issue if the format of the "user" in the schema and the "user" in the validation functions changed. But, I don't see why that would happen, and if the format changes, you'd have problems regardless and given charm.go is in the names package I think it's fine for there to be a package level "user" that it uses [02:55] anastasiamac: so, LGTM from me. [02:56] waigani: thnx :-) [02:59] anastasiamac: and LGTM from me - I didn't know the definition of the schema used the ~user part :) [02:59] thnx jw4 :) and here I thought u were going to leave for real... [03:00] lol [03:00] confession: I'm actually BACK [03:00] I scarfed [03:01] * thumper looks at anastasiamac's names branch [03:03] anastasiamac: just a few easy tweaks [03:10] menn0, looks like build revision 2179 has your fix for the MaaS upgrade and is being run through CI now [03:12] jog: yep [03:12] jog: i'm fairly confident it'll pass now [03:12] menn0, are you done with finfolk? [03:13] I am [03:13] I should stop the server that running there, so this revision build can run when it gets to that test [03:13] only the MAAS server is running now [03:14] jog: I killed the other machine [03:14] jog: but please check that everything is in order [03:15] jog: I've cleaned up what I was using [03:15] * menn0 heads out to get some groceries [03:15] menn0, thanks! and yeah it's just the MaaS server that we shutdown [03:15] menn0, thanks for the quick help on this one! === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [03:29] thumper: about separate var blocks... [03:29] thumper: wanted to group exported vars vs non-exported... [03:29] thumper: u don't like this grouping? [03:29] thumper: one var block for all is beta? [03:36] I don't see why they need to be separated [03:36] exported vars have comments [03:36] internal ones don't [03:36] the comments are enough separation I think [03:39] oh my god [03:39] this coffee is good [03:39] I feel I may need another real soon now [03:40] thumper: k since u have found a gr8 coffee, I'll put vars in one block... [03:40] waigani: you can't land stuff until this page: https://bugs.launchpad.net/juju-core/+bugs?field.tag=ci+regression&field.tags_combinator=ALL has no criticals [03:40] didn't find... made [03:41] thumper: good to know, I was using a different filter on lp [03:41] the tags stay there until CI passes, then it removes them [03:41] that is when master is open for landing again [03:42] thumper: I thought it was only Critical though? And not including Fix Released? I shortened that to: http://goo.gl/4zd1e9 [03:43] jw4: it is, that's why I said no criticals [03:43] thumper: doh :) [03:43] thumper: if u made a gr8 coffee, does it mean u r k with me merging my PR into names? [03:43] jw4: I saved that page, so now I just start typing "regression" and hit enter [03:43] thumper: nice [03:44] anastasiamac: do you feel strongly that they should be separate? [03:44] thumper: not strongly enough :) [03:44] thumper: they r distinct [03:45] thumper: whether we r separating them otherwise si a style [03:45] thumper: I am pendantic and will separate and teeth things apart until I get to nano levels [03:46] anastasiamac: I'm happy that the local and exported vars are grouped within the var statement [03:46] but we don't need multiple var statements [03:46] thumper: excellent! I merge then? :P [03:46] anastasiamac: are they grouped yet? [03:47] * thumper refreshes [03:47] sorry hadn't been looking [03:47] thumper: they r :) [03:48] line 36 of charm.go [03:48] they are almost... [03:49] thumper: ur coffee must b really good! m on it :-) [03:49] unfortunately my coffee is finished [03:49] I did consider making a big cup 4 shot one [03:49] but decided against it [03:49] perhaps I should have [03:49] anastasiamac: merge, quick! while you've still got a chance! [03:51] thumper: should be perfect now but I'll re-order it for mattyw [03:51] anastasiamac, waigani sorry - I jumped in at the wrong/ right time :) [03:52] mattyw: surely URI not URL [03:52] waigani: m weaning myself off coffee (and onto the coke) so will not b as quick as all these "real coffee" drinkers :D [03:52] why no coffee? [03:52] that just seems cruel [03:53] coffee is so much better for you than coke [03:53] thumper, I think so - but isn't the accepted name CharmURL? [03:53] mattyw: probably [03:53] thumper: apparently my coffee is not up to wallyworld's standard... so coke it is atm [03:53] tut-tut [03:53] I used to despise decent coffee - it felt like a waste of money [03:53] all it took was one trip to Dunedin [03:54] mattyw: and now you want to buy an espresso machine? [03:54] jog: thank you for the debugging help [03:55] thumper, thinking about it [03:55] anastasiamac, I'm basically not too fussed about the name [03:55] menn0, np... the maas upgrade tests should start fairly soon for 2179 [03:56] anastasiamac, but changing the ordering I think is a small change but very useful [03:56] anastasiamac, at least for me :) [03:56] I was half joking about URI vs URL [03:56] mattyw: the ordering is a bit of a thing for me, actually.. [03:57] mattyw: i was hoping to group local and exported vars [03:57] mattyw: m look n and may change in a sec :) [03:58] anastasiamac, that makes a lot more sense, to be totally explicit - what confused me was I expected charmStoreSchemaSnippet to be the regex for the whole thing charm url - and then when I read the definition I was suprised [03:59] mattyw: ic [03:59] anastasiamac, ordering based on exported or not makes a lot of sense - I'd be happy with just a comment above local and charm store snippet I think [03:59] anastasiamac, although the more I talk about it the more I think it's fine as it is [03:59] mattyw: let's talk some more than :) [03:59] anastasiamac, haha [04:00] mattyw: well, this area my be confusing [04:00] mattyw: and I'd like it to b clear from a glance [04:00] mattyw: there is a block comment above the whole of var block [04:01] anastasiamac, ah - I was about to suggest something like that [04:01] mattyw: explaining what the whole URL (URI ***looking at thumper***) is [04:01] anastasiamac, yeah - that's amazing - just land it as is - ignore me :) [04:01] mattyw: r u sure? [04:02] anastasiamac, I'd be tempted to add a comment above validCharmRegEx saying - this is the regex for the whole CharmURL [04:02] anastasiamac, but then the actual regex basically says that [04:02] anastasiamac, so even that feels redundant [04:03] anastasiamac, I'm definitely in bikeshedding territory now though - just land it :) [04:03] mattyw: k. I'll land as is and might come back to it as needed coz m still planning to head to juju/charm with it before even getting to juju/juju... [04:05] * anastasiamac landed tiny PR [04:08] anastasiamac, tiny PRs are the worst :) [04:08] :) [04:12] waigani, ping? [04:33] mattyw: pong [04:34] waigani, just looking at http://reviews.vapour.ws/r/474/diff/ -> what is OtherState for in storeManagerStateSuite? [04:34] mattyw: it's the state for another env, I should probably rename it to make that clear [04:35] mattyw: also that branch is a WIP, I'll be pushing up the latest tomorrow [04:35] waigani, that's what I was going to suggest :) [04:35] waigani, ok cool [04:36] mattyw: AND the fam is demanding that I join them for dinner, which I better do unless I want to sleep outside tonight! [04:36] waigani, enjoy! [04:42] jog: the maas upgrade test for 1.21 just passed [04:42] woo hoo! [04:43] yay [04:43] how long does it usually wait on the "Attempting to connect to 10.0.30.173:22" line? [04:44] menn0: can you mark as fix released or does that need to be someone else? [04:45] jw4: it waits a while.. it's trying to make an API connection as the instance comes up [04:45] menn0: yeah - it seemed to be several minutes [04:45] menn0: I think someone from QA is supposed to do it. jog? [04:46] jw4, menn0, in this case it's waiting for MaaS to boot a machine... usually around 10 minutes [04:46] jw4: that's what I was seeing while manually testing with maas [04:46] jog: I see [04:46] menn0: cool - so you were testing your changes on the same hardware that's running the tests? [04:47] jog: do you know how CI becomes unblocked? does it require a manual step by someone on the QA team or is it automated based on test results? [04:47] menn0, jog it also looks like we only have one (or limited) hardware groups for maas? [04:47] menn0: I think it's automated once the bug is marked Fix Released, but I could be wrong [04:48] jw4: yeah I was using the host that Jenkins uses for MaaS tests (on KVM) [04:48] menn0: interesting. Cool, but surprising [04:48] menn0, I believe fixed-released will unblock [04:49] jw4: suprising? [04:50] jog: it's a shame that the "Fix Released" has 2 meanings [04:50] s/ the// [04:50] oh well [04:50] menn0: I guess setting up a maas environment isn't trivial - but it seems like while you were working on finfolk none of the CI tests could run [04:50] err actually fixed-committed [04:51] jog: I don't think fixed committed will unblock CI? [04:51] jw4, we're working on fixing that... finfolk was upgrade last week, so we can run multiple environments [04:51] jw4: that's what sinzui told me to do :) he disabled one of the top level CI jobs [04:52] jog, menn0 I see [04:52] jw4: the bug needed fixing and that was the fastest way to get it sorted [04:52] menn0: well (relatively speaking) it WAS lickety split fast [04:52] jw4: i'd like to get my machine set up to do MaaS on KVM locally [04:53] menn0: yeah me too [04:54] jog: yeah I don't think Fix Committed alone is enough to unblock CI [04:54] it's also possible to downgrade the bug from critical to high and it will unblock [04:54] jog: it's still blocked now and I marked this ticket as Fix Committed quite some time ago [04:54] jog: there must be something else to it [04:54] menn0, jog : I bet if you mark it as fixed released it'll unblock [04:55] menn0: maas-upgrade-trusty-amd64 looks set to pass momentarily too [04:55] jw4: I think you're right but is that actually the correct process? [04:55] * jw4 shrugs [04:55] woot! [04:55] that's where I'm lost too [04:55] shall we wait for the second upgrade test to pass... there are two mass tests one for devel (which already passed) and one for stable maas [04:56] the upgrade is actually going on now [04:56] jog, yeah - the second one is the one I'm willing on as we watch :) [04:58] woot [05:05] jog: so when do the maas upgrade tests for master run? [05:05] when a commit is picked up from that branch [05:08] menn0, did you already apply this fix there? [05:08] ah yes it looks like you did [05:10] jog: yep I did. I merged them one after the other. [05:11] jog: i'm about to EOD (and I imagine you were supposed to have quite some time ago) [05:13] menn0, it's building now http://juju-ci.vapour.ws:8080/job/build-revision/2180/console [05:13] jog: ok cool [05:15] nice and we have a blessed build for 1.21 [05:15] http://reports.vapour.ws/releases/2179 [05:17] jog: \o/ [05:25] * menn0 is EOD [05:39] FWIW sinzui, mgz_, et. al. - I believe https://bugs.launchpad.net/juju-core/+bug/1403200 has passed all tests and deserves to be marked fix released [05:39] Bug #1403200: maas upgrades do not complete

[06:03] davecheney, ping? [06:03] davecheney, you know what - cancel that and ignore me forever [06:03] * mattyw needs to read docs more carefully [06:05] morning axw and wallyworld, how are you guys doing? [06:33] axw wallyworld sorry, keep getting dc here if you ansnwered === urulama is now known as urulama|out [07:02] jam1: axw is off until Jan, I think [07:03] jam1: wallyworld is off for the day ;) [07:03] jam1: wallyworld will b back tomorrow === liam_ is now known as Guest72494 [07:08] jam1: did u get my last msgs about axw and wallyworld? === ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: see calendar | Bug reports: https://bugs.launchpad.net/juju-core/ [07:33] CI no longer blocked [07:49] previously failed PRs re-queued for merging [07:50] anastasiamac: yes, apparently you didn't get mine: [07:50] jam1 [07:50] 09:05 [07:50] anastasiamac: thanks, looking at the calendar it looks like both of them are off today [07:51] jam1: yes, b oth r off today [07:51] jam1: and ian is back tomorrow :) [08:11] menn0, hey are you around? [08:12] menn0: kinda :) [08:19] menn0, :) [08:19] menn0, so your fix worked [08:20] menn0, thanks for the quick response [08:21] dimitern: no problems. [08:21] dimitern: is it the best fix though? [08:22] menn0, I don't know about the best, but it's fool-proof at least [08:23] menn0, I'll propose a slight fix to change the ordering of addresses returned by maas's instance.Addresses method [08:23] menn0, which will make it slightly faster and in your patch the loop will do a single iteration most of the time [08:26] * dimitern needs to step out for a while [08:27] dimitern: that sounds good [08:28] dimitern: that loop doesn't get called that often and there's not going to be huge numbers of addresses to check through so I don't think performance is much of an issue [09:11] hi axw [09:11] jam1: heya [09:11] mark's in another discussion right now, so I've got some time if you want to give/get feedback on anything [09:12] jam1: I have only just started looking at comments, nothing really controversial [09:12] I really don't like count,size but maybe it's just me [09:12] man, I wish I could use VIM to edit Google docs :) [09:12] axw: so what mark really likes is clean, easy to read syntax [09:13] and he feels that : an x, etc add a lot to how hard it is to read a given string [09:14] jam1: my take on it is that the number doesn't mean anything when you see it first. so then you have to go digging into documentation, rather than it being obvious in the first case (Nx being a fairly universal way of representing a multiplier, I think). but admittedly it doesn't work when you don't have a size [09:16] jam1: glad to see NFS out of scope :) [09:27] jam1: "pool" is just the new term for "source"? [09:27] I don't recall there being talk of pools previously [09:38] dimitern, ping? [09:38] mattyw, hey [09:46] axw: pool is being explicitly fleshed out as a way to start passing extra parameters into the system, without overloading the "—storage" parameter. [09:46] jam1: yeah, just read over that section a bit more. I like it. [09:47] jam1: any general feedback/news before I head off? [09:48] axw: I think we're pretty happy with what we've gotten to, and I'm just trying to make sure the current doc is consistent [09:48] axw: we're soliciting feedback at this point (from maas, antes, etc) [09:48] jam1: cool [09:49] alright, I'm going to go have a holiday then ;) [09:49] jam1: thanks, ttyl [09:51] axw: enjoy [09:59] TheMue: dimitern: I'm going to be a few minutes late to standup, sorry [09:59] voidspace, ok, np [09:59] voidspace: ok [10:00] mgz_, hey, do you know when 1.21-beta4 is due? [10:52] dimitern: I'm pretty sure it was due at least a week ago [10:52] Our original promise was 1.21 on Nov 15 [10:52] which we are *way* past. [10:55] jam1, Oh, I see - well with the api-endpoints fix landed it can be release now [10:56] jam1, although during my live testing I discovered an issue fixed on master and not backported to 1.21 which is important [10:56] jam1, I'll file a bug for it and have a chat with sinzui should 1.21-beta4 wait for it [10:57] dimitern: sounds like something that should block, and you've got a couple hours before mgz/sinzui would possibly build a 1.21-beta4 release :) [10:57] dimitern: I'm happy for you to delegate that backport, but if you've found something serious, we should be serious about it. [10:58] jam1, right, now's the time then [10:59] jam1, the issue is apt-get retrying logic is faulty - we're calling cmd.CombinedOutput more than once, which errors out after the first call as Stdout is already set [11:00] dimitern: sounds like a real, but not too hard to fix, bug, rigthH? [11:00] jam1, the fix is in juju/utils/apt, so 1.21 needs to (carefully - as there are about a month of changes in utils since) start using a newer utils [11:00] or we backport to what they are currently using [11:01] yes, it sucks, but it might be less mental overhead [11:04] * jam1 heads to lunch === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [12:30] dimitern: yeah, beta4 is overdue, we're trying to release it currently - have got a good rev after your fix backport [12:31] mgz_, there's an issue I discovered during my live tests - apt-get retry logic is not working [12:31] do you have an idea when it regressed? [12:31] mgz_, which is already fixed on master, but not backported to 1.21 [12:32] mgz_, I know as I fixed it in juju/utils/apt, but 1.21 uses an earlier rev of utils [12:32] well, certainly backport [12:32] mgz_, should we hit the red button until this lands? [12:32] but is this a new breakage that wasn't in beta3? [12:34] mgz_, let me check [12:38] mgz_, it was broken since at least alpha3 (or beta2 - not quite sure; the commit log is ambiguous) [12:39] okay, so I think we try to get your fix for this beta, but it's not the end of the world if we don't [12:42] mgz_, scratch that - alpha3 is more likely [12:42] mgz_, ok, I'll file a bug then and target it [12:43] * dimitern thinks *everyone* should rebase and merge minor commits before they end up in master [12:44] or at least be aware they will end up on master and use helpful commit logs - sifting through like 30 commits like "fix dependencies.tsv", "update dependencies.tsv" or "add dependencies of dependencies to dependencies.tsv", are *not* helpful at all to point to *what* changed [12:45] thanks dimitern === kadams54 is now known as kadams54-away [12:52] mgz_, there's a pre-existing bug 1394524 which I now retargeted for 1.21-beta4 [12:52] Bug #1394524: juju/utils/apt retrying logic is poorly tested and can fail the second time

[13:25] ericsnow: ping [13:50] jam1: sorry, was away today but am online for a short time now [14:07] fwereade: was there a decision about what to do about exposing zones to charms? Are we just going to let charms set their zone in their relation data the old fashioned way? [14:07] natefinch, ah, sorry [14:08] natefinch, we should certainly expose it, but I don't think there's any reason to dump it into relation data by default [14:08] natefinch, those that need it can add it [14:08] natefinch, and personally I would prefer to expose it via $JUJU_AVAILABILITY_ZONE than by tacking it onto unit-get [14:09] natefinch, (and IMO we should not expose lists of zones at this stage -- I'm willing to hear proposals, but the ones I've seen have not been adequate ) [14:09] fwereade: agree on list of zones. There seemed to be no need for that. [14:10] fwereade: how about exposing zone of related units? I think that was in the proposal too, so you can see what zone your DB is in, for example. [14:10] natefinch, strong -1 to that [14:10] natefinch, zone-scoped relations would be kinda cool [14:11] natefinch, but they also bump up against the yuckiness of local-scoped non-subordinate relations [14:11] natefinch, ie they have exactly the same opaque failure modes [14:11] natefinch, and we should figure out how to do them *both* right [14:12] natefinch, *if* charms want to put that info over their relations, ofc we can't stop them [14:12] natefinch, exactly the same in peer rels and pro/req rels [14:12] natefinch, but I don't think it's something we want to make into a feature [14:12] fwereade: ok [14:13] fwereade: that sounds good. [14:15] fwereade: so the spec is now - simply expose zone via $JUJU_AVAILABILITY_ZONE and that's it? [14:15] natefinch, I think that's the MVP, yes ;) [14:16] fwereade: ok :) [14:24] natefinch, do you have a minute to review http://reviews.vapour.ws/r/650/ [14:25] sinzui: ship it! [14:25] thank you natefinch [14:33] wwitzel3: 1:1 in moonstone? [15:14] jw4: pong? [15:15] ericsnow: morning :) - Hey I've addressed all your issues on PR 616, with two issues asking for your agreement to drop in favor of a TODO : http://reviews.vapour.ws/r/616/ [15:15] ericsnow: care to take a quick gander and drop or object? [15:15] * ericsnow takes a look [15:22] jw4: thanks so much for addressing my concerns. [15:22] ericsnow: thanks for raising them :) [15:23] jw4: I'm fine with dropping the first one and while I'm not convinced on the second one I guess I'm okay with dropping it for now too [15:23] jw4: what's the concern with using IsolationSuite [15:24] jw4: it's not like the mongo suite or something :) [15:24] ericsnow: I think you make a good point in your comments. I was hesitant to pull in a big suite, but I think you're right - IsolationSuite is okay [15:25] ericsnow: I'll do that and clean up the pr and ping you again [15:25] jw4: yeah, if you look at the code, it doesn't add much but what it does add is super helpful [15:25] jw4: thanks! [15:25] ericsnow: thanks too [15:25] jw4: glad to do it [15:42] gah - I missed the window while CI isn't blocked - teh suk === ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: see calendar | Open critical bugs: 1403546 [15:53]