[03:08] huwshimi hey, everything working out ok? [03:09] huwshimi I have a question about pr #433 when you get back [03:11] hatch: Yep, all good [03:12] hatch: What's the question? [03:12] huwshimi so is there a reason why https://github.com/juju/juju-gui/pull/433/files#diff-e6baa739d19ae967f00d894884a065acR602 can't go in the addMachines loop? [03:28] huwshimi sorry server went down :) [03:29] np [03:29] so did that last message make it to you about putting that stuff in the addMachines loop? [03:30] nope [03:30] hatch [03:30] huwshimi so is there a reason why https://github.com/juju/juju-gui/pull/433/files#diff-e6baa739d19ae967f00d894884a065acR602 can't go in the addMachines loop? [03:32] hatch: oh, up in the case? [03:32] yeah [03:32] looks like it can be done in the same loop so you don't have to loop twice [03:32] I don't see why not [03:33] excellent [03:34] huwshimi and as for the line wrapping, it's fine for now but we should fire an email off to design because I bet _every_ time you change the constraints they will wrap [03:35] hatch: Yeah, I'm just not sure what the problem with the line wrapping is? [03:35] oh it just doesn't look very good heh [03:35] nothing else wraps [03:40] hatch: OK, just pushed that change [03:42] huwshimi thanks! +1'd but I can't QA it atm so...I'll have to take your word on it ;) [03:42] :) === uru-afk is now known as urulama [07:07] mornin' all [07:07] urulama: how're you doing today? [07:07] rogpeppe1: morning [07:07] rogpeppe1: better [07:07] urulama: good to hear! [07:08] urulama: is that "totally better" or "only just made it to work" better? [07:09] rogpeppe1: more of the second, but at least i am awake and am able to think :D [07:09] urulama: well that's something... [07:17] rogpeppe1: how was your diving? [07:17] urulama: not much diving, but some good plunges... [07:18] urulama: a great trip down Hell Gill [07:19] urulama: https://www.google.co.uk/search?q=hellgill&es_sm=93&tbm=isch&tbo=u&source=univ&sa=X&ei=mtXEU_nHL4ua1AWsKA&ved=0CC0Q7Ak&biw=1237&bih=600#imgdii=_ [07:20] rogpeppe1: niiiiice! [11:00] morning [13:52] bac: comingsoon seems to be pointing at a real env? [13:52] bac: it's asking for a user login, maybe it's just missing the sandbox config? [13:53] * bac looks [13:53] bac: oh hmm, getting a diff ip [13:54] 138 something? [13:54] bac: right [13:54] i get 138.91.155.196 [13:54] 138.91.155.196 for comingsoon [13:54] 138.91.154.88 for ci.jujugui.org [13:55] it's on that ci machine right? [13:56] comingsoon should be 138.91.154.88 [13:56] luca: so working on comingsoon, looks like a dns issue ^ sorry for the trouble [13:56] rick_h__: ah, it’s ok. Was just wondering if you has passworded it :) [13:57] luca: no more changing for you, locked out! :P [13:57] rick_h__: haha [13:57] rick_h__: if you want me to stop submitting bugs you have to only ask :P [13:57] luca: no, appreciate the eyeballs [13:58] bac: looking at the rt it's set to 138.91.155.196 per the request [13:58] bac: can you reopen or file a new rt please? [14:00] rick_h__: i see that. yes, i incorrectly pointed it at the GUI managing the cluster [14:12] rick_h__: comingsoon dns is corrected [14:14] bac: ty much [14:14] luca: ^ you should be able to access it again [14:14] rick_h__: cheers [14:18] hey rick_h__ [14:18] I just realized something that I used to consider an annoyance [14:19] but like, IMO should now be considered a workflow/usability buzzkill [14:19] waiting 15 minutes for my shiny new bundle to be indexed before I can share it with the world totally saps the enthusiasm [14:29] jujugui: can someone look at https://github.com/juju/juju-gui/pull/435 for me? [14:29] on it [14:30] hey bundle people: https://jujucharms.com/bundle/~jorge/hadoop-es/8/constraints/?text=hadoop-es#deploy [14:30] if I drop the 8 from the quickstart command, will that just deploy the latest version of the bundle? [14:31] jcastro: yes, it should [14:32] Makyo: your current work addresses bug 1340666, doens't it? [14:32] <_mup_> Bug #1340666: Clicking the destroy icon does not destroy the machine or container [14:35] luca: carla around? [14:35] rick_h__: on holiday today [14:35] luca: ok thanks [14:35] rick_h__: do you need anything in particular? [14:36] luca: yes, we agreed to add some description field to bundles [14:36] luca: and I can't find anything that notes if we kept the summary (one line) or description (couple of sentences) for it [14:36] luca thanks for the email, I forgot about THAT mockup.....(we have too many lol) [14:36] luca: and wanted to see if she knew and which sized content she was designing for [14:36] hatch: no worries :) [14:38] rick_h__: I’ll pass the message on, she’ll be back tomorrow [14:38] luca: ok ty [14:38] luca: I can send her an email then. Just wondered if she just wasn't on irc [14:38] rick_h__: ok :) [14:39] jcsackett review/qa done [14:39] hatch: thanks! [14:39] I think CI is broken on Makyo's branch [14:41] hatch: i concur. [14:50] hatch, jcsackett: what is the issue with CI? [14:50] bac it didn't pick it up [14:50] it said 'please test this' [14:50] did you manually kick it? [14:50] I'm wondering if Makyo used the wrong user account or something [14:51] you can manually kick it from GH? [14:51] hatch: no. via jenkins. [14:51] oh, no, but it's odd that it didn't pick it up on GH no? [14:52] yes, i guess. i haven't looked at the details [14:53] Was on the other computer, sorry. Yes, jcsackett. I only have one account, hatch. [14:54] Makyo odd, you don't have an icon anymore, thought it was a different account [14:54] hatch, I have an icon on my end. You running into gravatar problems? [14:56] Makyo: mostly he's musing at why jenkins seems to think your PR doesn't get auto tested. [14:56] Makyo: i'm going to throw your head on the card and assign that bug to you, if you have no objections. [14:56] Makyo GH doesn't use gravatar any longer apparently [14:56] Yeah, that's the second time I've gotten that, too. And yes, that's fine. [14:56] hatch, you have to set it as a separate setting. [14:56] Makyo: so, CI just has it in for you? :p [14:57] I have to set it to allow me to see your avatar? lol [14:57] hatch, No, sorry, you have to add a separate gravatar email. [14:57] https://avatars3.githubusercontent.com/u/303761?s=140 that is the address for your icon [14:57] hatch, jcsackett https://github.com/juju/juju-gui/pull/416 rick_h__ did :ok test:, is this a setting? [14:57] not gravatar [14:57] Makyo: so do you want me to kick off a jenkins build for 0c9371c35e [14:58] bac, sure [15:00] oops, jujugui call now [15:00] Makyo: & [15:00] :) [15:00] Makyo: ^ [15:00] heh next key over [15:11] http://www.meetup.com/London-React-User-Group/events/191406572/ and http://www.meetup.com/swiftly/events/192370642/ [15:11] I'm not sure I'll be attending any - just thought i'd bring it up [15:11] they are both fairly close [15:11] couple tube stops away [15:12] jujugui: my wifi died just as I was joining standup. Currently using my cellphone as a hotspot, but I don't get great coverage in my house. Restarted the router twice and still can't see wifi so not sure when I'll have dependable internet again. [15:12] kadams54 are you using a 2Wire router? Thats what our isp provides and it's junk [15:12] lol [15:18] rick_h__ watch should arrive today......it's on the truck! [15:20] hatch: woot! [15:20] got in trouble with my wife about it :P [15:20] lol - that's how you know it's a good purchase! [15:20] with my luck mine won't even work [15:21] hahaha [15:24] battery dead [15:24] must charge for 8hrs before you can use it :P [15:32] lol son-of-a [15:40] rick_h__: a bit of googling solved it [15:41] rick_h__: jeeze google don't make intuitive UIs these days [15:41] Makyo: so the build for your branch failed on jenkins, but since it was started manually didn't report back to github. http://ci.jujugui.org:8080/job/juju-gui/1417/console [15:43] lint failure [15:43] rogpeppe1: ah awesome! [15:43] rogpeppe1: I've given up and just make sure I create the doc from the folder. I fail at moving it [15:44] rick_h__: i added the folder to my drive, then dragged the doc from to the folder [15:45] rick_h__: i guess you can't add stuff to folders unless they're in "My Drive". [15:45] rogpeppe1: oh, interesting [15:49] luca: ping got a sec before your EOD? [15:49] rick_h__: hey, yes I do [15:49] can you jump in the standout hangout? [15:49] omw [16:10] * rick_h__ goes to get lunch [16:23] luca: i'm working on bug 1339779, and it seems a bit odd as listed. do you just want containers to not be shown if the machine they're on has also just been created? b/c i figure we should show something in the deploy confirmation if your just creating a container on a machine that already exists. [16:23] <_mup_> Bug #1339779: Containers that are created in MV should not be shown as part of the "Machines created" section in the deployment summary [16:24] also: you only reference the deploy confirmation--do you also mean the regular summary? [16:25] jcsackett: if your just creating a container thats a minor change which incurs no extra cost so it should be part of the deployment summary [16:26] luca: ok, so just hide it from the summary if the machine it's on is also being created. [16:26] jcsackett: creating a container doesn’t constitute a new machine either so the “Container created” message shouldn’t be populated within the “Machines created” summary section. [16:27] jcsackett: well, it should be hidden regardless if the machine is new or old [16:27] luca: so, you want a new "Containers added" section as well--in that case rather than not showing the container when the machine is created shouldn't we just put in the container section? [16:27] jcsackett: no, I think I’m confusing issues with the wording of the bug. [16:27] luca: i'm certainly confused. :p [16:27] jcsackett: I don’t want to show that containers have been created at all in the deployment summary [16:28] jcsackett: the only place it should be visible is in the complete change log [16:28] jcsackett: sorry! [16:28] luca: ok. [16:28] one usability thing then--if i create a container, i either a) have created something, but see no indication that i can commit that change, or b) see i can commit the change, but when i get a confirmation there's nothing there. [16:30] jcsackett: well, for a) you’ll see a single change in the change log if you open the curtain. b) if there are no big changes made to populate the summary the full change log should be open by deafult. [16:31] luca: ah, ok. [16:32] luca: so if i just create a container, when i go to deploy we'll open the changelog rather than displaying the summary thing. [16:32] that makes more sense. [16:32] jcsackett: yeah, though I’m not sure that was ever built in. [16:32] luca: i dn't believe that behavior exists yet, no. [16:32] but i think it's in scope for this branch. [16:33] jcsackett: ok, cool [16:33] luca: thanks for the clarification. :) [16:33] jcsackett: no worries, I’m happy to help :) [16:37] interesting perf results .apply() .bind() .call() http://jsperf.com/function-calls-direct-vs-apply-vs-call-vs-bind/40 [16:49] 2-more-tests [16:59] bac: can you peek at https://bugs.launchpad.net/bugs/1311321 and help post a verification so they can move forward with 1.3.2 into trusty? [16:59] <_mup_> Bug #1311321: ascii can't decode error in 14.04 server install

[17:02] tvansteenburgh: I see your recent MP go by. We'd love to make sure you take a peek at the charmstore api doc emailed out to make sure the api there will help all your needs . [17:02] rick_h__: cool, is this email already sent? [17:03] tvansteenburgh: yes, it was sent to juju-dev [17:03] rick_h__: k, will take a look, thanks [17:04] tvansteenburgh: we've got a few specs you and your team might be interested in, /me goes for the link [17:05] tvansteenburgh: https://docs.google.com/a/canonical.com/document/d/1TgRA7jW_mmXoKH3JiwBbtPvQu7WiM6XMrz1wSrhTMXw/edit [17:05] rick_h__: thanks [17:22] * rick_h__ moves to the coffee shop [17:25] does anyone know how I remove a file from a series of commits? [17:26] computer crashed, just like that. luckily i'd saved my recent changes, phew. [17:26] a good sign i should stop though. [17:26] g'night all [17:26] rogpeppe you should use a real editor :P night [17:27] hatch: actually, i've been meaning to make acme do a periodic dump for ages. [17:27] hatch: it already supports dumping the whole state of the editor - but just manually. [17:27] (or if the editor is killed) [17:27] kernels shouldn't crash just like that [17:27] sublime does some auto-save-to-temp, so anytime it crashes or whatever the changes are always there but not reflected in the original unless saved [17:28] heh nope they shouldn't [17:28] rick_h__: so juju-quickstart SRU landed in trusty-proposed. We need to get these bugs verified from the binaries in trusty-proposed itself now. [17:28] once upon a time they'd at least produce a panic message so you had *some* idea what the problem might be [17:28] rick_h__: I know you had some ongoing CI efforts going. I wonder if you could run the same CI against trusty-proposed as an easy way to automate this verification? [17:28] but this has happened a few times to me - the whole thing just switches off and on again [17:30] darn, i have lost more stuff than i thought. [17:34] jujugui I need a review and qa for the new scale-up UI branch https://github.com/juju/juju-gui/pull/437 plz and thanks [17:34] hatch: I can take a look [17:34] rogpeppe :-( [17:34] kadams54_ thanks [17:44] rbasak: thanks for the heads up. We'll work on getting that QA'd. [17:44] rbasak: the CI efforts aren't ready currently, we'll manually QA. I'm not sure how we'd automate off the proposed package. That's an interesting idea to look into. [17:45] we normally do things off the source [17:47] damn glossy laptop screens, outdoor fail [17:47] haha, just sit facing the sun :) [17:47] I'm in the shade but like I'm trying tinto a mirror [17:47] typing that is [17:48] hmm odd mine isnt like that [17:48] is this your new dell? [17:49] "Dude you got a Dell!" [17:49] hatch: yea, stupid thing [17:52] hatch: you on the test failures for your branch? [17:53] rick_h__ yeah, iunno wth is going on [17:54] looks like the third manually triggered run is still going [17:54] * hatch crosses fingers [17:54] hatch: :/ it seemed to be a legit test there [17:55] yeah I know, but I can't reproduce that failure locally running prod/debug on phantom or chrome [17:59] rick_h__: OK - thanks! [17:59] rbasak: thank you [18:00] rick_h__: oh, wait. Note that the juju-core SRU still needs further review. You might be broken until that goes from 1.18.1 to 1.18.4. [18:00] bah, and rain clouds on the way. Curse you mother nature for giving me a great day but not able to enjoy it. [18:00] (if you need that - I forget) [18:00] watch hath arrived [18:00] rbasak: no, I think our update was only tied because of 1.18.1? We're actually tied to 1.18.0 as far as our release goes [18:01] it was a response to bugs presented by the 1.18.0 release [18:01] rick_h__: OK - it might not actually be broken then. [18:01] In any case, if it is, it's fine to wait until it lands. [18:01] * rbasak needs to run [18:07] looks like the test failure is legit....now to figure out why... and why I can't reproduce it locally [18:08] kadams54_ I'm not sure I understand your qa issue [18:08] hatch: which one? [18:08] the first one [18:08] you can't place two units on bare-metal [18:09] Doesn't mean people won't try :-) [18:09] sure - but that's not related to this branch [18:09] Right now we allow it and it gets everything into a funky state [18:09] Maybe a new bug then? [18:09] I'll try a qa doing that on a container and see what happens [18:11] rick_h__: i found the charmworld ngram search error and will be finishing up shortly [18:11] kadams54_ can you elaborate with a step-by-step on point 1? I can't reproduce it [18:12] bac: awesome, thanks for that [18:12] hatch: on a container or on the bare metal? I just tried on a container and I still get stuck with one change that just won't commit… [18:12] kadams54_ yeah I need step-by-step because it's working perfect here [18:12] hatch: also doing a clean build right now to make sure it's not something on my end. [18:14] hatch: How about a screenshare? [18:14] hatch: still seeing problems after a clean build. [18:15] yeah sure [18:15] standup room? [18:15] ok in [18:15] k [18:18] rick_h__ u got a sec? [18:18] join the standup room? [18:18] hatch: loading [18:27] I'm going to step away for some lunch, when I return I'll track down that CI issue with my branch. [18:35] hatch: still running into a JS error, even with one unit per container. Ping me when you're back from lunch. [19:05] ping https://github.com/juju/charm/pull/17 [19:06] jrwren: so normally just ping that with the jujugui highlight [19:06] jrwren: and please make sure your irc client is setup to highlight on jujugui [19:06] Makyo: you up for a tiny Go review? ^ [19:06] So many jujugui pings… [19:06] Sure [19:06] kadams54_: just for you :P [19:06] :-) [19:06] and then try not to ping too much on jujugui if hatch is anywhere near you, as his sound effect is annoying. :p [19:07] lol [19:07] Good things to know before next week [19:07] jcsackett: i think we're at a safe distance atm [19:07] jcsackett: and you know he only turns that on when you're around [19:08] for his own sanity, i should hope so. [19:08] highligh jujugui like this? :p [19:08] jrwren: :) [19:08] Yup, now all jujugui knows. [19:08] jrwren: you should work out just fine in this group. :p [19:09] i may have done that wrong. jujugui like this. [19:09] * kadams54_ giggles. [19:09] i really want to keep going, but I shall practice restraint. [19:15] what is the process now? do /I/ go merge the pull req? [19:15] jrwren: for now just hit the merge button [19:15] jrwren: there's work to pull that into a CI system with juju-core and other deps and eventually it'll hopefully be part of a CI process [19:16] oh, i don't have write access [19:16] jrwren: oh hmm, /me checks perms [19:17] jrwren: added you to juju org, make sure to go to https://github.com/orgs/juju/members and mark your membership as public please [19:18] done [19:18] push the green button [19:18] jrwren: cool then mark the card as done by moving to daily call [19:19] jrwren: and I think you can move forward with the description card now. I don't think if we have a summary (1 sentence) or longer it matters to the source. [19:20] ok [19:44] jujugui: https://github.com/juju/charm/pull/19 [19:46] kadams54_ back [19:49] kadams54_ I'll need you to put the exact step-by-step instructions in the PR as I cannot reproduce any errors [19:52] jujugui anyone have a free moment to run some tests locally for me to see if they fail? [19:54] maybe? [19:54] hatch: what tests? [19:54] the gui's make test-prod and test-debug tests [19:54] do you have phantomjs and whatnot installed? [19:56] jrwren actually you can forget it I figured out a way to make it fail locally [19:56] thanks though [19:56] jcsackett, rick_h__: could either of you review and QA my charmworld branch? https://codereview.appspot.com/117810044 [20:06] jujugui the :checked psudo selector does NOT work in phantomjs..... [20:06] 'input[name="placement"]:checked' [20:06] jrwren: i looked at your branch and made some trivial suggestions. i think we're deferring to rogpeppe and frankban for final approvals. [20:06] ugh [20:08] thanks for catching typos. Pretty lazy on my part. [20:09] hatch: yeah, that also bit me awhile back. [20:10] what a piss-off [20:10] lol [20:10] bac: I've hit EOD and have to run to swim class. Let me know if jcsackett isn't available and I can qa it in the morning [20:11] rick_h__: happy swimming [20:11] heh, 4ry old almost drowing ftw [20:11] drowning [20:13] lol - he'll learn :) [20:18] hatch: added steps to the PR. Let me know what happens. [20:18] thanks, checking [20:21] kadams54_ ok I can reproduce what you're seeing now - lemme take a look to see where the issue is [20:23] i'm done for day, but i'm taking the kid to gymnastics and working more from there :) [20:28] kadams54_ very odd bug....nice catch, this might be a bigger issue, I'll see if I can do a driveby [20:29] Yay? ;-) [20:29] lol [20:29] better we found this now that in 2 weeks [20:30] jujugui: anyone want to do a charmworld review and QA? changes are pretty straightforward. https://codereview.appspot.com/117810044 [20:31] bac I don't have charmworld set up but I can after I get mine landed [20:31] will likely be a while heh sorry [20:34] hatch: no prob [20:35] jujugui ^ if anyone wants to take this review/qa before me feel free to do so [20:35] hatch, bac on it. [20:35] thanks Makyo [20:35] ty Makyo [20:38] kadams54_ this is fixable...fixing [20:39] :) just keeping you posted I guess heh [20:39] :-) [20:39] Thanks [20:39] How's the fixing going? [20:39] 10% 25% 76% done? [20:39] good - I !@#$%^&* it up [20:39] :P [20:39] lol [20:39] LOL [20:39] Well that didn't take long [20:39] just giving credit where credit is due ya know... [20:42] kadams54_ and fixed....aww yeah [20:42] Sweet… [20:42] kadams54_ heh I had this like this before and must have removed it by accident or something https://gist.github.com/577c30b5dc9fec36b895 [20:43] oops [20:43] My honor to break it then :-) [20:43] haha [20:44] linting, running tests then will be good for another qa [20:44] when is your EOD? [20:49] kadams54_ ok ready to go for another QA [21:06] Makyo: i'm going to take the dog out. will be back later. [21:09] bac, can't log into RV to say so, but LGTM, QA okay [21:20] oh darn he left [21:20] jujugui anyone able to do another review/qa on https://github.com/juju/juju-gui/pull/437 ? [21:22] rick_h__ do you know if you can send hangout messages from this watch? It seems to only support sms [21:27] hatch: I use hangouts as my sms app so not sure. [21:27] when I send it uses hangouts and not sure what it ends up doing [21:27] yeah it seems to only send via SMS not hangouts [21:27] well hangouts app [21:27] bit sms [21:27] but* [21:27] kind of odd [21:28] hatch: ping me via hangouts and I'll see if I can reply :P [21:28] to mitechie not canonical [21:28] oh I don't have it [21:28] my wife stole it [21:28] lol [21:30] lol [21:31] so....I may not have a watch anymore? [21:31] haha [21:31] guess time will tell [21:32] needed a watch strap with a lock on it :) [21:32] though I suppose losing a watch > losing an arm [21:32] haha - it's unfortunate it doesn't have a speaker [21:32] would be nice to answer calls on it [21:32] no, no it would not [21:32] go get that samsung thing with that stuff if you want that [21:32] the samsung one has a speaker? [21:53] Makyo: would you mind adding your approval and comments to the MP in launchpad? https://code.launchpad.net/~bac/charmworld/ngram-inquiry/+merge/226910 [21:53] Makyo: and thanks for looking at it. [22:07] Makyo I think there is something wrong with your GH account - your new branch isn't being tested either [22:08] hatch, the only variable I can think of is whether or not my membership is public. Will make sure. [22:08] I still don't get any photo for you, but I do for everyone else [22:08] I get a photo for myself on all devices. [22:09] weird [22:10] Makyo: why does CI hate you and not want to test your branches? [22:11] rick_h__ do you see an avatar for him on GH? [22:11] the drinking dog? [22:11] It's an arctic fox dressed in a victorian suit with a gin and tonic, I'll have you know. [22:11] I see a grey octopus [22:12] Makyo: oh, well in that case :P [22:12] Hahaha [22:12] lol!!] [22:12] It was leftover from gravatar, which I see has been removed. [22:12] oh so I was right? They did remove gravatar support? [22:13] I remembered reading something about that, but wasn't sure if I remembered right [22:13]