[00:05] <hatch> huwshimi so besides the var things code review ok?
[00:06] <huwshimi> hatch: I don't really know. I mean there's code there, it does some stuff. I'm not sure I know enough to be reviewing branches like this.
[00:07] <hatch> ahh ok
[00:08] <hatch> huwshimi can you respond with QA OK and then I'll land it, if there are some code issues that others don't like we can fix them in a follow-up
[00:09] <hatch> I just don't want to get held up as there are more changes to be made in this section
[00:12] <huwshimi> hatch: Left a note
[00:12] <hatch> lol, nice passive agressive comment
[00:12] <hatch> if you would like you could fire an email off to design :)
[00:14] <huwshimi> hatch: I'm not sure about landing this without a proper code review though. I can't see if Kyle did one either
[00:15] <rick_h__> huwshimi: hatch what do you need?
[00:15] <rick_h__> hatch: I can do one in the morning before you start if required
[00:15] <hatch> huwshimi ok that's fine if you're not comfortable
[00:15] <rick_h__> no calls until 10 yay!
[00:16] <hatch> rick_h__ that would be awesome thanks
[00:16] <rick_h__> hatch: ok, I've got it on my morning todo. 
[00:16] <rick_h__> too shut down to look right now sorry
[00:16] <rick_h__> thanks for looking huw
[00:17] <hatch> np it's well past EOD :) 
[00:17] <hatch> rick_h__ https://github.com/juju/juju-gui/pull/437 then https://github.com/juju/juju-gui/pull/439 is branched from it
[00:17] <rick_h__> hatch: rgr
[00:18] <hatch> and now I'm also done :)
[00:18] <rick_h__> night hatch 
[00:18] <hatch> night rick_h__ huwshimi 
[00:18] <rick_h__> go find your watch :P
[00:18] <hatch> lol
[00:18] <hatch> right!
[08:00] <rogpeppe> urulama: morning!
[08:11] <urulama> rogpeppe: morning
[08:11] <rogpeppe> urulama: how're you feeling today?
[08:12] <urulama> rogpeppe: better, at least i feel hungry now :D 
[08:12] <rogpeppe> urulama: always a good sign...
[08:12] <rogpeppe> urulama: do you fancy pairing on moving the charm store apiHandler stuff forward?
[08:13] <urulama> sure. give me 10min to grab something to eat
[08:13] <rogpeppe> urulama: np
[08:42] <urulama> rogpeppe: sorry, that breakfast didn't land well :S
[08:43] <rogpeppe> urulama: oh dear :-\
[08:43] <urulama> rogpeppe: yeah, fats to soon ... nevermind, it'll pass ... 
[08:43] <urulama> rogpeppe: gogogo?
[08:43] <rogpeppe> urulama: if you'd prefer to go back to bed, or not interact much, that's fine
[08:43] <rogpeppe> urulama: yup, i'm there
[10:44]  * urulama lunches
[11:27] <rick_h__> morning all
[11:27] <rick_h__> rogpeppe: have you followed the license thread?
[11:27] <rogpeppe> rick_h__: i have
[11:27] <rogpeppe> rick_h__: (g'morning, BTW)
[11:27] <rick_h__> rogpeppe: can you please make sure all our repos, charmstore, charm, etc are ok on that front please?
[11:28] <rick_h__> rogpeppe: it looked like the agreement was lgpl with exception?
[11:28] <rick_h__> for outside libs
[11:28] <rogpeppe> rick_h__: yes
[11:28] <rogpeppe> rick_h__: charmstore is fine
[11:28] <rogpeppe> rick_h__: charm should probably be LGPL but is currently AGPL
[11:29] <rick_h__> ah, since it was pulled from core which is agpl?
[11:30] <rogpeppe> rick_h__: yes
[11:30] <rogpeppe> rick_h__: but it could easily be changed to LGPL
[11:30] <rick_h__> ok
[11:30] <rogpeppe> rick_h__: (with a possible caveat of whether LGPL is compatible with the apache 2 license)
[12:03] <rick_h__> moving to the coffee shop, biab
[12:06] <bac> hola
[12:20] <rick_h__> morning bac 
[12:22] <bac> how was swim lessons?  i remember enjoying them until they tried to make us go off the high dive.  didn't go back.
[12:23] <rick_h__> heh, due to scheduling fun we had to go private lessons this round and the boy is loving the personal attention
[12:24] <rick_h__> show off "I can swim under water" and he just throws himself into the lake
[12:24] <rick_h__> then comes up with half the lake being swallowed 
[12:24] <rick_h__> but it's fun, hard to not get eager for him to do real swimming so we can trust him to be more indenpendent at water parks/etc
[12:26] <urulama> i need to change place, "feels" too crowdy at home today :D
[12:27] <rick_h__> urulama: yea, coffee shops ftw
[12:28] <urulama> rick_h__: i actually have access to place with net and everything on the other side of town, near woods and more important, no kids singing and dancing around :D
[12:29] <rick_h__> urulama: sounds like a winner
[13:01] <jrwren> morning.
[13:01] <rick_h__> morning jrwren 
[13:53] <rick_h__> hatch: sorry, I'm behind on your reviews. Been a busy morning
[13:53] <rick_h__> hatch: looking now and will try to get done asap
[13:53] <hatch> np thx
[14:12] <rick_h__> hatch: one round of comments in 
[14:13] <hatch> thx will check
[14:13] <rick_h__> hatch: going to wait on the second one until the diff is one vs both
[14:15] <hatch> ok I'm going to have to fix the markup to enable enter submissions as it uses multiple form elements
[14:15] <hatch> atm you can submit the constraints form, the unit count form, etc which doesn't make any sense
[14:16] <rick_h__> hatch: ah, yea that's ungood. To the user it's all the same form
[14:17] <hatch> I'm guessing huw did that on purpose so I wonder what surprises await me in doing that
[14:17]  * rick_h__ heads back home, coffee shop is getting crowded. 
[14:17] <rick_h__> hatch: heh, well that's fine to do it as a follow up
[14:17] <rick_h__> hatch: but your current branch can land without the block
[14:17] <hatch> without the block?
[14:17] <rick_h__> hatch: but take a stab at it, if you end up in css hell, create a card and punt it
[14:18] <rick_h__> without the block on the enter key
[14:18] <rick_h__> saying "if you use the enter key it doesn't work predictably" is a follow on bug/card
[14:18] <hatch> well not really - they can submit the constraints form
[14:18] <hatch> so it falls apart if they hit enter on that
[14:18] <hatch> I'll take a stab, see where it ends up
[14:32] <bac> hi abentley
[14:32] <abentley> bac: otp
[14:33] <bac> abentley: ok, please ping me when you have a few minutes free
[14:55] <hatch> jujugui call in 5
[14:58] <rick_h__> jujugui call in 1 and go
[14:59] <rick_h__> or now ish
[14:59] <rogpeppe> jujugui: hmm, i'm getting "Couldn't start the video call because of an error"
[14:59] <urulama> rick_h__: same here
[14:59] <rick_h__> rogpeppe: urulama another browser?
[15:00] <rick_h__> kadams54: ^
[15:00] <rogpeppe> i'll try incognito
[15:00] <rick_h__> bac: ^
[15:01] <bac> trying
[15:03] <rogpeppe> that didn't work
[15:03] <urulama> me neither
[15:03] <rogpeppe> unfortunately i don't have another browser installed currently
[15:03] <urulama> tried firefox and chrome
[15:03] <urulama> (and safari /me runs away)
[15:04] <rogpeppe> urulama: our previous session seems to have tainted both of us...
[15:04] <urulama> i get the "due to the number of participants ..." error
[15:04] <rogpeppe> i don't get that
[15:04] <rogpeppe> it lets me in (apparently) and then gives me the error
[15:05] <rogpeppe> jujugui: sorry guys
[15:05] <urulama> yes, same here ... see who is there but not able to join :(
[15:06] <rick_h__> sounds like it hates EU folks :/
[15:06] <rick_h__> everyone else is here
[15:06] <rogpeppe> rick_h__: for the record, the "store: start version api responses" card is making good progress. urulama and i should have something to show very soon
[15:07] <rogpeppe> urulama: can you still join gogogo?
[15:07] <urulama> rogpeppe: yes
[15:07] <urulama> rogpeppe: no
[15:07] <urulama> :S
[15:07] <rogpeppe> urulama: i thought it was working for me too...
[15:07] <rogpeppe> urulama: and then not
[15:07] <rogpeppe> urulama: bugger
[15:08] <urulama> rogpeppe: maybe google blocked us due to the usage today :D :D
[15:08] <rogpeppe> urulama: hmm
[15:09] <urulama> rogpeppe: let's give it 10min and retry
[15:09] <rogpeppe> urulama: yeah
[15:11] <rick_h__> rogpeppe: urulama k, reported. Nothing big from the team. I've got a vet appt and will be afk some this afternoon, but that's post your EOD so no worried on your end
[15:12] <jcsackett> rick_h__: re the tagging notion--are we going to be on the hook to do that as proper tagging? e.g. a charm can have multiple tags, and a search should be able to do multiple tags?
[15:12] <jrwren> In go, I know we follow gofmt. do we have style guidelines beyond that?  e.g. prefer multiline string to string with embedded \n after a certain number of newlines?
[15:13] <jcsackett> jrwren: in python, flake8 is your style bible.
[15:13] <jrwren> yes, I flake8 in python.
[15:13] <jcsackett> that's about it, afaik.
[15:13] <jrwren> ok.
[15:13] <jcsackett> and for js in the gui, i have no idea what our style rules are--i just fix what the linter screams at me about. :P
[15:14] <jcsackett> seems to be working so far. :P
[15:15] <rick_h__> jrwren: there's a pull request in juju core for style guide
[15:15] <rick_h__> jrwren: take a peek and see if you can find it in current or recently closed pull requests in /juju/juju
[15:15] <rick_h__> jcsackett: it'll be just like categories now, a list of string. And yes, we'll index those and allow searching on that filter
[15:15] <jcsackett> rick_h__: cool.
[15:15] <urulama> rick_h__: ok, good luck at the vet, maybe see you later
[15:16] <rick_h__> urulama: sure thing, I think we should chat in a bit. just cathing up
[15:16] <urulama> rick_h__: ok, ping when you come back, otherwise, first thing in the morning?
[15:17] <rick_h__> urulama: yep
[15:18] <rick_h__> jrwren: https://github.com/juju/juju/tree/master/doc/contribution
[15:18] <jrwren> thanks rick_h__ 
[15:19] <rick_h__> np, it's a WIP but something we should get familiar with and support across projects. rogpeppe urulama ^ as well
[15:19] <rick_h__> bac: Makyo ^
[15:19] <urulama> rick_h__: checking
[15:20] <rogpeppe> jrwren: also, this is well worth reading: https://code.google.com/p/go-wiki/wiki/CodeReviewComments
[15:21] <rogpeppe> jrwren: and in general, the go stdlib is very well written and idomatically designed - if it does something a particular way, it's usually a good way to do it
[15:22] <jrwren> Great to know.
[15:22] <rogpeppe> jrwren: there's also this: https://github.com/golang/lint
[15:23]  * urulama brb
[15:23] <jrwren> oooh, golint, lots of messages. I like it.
[15:24] <bac> rick_h__: got a sec? http://162.213.35.28:8080/job/charmworld-autoland/165/console  -- search for "Selec+" ... it seems the console output abruptly halted, not capturing the actual problem
[15:24] <bac> not a one off
[15:24] <rick_h__> bac: looking
[15:26] <rick_h__> bac: hmm, yea. It was still installing deps and then failed. Mabye a netork issue?
[15:27] <bac> perhaps.  i'll look to see if it failed at the same point previously
[15:27] <rick_h__> network, the jenkins-launchpad-plugin? Maybe a missing dep?
[15:27] <rick_h__> from the download cache?
[15:27] <rick_h__> bac: I'd look at a normal fresh run and see what package it's grabbing after the python-lazr and see if something is up with fetching it?
[15:27] <bac> ok
[15:31] <urulama> rogpeppe: still no gogogog :(
[15:31] <rick_h__> urulama: rogpeppe I'm going to setup a call for the morning. Hopefully the hangouts issues work out by then
[15:31] <urulama> rick_h__: ok
[15:31] <hatch> rick_h__ moving that form stuff is causing issues, I'll land my two branches then do it as a follow-up right away, will be muuuch easier when I don't have to worry about conflicts from my next branch
[15:31] <rogpeppe> urulama: yeah, i'm still having the same problems
[15:31] <rick_h__> hatch: rgr
[15:33] <rogpeppe> urulama: this is what splitId is looking like now, BTW: http://paste.ubuntu.com/7803979/
[15:34] <urulama> rogpeppe: ok, this is muuuch better then the clutter before :D
[15:35] <urulama> rogpeppe: but we do "parse" it twice, right (with the Charm.parse) call?
[15:36] <rogpeppe> urulama: sure. but the first parsing is very lightweight. i doubt it'll take more than a small number of ns
[15:37] <hatch> rick_h__ ok while these things land I'm just going to pick off another bug card from the pile
[15:38] <rick_h__> hatch: rgr
[15:39]  * rick_h__ goes to get some lunch
[15:39] <urulama> rogpeppe: yes, i was just thinking in a way, that this splitId could be part of Charm, so that it is always in sync to all
[15:39] <rogpeppe> urulama: that's a good idea
[15:40] <rogpeppe> urulama: i guess you'd probably want to make the knownSeries an argument to it then
[15:41] <urulama> rogpeppe: that part i don't like :D (but have no alternative atm)
[15:41] <urulama> (as agreed before)
[15:41] <rogpeppe> urulama: yeah, i'm not keen either. i'm tempted to just leave this logic in the charm store for the time being, as we don't really want other people doing the same thing
[15:41] <urulama> rogpeppe: +1
[15:42] <rogpeppe> urulama: after all, we do double-check that the final URL parses ok
[15:42] <rogpeppe> urulama: so if charm urls change, then our tests will break immediately
[15:56] <jrwren> rogpeppe: https://github.com/juju/charm/pull/19 look good?
[15:57] <rogpeppe> jrwren: LGTM
[15:57] <jrwren> ty.
[15:57] <jrwren> now I can bug rick_h__ for moar! :)
[15:58] <rick_h__> ruh roh
[15:58]  * rick_h__ pulls up the board of work item doom
[16:00] <rick_h__> jrwren: side task, can you git pull origin develop from the ci slave machine in the /var/lib/jenkins/jenkins-github-lander directory?
[16:01] <jrwren> oh, to get changes there?  sure.
[16:01] <rick_h__> jrwren: yea, catch it up to latest src
[16:09] <jrwren> I can't status the ci-environment :(    http://pastebin.ubuntu.com/7804136/
[16:10] <rick_h__> jrwren: there's been a bug going around on that, /me looks
[16:11] <rick_h__> jrwren: https://bugs.launchpad.net/juju-core/+bug/1307434
[16:11] <_mup_> Bug #1307434: talking to mongo can fail with "TCP i/o timeout" <cloud-installer> <landscape> <performance> <reliability> <juju-core:In Progress by mfoord> <https://launchpad.net/bugs/1307434>
[16:11] <rick_h__> restarting the state server seems to have helped? 
[16:12] <rick_h__> jrwren: marked as in progress
[16:12] <rick_h__> jrwren: did you get access to azure? 
[16:12] <rick_h__> jrwren: or need me to do the bouncing?
[16:12] <jrwren> i don't have access to the web portal. I could probably use azure cmdline tools to do it.
[16:12] <jrwren> that might be a good exercise for me :)
[16:14] <rick_h__> jrwren: will reboot it here, one sec
[16:16] <rick_h__> jrwren: give it a shot?
[16:17] <jrwren> thanks.
[16:19] <hatch> thanks to all the hard work jcsackett  put into the changes in rendering the inspector my current branch is super trivial to implement :) yay jcsackett 
[16:19] <rick_h__> woot yay jcsackett :)
[16:20] <jrwren> rick_h__: just trusty-slave or other slaves too?
[16:20] <rick_h__> jrwren: I can't recall which I updated, please check all three
[16:20] <rick_h__> jenkins machines
[16:22] <hatch> rick_h__ hey I just wanted to point this bug out that my branch will create - I'm not sure what priority you want to put it at https://bugs.launchpad.net/juju-gui/+bug/1342809
[16:22] <_mup_> Bug #1342809: Inspector tabs should route the url <juju-gui:New> <https://launchpad.net/bugs/1342809>
[16:23] <rick_h__> hatch: they can't route because it's too hard to figure out inspector tab vs details/browser tabs
[16:23] <rick_h__> hatch: and we've prioritized the charm details over inspector tabs
[16:24] <hatch> I'm not sure I understand, I don't see why they both can't work? 
[16:25] <hatch> http://192.168.33.10:8888/inspector/wordpress/charm/tab/relations/:flags:/mv/ seems to work just fine
[16:27] <hatch> oh I see a bug in it... showTab() closes the breakout
[16:27] <hatch> so you can't have a tab navigate and the breakout visible
[16:28] <hatch> I'm pretty sure that's the viewlet slot issue and not a routing issue though
[16:30] <bac> rick_h__: the jenkins issues was due to it running out of disk while doing an install inside the lxc, so the error message got swallowed.  cleaned up some old lxc directories and trying again.
[16:30] <bac> s/issues/issue/
[16:30] <rick_h__> bac: ah!
[16:31] <rick_h__> hatch: looking, sorry. in my head tabs in the inspector would be just like the browser as #tabname
[16:31] <rick_h__> and so we have two namespaces living in the one propery
[16:32] <rick_h__> hatch: but it looks like I'm mistaken and the inspector tab is part of the root url?
[16:32] <hatch> it is now :) 
[16:32] <rick_h__> hatch: hangout?
[16:32] <hatch> sure
[16:32] <hatch> trying to join the standup one
[16:49] <hatch> rick_h__ does your watch disconnect from the phone a lot? This one dc's like every hour then you have to turn the phone on and hit the button to reconnect 
[16:50] <rick_h__> hatch: no, it's been really good
[16:50] <rick_h__> hatch: does your phone do BT LE, 4.0 I think?
[16:50] <hatch> yep, running the latest android and everything - all power saving options turned off
[16:50] <hatch> I can't even find anyone complaining online so this might be an isolated incident 
[17:02] <hatch> rick_h__ https://github.com/juju/juju-gui/pull/439 is ready for review - sidenote: I had to pull it down and rebase develop into it to remove the old commits, I kind of assumed the Pr would do that automatically
[17:04] <rick_h__> hatch: rgr, loading
[17:07] <urulama> jujugui night all
[17:07] <rick_h__> urulama: have a good evening
[17:15] <rick_h__> hatch: can I ask you about non machine view uses?
[17:15] <hatch> pourquoi?
[17:15] <rick_h__> qa without :flags:/mv
[17:16] <hatch> oh...
[17:16] <hatch> hmm
[17:16] <rick_h__> it seems to be wanting a bit now
[17:16] <hatch> heh
[17:16] <hatch> ok I guess my removal branch can't land?
[17:16] <rick_h__> not at this time. 
[17:17] <hatch> hmm
[17:17] <rick_h__> it can make sure you only get the new UX in MV, but without the flag is still important for 3wks
[17:17] <rick_h__> well, 2 we'll call it
[17:18] <hatch> hmm ok I think I can use those new flag css classes to hide it with mv
[17:18] <hatch> I'll leave this branch for reference, close the PR, and create a new one to hide the old stuff under mv
[17:18] <rick_h__> hatch: k, so I this branch will be a bit diff to land
[17:18] <rick_h__> hatch: ok, sounds good thanks
[17:18] <rick_h__> sorry for the blockage there :/
[17:19] <hatch> s'ok there will be some conflicts in the future but the majority of the code will still be usable so definitely want to keep it around
[17:19] <rick_h__> k
[17:20] <rick_h__> jujugui, just a reminder to QA both with and without the feature flag.
[17:30] <hatch> rick_h__ can you comment about the non mv stuff on #439 PR?
[17:43] <hatch> jujugui looking for a quick review/qa on https://github.com/juju/juju-gui/pull/440
[17:43] <kadams54> hatch: checking
[17:43] <hatch> th
[17:43] <hatch> x
[17:44] <kadams54> welcom
[17:44] <kadams54> e
[17:47] <hatch> :
[17:47] <hatch> P
[17:53] <hatch> LOL airbnb's new logo
[17:53] <hatch> clearly they didn't run that one past the internet lewd machine first
[17:58] <hatch> arosales hey did you see the ghost charm is now promulgated?
[18:29] <hatch> jujugui looking for a review/qa on https://github.com/juju/juju-gui/pull/441
[18:29] <hatch> really trivial css change
[18:30] <hatch> kadams54 did you get lost on #440? The diff isn't that big ;)
[18:33] <kadams54> hatch: sorry, had an important phone call come in.
[18:34] <hatch> those are the worst - getting in the way of the daily activities 
[18:35] <kadams54> hatch: all done with review and QA.
[18:35] <hatch> thanks! Can I sucker you into doing #441 too?
[18:35] <hatch> it's really really small :)
[18:35] <kadams54> To make up for it, I'll check out your trivial CSS change.
[18:35] <kadams54> Hah!
[18:35] <kadams54> Great minds.
[18:35] <hatch> lol
[18:40] <kadams54> Trivial thing I just noticed: we don't have proper pluralization in the new scale up UI or in the unit list below… "1 units" and "1 running units".
[18:40] <kadams54> Not in the scope of your work though
[18:41] <rick_h__> it's a simple helper, add it real quick :P
[18:41] <kadams54> OK, #441 is ready to ship
[18:41] <rick_h__> we're getting bad about not catching drive by stuff with that plural stuff. It's getting wrong all over
[18:45] <hatch> kadams54 thanks, I'll add that pluralization in the follow-up
[18:52] <hatch> http://blog.atom.io/2014/07/02/moving-atom-to-react.html
[18:52] <rick_h__> kadams54: how goes your branch?
[18:53] <hatch> it says they are using jquery...I really have no idea what for when they control the environment it operates in
[18:54] <rick_h__> kadams54: I'm heading to the vet, but I'd like to get another set of eyes on your WIP to help move the card of work through. hatch or Makyo can one of you take a peek and see how you can help please?
[18:54] <hatch> sure
[18:54] <hatch> kadams54 what's he talking about?
[18:54] <hatch> ;)
[18:55]  * rick_h__ goes to get the dog poked
[19:01] <bac> yay, my favorite test case now works: https://jujucharms.com/?text=ouch
[19:04] <jcsackett> kadams54: are you leaving friday morning from london?
[19:07] <hatch> jcsackett I am
[19:07] <hatch> well...friday noon i think
[19:08] <hatch> iunno it's in the spreadsheet heh
[19:08] <jcsackett> hatch: i'm pinging kadams54 b/c i think he is on the same flight as me, and mine got modified--i'm leaving the 26th, but the sheet says the 25th. i would imagine kyle is in the same boat, unless he really is leaving friday AM.
[19:08] <hatch> ohhh
[19:09] <jcsackett> yeah, i just emailed sarah to sort it, but kadams54 might need to do the same.
[19:10] <kadams54> jcsackett: Uh oh, yeah, that wouldn't be good
[19:10] <jcsackett> kadams54: you're in the same boat, then?
[19:10] <kadams54> jcsackett: I haven't seen any e-mails about changes yet.
[19:10] <jcsackett> kadams54: are you leaving sat or fri?
[19:10] <kadams54> Last I knew, Friday
[19:11] <jcsackett> kadams54: ok, so you're fine. that's what it says for you. we're both DL-19, just on different days.
[19:11] <kadams54> DL0019, leaving at 9:35 AM
[19:12] <jcsackett> cool, figured there was a chance we were both on the same flight, rather than just flight num, and yours had been goofed too.
[19:12] <kadams54> hatch, Makyo: I'll have a PR shortly for you to look at on that branch.
[19:12] <jcsackett> but it's just the same flight, so i'm the only one goofed. :P
[19:12] <jcsackett> er, flight no. anyway.
[19:20] <kadams54> jcsackett: I'll try not to trash the plane too much on my flight then :-)
[19:20] <jcsackett> kadams54: i would appreciate that. :p
[19:44] <kadams54> guihelp: is there a reason /:flags:/mv/ is 404ing for me on comingsoon?
[19:45] <hatch> bac ^ comingsoon isn't dispatching paths to the guiserver
[19:46] <hatch> kadams54 ^ the app is supposed to be handling the urls but the server isn't passing them through
[19:48] <bac> hatch: ungood
[19:48] <hatch> that's your fault right?
[19:48] <hatch> :)
[19:48] <bac> hatch: yes, it was my mid-afternoon time bomb
[19:48] <hatch> lol
[19:48] <hatch> bac is it something you can take a look at or should someone else?
[19:50] <bac> hatch: i'm looking.
[19:51] <hatch> thank yas!
[19:54] <bac> hatch: [client 198.69.45.233] File does not exist: /var/www/juju-gui/build-prod/:flags:
[19:54] <hatch> bac right, but why is it now thinking that that's a file?
[19:55] <hatch> http://comingsoon.jujucharms.com/machine also fails for example
[19:55] <bac> so apache is attempting to
[19:55] <hatch> bac it should be passing anything that's not in the juju-ui path to the GUI
[19:55] <bac> serve it instead of having the app do it
[19:55] <hatch> yeah...did someone break the charm?
[19:55] <bac> charm or apache config?
[19:56] <hatch> doesn't the charm contain the apache config?
[19:56] <hatch> heh
[19:56] <bac> not charm.  this isn't installed via  charm
[19:56] <hatch> ohhh
[19:56] <bac> it were hand-rolled by me
[19:56] <hatch> I thought this was the charm which was just updated every time
[19:56] <bac> has anyone tried :flags: in the last week or so?
[19:57] <hatch> I thought I used it yesterday tbh
[19:57] <hatch> maybe it was monday?
[19:57] <bac> this config hasn't changed since the 10th
[19:59] <hatch> hmm, well then...
[19:59] <hatch> maybe I didn't use a flag or direct url
[19:59] <hatch> sorry I can't be of more help
[19:59] <hatch> I could look at the config though if you want
[20:02] <bac> hatch: http://bazaar.launchpad.net/~juju-gui-charmers/charms/trusty/juju-gui/trunk/view/head:/config/apache-site.template
[20:02] <bac> that's what the charm does
[20:03] <bac> i didn't think to copy the charm and just manually created an apache config from the nginx config we used on the old site
[20:03] <bac> hatch: FallbackResource looks interesting
[20:03] <hatch> I was just going to say that might be the trick, I was just looking it up heh
[20:04] <hatch> yep that does look like what we need
[20:04] <hatch> wow it's been a long time since I've had to read an apache config
[20:04] <bac> ha
[20:04] <hatch> brings me back to the good ol days of multiple client PHP work on the same server
[20:04] <hatch> oy
[20:05] <hatch> "directive all the things!"
[20:11] <bac> thanks hatch.  kadams54 http://comingsoon.jujucharms.com/:flags:/mv/ works
[20:11] <kadams54> bac: thanks
[20:11] <hatch> bac thanks for doing that so quick! u rock
[20:11] <bac> np
[20:25] <kadams54> Makyo, hatch: WIP PR at https://github.com/juju/juju-gui/pull/442
[20:25] <Makyo> Looking
[20:26] <kadams54> Makyo, hatch: I also ran into something that may have invalidated work today. Need to talk to someone about the supportedContainers attribute on machines.
[20:29] <hatch> oh?
[20:29] <hatch> what's the issue?
[20:34] <rick_h__> and the dog has a high temp right before I leave for a trip. Go pets!
[20:36] <hatch> poor puppy
[20:37] <kadams54> hatch: got a few minutes to chat?
[20:37] <hatch> sure 1min just got to relocate to somewhere cooler
[20:38] <kadams54> You're in Canada already.
[20:38] <hatch> it's like 20c out there...way to hot ;) ( rick_h__ )
[20:39] <hatch> kadams54 ok joining the standup room
[20:44] <jrwren> today, bundles don't have ability to run services on existing machine, does it?
[20:44] <jrwren> I know this is coming as part of charm store api
[20:46] <hatch> jrwren correct
[20:46] <hatch> bundles are just a yaml file
[20:46] <hatch> actually
[20:46] <hatch> that's a deployer file
[20:46] <hatch> :)
[20:46] <hatch> go conflated terminology!
[20:46] <jrwren> a yaml file with no to: machine node :)
[20:49] <jrwren> oh THAT juju-deployer!
[20:49] <jrwren> thanks hatch
[20:49] <hatch> kadams54 your branch will conflict with Makyo's that just landed
[20:50] <kadams54> hatch: Got it.
[20:50] <hatch> jrwren lol np, don't worry it's confusing to people who have been working with it for a long time :) 
[20:50] <hatch> the deployer will be moving into juju-core at some point
[20:52] <jcsackett> jujugui: can someone review https://github.com/juju/juju-gui/pull/443 for me?
[20:52] <hatch> yup
[20:52] <hatch> I can
[20:53] <jcsackett> thanks hatch.
[20:53] <Makyo> Totally spaced out lunch.  Sorry kadams54, didn't mean to go awol
[20:53] <kadams54> Makyo: np
[20:53] <hatch> psshhht Colorado.....
[20:53] <kadams54> lol
[20:53] <Makyo> What? D:
[20:55] <hatch> "sorry bro I like..................totally space out.............what was I doing again?.........."
[20:55] <Makyo> Pff.  I just meant I got hungry and realized how late it was :P
[20:56] <hatch> lol suuuure
[20:56] <hatch> ;) ;)
[21:02] <jcsackett> hatch: you've got to get a new joke about colorado.
[21:03] <hatch> "what are you 50 and run in bare feet??"
[21:03] <hatch> how's that?
[21:04] <hatch> that's all the stereotypes I know about CO :P
[21:04] <hatch> jcsackett comments made - maybe if you want to check them out before I do a qa
[21:04] <jcsackett> hatch: looking into switching to a truthier way of doing things now.
[21:05] <jcsackett> changes should be up in a sec.
[21:05] <hatch> cool thanks
[21:05] <jcsackett> hatch: the only "not major" change we've got spec for is containers, unless there's a bug i don't know about.
[21:06] <hatch> jcsackett right, I mean, the rule is that only things that cost money are in the top right?
[21:06] <hatch> config changes don't involve $ changes
[21:06] <jcsackett> hatch: this whole rule is new to me, and like i said, only containers have been mentioned to me.
[21:06] <jcsackett> we can add config if we're told to put config in.
[21:06] <jcsackett> but until that's marching orders, i don't think we should expand this scope.
[21:06] <hatch> ok that's cool - want to reply to that in the PR? 
[21:06] <jcsackett> already did.
[21:07] <hatch> :) thanks 
[21:07] <hatch> lemme know when changes are up and I'll pull it down for qa
[21:11] <jcsackett> hatch: sure thing. hit one weird thing having changed to truthy
[22:10] <jcsackett> hatch: finally pushed up. had a surprising amount of fallout from badly structured tests.
[22:10] <hatch> ahh, well then!
[22:10] <jcsackett> well, badly is a bit strong--but brittle, anyway. :)
[22:10] <hatch> thanks I'll take a look
[22:10] <hatch> :)
[22:11] <jcsackett> cool. i'm off to get stuff for dinner. if you run into anything QA bad i'll have to deal with it tomorrow morning, otherwise i'll rebase and :shipit: when i return if you qa ok.
[22:12] <hatch> sounds like a plan
[22:12] <hatch> cya
[22:12] <jcsackett> lata
[22:58] <hatch> jcsackett looks good +1, I have some issues with the UI but I sent an email off to design about them
[22:58] <huwshimi> Morning
[23:04] <hatch> mooooooorning
[23:05] <hatch> tonight I'm going to try and convince myself web components make sense
[23:06] <huwshimi> Yay!
[23:08] <hatch> so far it's just seamed like they are going to become the next jquery plugin mess
[23:08] <hatch> but maybe....just maybe I'll find an example which makes sense heh
[23:10] <huwshimi> hatch: What are you looking at exactly?
[23:11] <hatch> huwshimi polymer/web components 
[23:12] <hatch> there are still going to end up being 200 different modal dialogue web components each adding different frameworks to the page, each with different css, aria support etc etc etc
[23:13] <hatch> so I'm really not sure how it's going to get us further ahead than we already are right now
[23:13] <hatch> I'm still not going to take some calendar web component which adds jquery to the page and include it in our app for example
[23:14] <hatch> and it moves the configuration into the DOM essentially making html xml :)
[23:18] <huwshimi> yeah, it definitely has an xslt thing going on.
[23:18] <hatch> for people making web pages it's probably really awesome 
[23:18] <hatch> web apps...not so much
[23:18] <hatch> at least that's where I'm at now :)