[03:02] <rick_h_> huwshimi: your card ok? I wasn't sure if it's something we could tweak yet until other stuff landed
[03:13] <huwshimi> rick_h_: It's fine so far. I have the basics working, just need to get all the update/add/remove bits changing the correct elements.
[03:14] <rick_h_> huwshimi: ok cool
[11:28] <frankban> luca: morning, do you have a link to a ghost relation wireframe?
[11:29] <luca> Hi frankban, it should look like this: https://docs.google.com/a/canonical.com/file/d/0B7XG_QBXNwY1cjhIZnZXS3pxZG8/edit
[11:29] <luca> frankban: a grey line with no status indicator in the circle
[11:30] <frankban> luca: thanks, that's what I was looking for
[11:33] <luca> frankban: great. I can get Spencer to output the assets if you need.
[11:39] <frankban> luca: it would be nice, I just need the circle svg
[11:45] <luca> frankban: ok, I’ll get him to send it over as soon as he can
[11:45] <frankban> luca: thanks
[11:49] <frankban> luca: abort! I was able to create the svg starting from an existing one
[11:49] <luca> frankban: ah, nice, no worries
[11:50] <frankban> luca: #e2e2e2 is almost invisible given the current GUI background
[11:51] <frankban> luca: at least with my crappy external monitor. much better using the macbook screen
[11:54] <luca> frankban: ok, thats the Ubuntu grey but I’ll have a word with Spencer to see if we can get something with more contrast.
[12:14] <frankban> guihelp: I need one review and QA for https://github.com/juju/juju-gui/pull/275 ? Anyone? thanks!
[12:14] <rick_h_> frankban: sure thing
[12:14] <frankban> rick_h_: thanks
[12:36] <bac> jcsackett: around?
[12:36] <jcsackett> bac: ish.
[12:37] <jcsackett> what's up?
[12:37] <bac> jcsackett: no rush, when you get in fully would you look at https://codereview.appspot.com/91140045 ?
[12:37] <jcsackett> bac: sure.
[12:39] <frankban> rick_h_: thanks for the review!
[12:39] <rick_h_> antdillon: morning, how are you getting along with my email?
[12:39]  * frankban lunches
[13:11] <antdillon> rick_h_, Morning, I am. Getting back up to speed
[13:11] <rick_h_> antdillon: cool, let me know if you get stuck or have any questions. 
[13:11] <antdillon> rick_h_, Will do thanks
[13:14] <jcsackett> bac: lgtm, with a minor question.
[13:14] <bac> there are no minor questions
[13:14] <bac> no, wait, there are no dumb questions
[13:17] <bac> jcsackett: i think what happened here is in an earlier version i was using the 'extra_data' to fill out the expected results, so i wanted it squirreled away separately.
[13:17] <bac> jcsackett: so i can make the change you request easily and it'll be more readable.
[13:18] <jcsackett> bac: awesome.
[13:28] <redir> guihelp how does one troubleshoot bzr connections? 
[13:28] <bac> redir: what's the prob?
[13:29] <redir> I can't seem to push anything -- it hangs -- and -v doesn't display any more information
[13:29] <kadams54> With powerful incantations and blood sacrifice
[13:29] <kadams54> That's how
[13:29]  * redir gets blood bowl and starts chanting
[13:30] <redir> idea
[13:30] <redir> found it...
[13:30] <jcsackett> see, the blood bowl totally works.
[13:30] <redir> nm 
[13:31] <redir> heh
[13:32] <redir> stale .ssh ControlPath entry
[13:35] <redir> bac got a minute to talk about the ngram search interface?
[13:42] <rick_h_> jujugui added a card to urget, found a big issue while trying to see where we are with machine view in a real lxc env today
[13:42] <rick_h_> urgent bah
[13:42] <rick_h_> heads up for folks looking for a new card soon
[13:44] <redir> rick_h_: I don't have permission to add comments/edit the docs you sent me
[13:44] <rick_h_> redir: sorry, sec
[13:44] <redir> np
[13:45] <rick_h_> redir: updated
[13:48] <rick_h_> ok, so maybe that bug is my machine
[13:48] <redir> tx
[13:48] <rick_h_> jujugui can anyone try to reproduce my bug in urgent please? Now I can't click on a google doc and tried in FF and chrome so maybe my computer hates me
[13:48] <kadams54> Checking
[13:49] <frankban> rick_h_: trying
[13:49]  * rick_h_ feels like his computer is possessed
[13:50] <frankban> rick_h_: I am able move service blocks in LXC, with and without flags
[13:50] <bac> jcsackett: i did this instead: http://paste.ubuntu.com/7410490/
[13:51] <frankban> able to move even
[13:51] <jcsackett> bac: ok, i can see the value of that as a way to isolate expected value. thanks for the changes.
[13:51] <bac> redir: sorry, didn't see your message.  let me get my branch landed then let's talk, whatever
[13:51] <bac> jcsackett: it is a better test...
[13:51] <redir> bac: np, ping me when you are free...
[13:51] <rick_h_> frankban: thanks deleting the card
[13:57] <bac> redir: want to chat on G+?
[13:57] <redir> sure
[13:58] <redir> bac: gimme 5 minutes?
[13:58] <bac> ok
[14:03] <redir> bac: ready
[14:10] <bac> redir: https://plus.google.com/hangouts/_/canonical.com/daily-standup
[14:17] <hatch> morning
[14:19] <rick_h_> morning
[14:20] <hatch> I can talk today
[14:20] <hatch> yay
[14:31] <kadams54> guihelp: I know I've seen this test failure before, but can't remember what it means: "Error: Uncaught SyntaxError: Unexpected token C (http://192.168.33.10:8888/test/index.html:1)"
[14:31] <kadams54> That ring a bell for anyone else?
[14:31] <hatch> kadams54 run make lint
[14:31] <hatch> it also seems like it can't serve that file
[14:32] <hatch> if you open that file in chrome devtools you'll see why it's broken
[14:32] <hatch> assuming you're running test server right now
[14:36] <rick_h_> kadams54: an unmocked api request
[14:37] <rick_h_> hatch: can you chat to antdillon on watching for changes to the ecs stuff please?
[14:37] <rick_h_> or Makyo ^
[14:37] <hatch> sure
[14:37] <kadams54> hatch: lint run, still having problems
[14:37] <antdillon> hatch, Thanks
[14:38] <kadams54> rick_h: it's happening in the after each hook
[14:38] <rick_h_> kadams54: well that just means that's when the api call responds or something. 
[14:39] <kadams54> Yeah, I think you're right, looking for API calls…
[14:39] <rick_h_> kadams54: but the issue is the api response code trying to json decode something that isn't valid json which is what that error is from
[14:39] <hatch> ugh this test suite...
[14:39] <kadams54> I can see the error is bubbling out of a json-parse-debug.js
[14:40] <rick_h_> kadams54: yep
[14:41] <hatch> antdillon ok you can't listen for changes to the changeset
[14:41] <hatch> (that was easy)
[14:41] <hatch> next!
[14:41] <hatch> :P
[14:42] <antdillon> hatch, So polling the changeset?
[14:42] <rick_h_> hatch: boooo, no ATTR to watch?
[14:42] <hatch> antdillon yeah this appears to be an oversight in the design
[14:42] <rick_h_> :(
[14:42] <antdillon> hatch, rick_h_ lol
[14:42] <hatch> should be pretty trivial to fix though
[14:43] <hatch> do you want to tackle that as a separate branch first?
[14:43] <rick_h_> hatch: antdillon +1
[14:43] <antdillon> hatch, I can try get it in this branch if you know of another example
[14:43] <hatch> It's out of scope of that branch
[14:44] <hatch> it's quite a bit of changes
[14:44] <hatch> basically everything that references the changeSet property needs to instead access an attribute
[14:44] <hatch> OR
[14:44] <rick_h_> hatch: just need the ECS to fire a change event? 
[14:44] <hatch> you hook up to the changeSet property using out object.observe polyfill
[14:44] <hatch> less custom events the better
[14:44] <rick_h_> ok
[14:45] <hatch> imho
[14:45] <rick_h_> sure
[14:45] <hatch> so....hmm lemme take a look
[14:45] <hatch> the code is so much cleaner not having to get/set an attribute
[14:47] <hatch> antdillon ever done anything with Object.observe() ?
[14:48] <antdillon> hatch, Not really, how hard could it be :/
[14:49] <hatch> Object.observe(ecs.changeSet, callback)
[14:49] <hatch> not very :P
[14:49] <antdillon> hatch, Cool
[14:49] <hatch> haha yeah....you want to look into databinding.js
[14:49] <rick_h_> no, no he doesn't
[14:49] <hatch> and grep for `observe` and `unobserve`
[14:50] <hatch> but ignore everything else
[14:50] <hatch> it's magic in there
[14:50] <antdillon> hatch, Got it
[14:51] <hatch> antdillon basically the pollyfill polls the object :) 
[14:51] <jcsackett> jujugui: nine minutes to call, yada yada.
[14:52] <hatch> antdillon app/assets/javascripts/Object.observe.poly.js
[14:52] <hatch> it's pretty thick, not much to see, but incase you were interested
[14:54] <hatch> we should probably update our polyfill
[14:55] <rick_h_> hatch: it's a slack card already
[14:55] <hatch> oh cool
[14:55] <hatch> there has been a ton of work done to the Polymer one
[14:55] <rick_h_> yep
[14:56] <antdillon> hatch, Will take a look
[14:56] <rick_h_> antdillon: you're welcome to join https://plus.google.com/hangouts/_/canonical.com/daily-standup?authuser=1
[14:57] <rick_h_> at the top of the hour for stand up
[14:57] <hatch> antdillon so this is just my preference because the code is so much cleaner not using attributes - if you run into any big issues feel free to let me know and we can revisit switching changeSet to an attribute
[14:59] <rick_h_> jujugui call in 1 
[14:59] <hatch> rick_h_ the blues docs that you shared are not editable fyi
[14:59] <rick_h_> hatch: k, will look. Thought I gave edit there
[14:59] <hatch> haha, blues... redir 
[15:00] <rick_h_> oh, can edit folder but not docs boo google 
[15:00] <hatch> heh, hyper specific ACL
[15:00] <rick_h_> Makyo: hatch redir call time
[15:21] <antdillon> hatch, You in the units in db call?
[15:21] <hatch> I am 
[15:22] <antdillon> hatch, Let me know when your free for a hand on this observe stuff please
[15:26] <hatch> will do
[15:30] <hatch> antdillon done
[15:30] <antdillon> hatch, Think I got it
[15:30] <hatch> nice
[15:37] <rick_h_> kadams54: want to pair up now?
[15:39] <kadams54> Yup
[15:39] <kadams54> Working on a PR
[15:39] <rick_h_> kadams54: cool, setup a hangout when you're ready and linky me
[15:40] <rick_h_> jujugui marked the unit db list card as critical and top of the lane 
[15:45] <kadams54> rick_h_: https://plus.google.com/hangouts/_/7acpjs4qa80af83u7shrgk05eg?authuser=2&hl=en
[15:51] <hatch> jcsackett got what you need from that diff img?
[16:11] <jcsackett> hatch: yup.
[16:13] <rick_h_> guihelp in running tests I see a ton of "Error: Invalid value for <g> attribute transform="translate(NaN,NaN)" 
[16:13] <rick_h_> this was related to the error I noticed in QA today
[16:13] <rick_h_> anyone remember seeing or can dupe that?
[16:17] <Makyo> Trying now..
[16:18] <frankban> uhm, so this is confusing, it seems models.js:ServiceUnitList.process_delta already has the code to update both "this" (the units model list itself) and service.get('units')... 
[16:19] <frankban> rick_h_: ^^^ so maybe something from the past. anyone remember if in the initial impl we had a top level unit list?
[16:19] <rick_h_> frankban: so we already have a units list? I didn't see it inspecting the db
[16:19] <Makyo> rick_h_, I'm seeing it in test-server. investigating quiickly.
[16:19] <rick_h_> Makyo: hmm, I had it in test server. Maybe my system is possessed today
[16:19] <rick_h_> Makyo: latest trunk?
[16:20] <Makyo> rick_h_, yeah, that's where I'm seeing it.
[16:20] <rick_h_> frankban: yea, no idea. I'm actually newer to the db and not sure of its history. 
[16:20] <rick_h_> Makyo: oh sorry, you did see it
[16:20] <rick_h_> Makyo: misreading, who put monday in my wed
[16:20] <frankban> rick_h_: no, we don;t have a top level unit list, but the process delta seems to assume we have it. so basically we are calling _process_delta twice on the same model list. trying to confirm
[16:20] <rick_h_> frankban: heh, well we're half way there then :)
[16:20] <frankban> heh :-)
[16:21]  * rick_h_ runs for food stuff before next meeting
[16:28] <bac> redir: sorry, meant to ask that question over here.
[16:28]  * bac lunches
[16:29] <bac> redir: over here, over here!
[16:30] <bac> redir: if it works, please 'bzr add' it to your branch
[16:30] <bac> redir, ok if not this branch, then share it somehow
[16:32] <redir> bac: I am in a maze of twisty little passages, all alike....
[16:32] <redir> I didn't complete it. I got as far as importing a couple things and looking for the necessary bits. 
[16:33] <redir> but decided that it wasn't trivial and was sorting socks instead of working on the actual card
[16:36] <redir> bzr makes me feel like a ten left thumbed person
[16:51] <hatch> anyone available for a review?
[16:51] <rick_h_> hatch: I can in about 5 if you need
[16:51] <hatch> ok just writing docs right now
[16:58] <hatch> jujugui https://github.com/juju/juju-gui/pull/277 whoever is available for a review/qa
[17:00] <rick_h_> hatch: hit a conflict against trunk, please make sure to rebase off develop
[17:00] <hatch> doh
[17:00] <rick_h_> small simple one
[17:02] <hatch> rick_h_ fixed
[17:02] <hatch> github thinks I did these commits 6 days ago heh
[17:02] <hatch> I must have broken something in the rebase
[17:07] <hatch> doh lint
[17:07] <hatch> and I just ran it too
[17:20] <hatch> so when I booted up my computer today, refind wasn't there, and neither was grub
[17:20] <hatch> :/
[17:20] <rick_h_> hatch: you did a osx upgrade?
[17:20] <rick_h_> hatch: every time it upgrades I have to reinstall refind
[17:20] <rick_h_> and then it's all back
[17:20] <hatch> I did some updates 
[17:21] <rick_h_> yea
[17:21] <hatch> ohh
[17:21] <hatch> sonofa
[17:21] <rick_h_> rerun the refind install.sh and you'll be fine
[17:21] <hatch> ahh cool cool
[17:21] <hatch> osx is a tricky bugger
[17:21] <rick_h_> it doesn't like the parasite os on there
[17:23] <redir> refind?
[17:24] <rick_h_> redir: let's you setup a boot manager to run ubuntu on apple hardware
[17:24] <hatch> http://www.rodsbooks.com/refind/
[17:24] <rick_h_> hatch: comments done, a few questions. Let me know if you want to chat on them. Will start QA
[17:25] <hatch> cool looking
[17:25]  * rick_h_ runs away before he can read them
[17:25] <rick_h_> does qa from the camper in the driveway
[17:25] <hatch> haha, it's still too cold here for normal camping
[17:25] <hatch> does your camper have a heater?
[17:25] <rick_h_> I think we've had our last frost warning to trying to get out for mother's day weekend
[17:26] <rick_h_> oh yea, propane furnace
[17:26] <rick_h_> and electric heating pads for the bunk ends
[17:26] <rick_h_> since the tent ends get a bit chilly at night
[17:31] <rick_h_> lol qa'ing this with the simulator turned on is nuts :P
[17:31] <hatch> yeah it's super broken hah
[17:31] <hatch> that's why I bolded that comment :)
[17:32] <rick_h_> Uncaught TypeError: Cannot read property 'add_unit' of undefined
[17:33] <rick_h_> I think my comments in there that hit on this are valid though. 
[17:34] <hatch> hmm when did you get that?
[17:34] <rick_h_> hatch: after the simulator reset the thing 5 or so times and I finally got the numbers input and hit add units
[17:34] <hatch> oh....well yeah, you need to turn the simulator off, the machine view panel is just blowing it all away
[17:34] <hatch> I'm surprised more doesn't break
[17:35] <hatch> :)
[17:35] <rick_h_> well, let's shoot for less breakage even with the simulator :P
[17:35] <hatch> well it's not the simulator, it's the rerendering of the panel 
[17:36] <hatch> if you hack the machine panel view code to stop re-rendering then you don't run into any issues
[17:36] <rick_h_> I thought that was in here?
[17:36] <hatch> no that's what huw is working on
[17:36] <hatch> the machine panel view listens to any change in the machine model, then re-renders everything
[17:39] <rick_h_> hatch: right but why does the scale up widget need to listen to those?
[17:39] <rick_h_> hatch: I think having those move from under the user would be a bit not-good
[17:39] <hatch> it doesn't
[17:40] <hatch> it's in the machine view
[17:40] <hatch> so when the machine view gets re-rendered it re-renders the scale up view
[17:40] <rick_h_> app/widgets/service-scale-up-view.js - line #70 in the diff
[17:40] <hatch> yeah that's where it listens to re-render the service list if it gets updated
[17:41] <rick_h_> right, but that seems bad UX imo, a user is there typing and stuff moves on them
[17:41] <hatch> it doesn't if the machine view doesn't re-render
[17:41] <hatch> that's what the _updateUI method does
[17:41] <hatch> and why it's so funky
[17:41] <rick_h_> ok, let's forget the machine view panel and just look at the life cycle of this new View
[17:42] <rick_h_> it's init'd and rendered, part of that is binding to change events on the db.services.on()
[17:42] <rick_h_> and if that changes, adds, removes, it updates the service list, which updates the UI
[17:42] <rick_h_> all while the user is trying to enter a 3 into the 4th box...
[17:43] <rick_h_> which is now the 5th box, or doesn't exist any more because of the change event from within the scale up view itself
[17:43] <hatch> well if the service goes away then they can't scale it up anyways
[17:43] <hatch> if the service is still there, it doesn't modify the UI
[17:44] <hatch> so you'll still be focused and typing in the input
[17:44] <rick_h_> that's horrible to users, and order it promised to never move the list on you? 
[17:44] <rick_h_> if I'm entering in the 4th box and the 2nd one goes away?
[17:45] <rick_h_> I don't think we can treat this widget as live updating. 
[17:45] <hatch> You thought the other way in Vegas :)
[17:45] <rick_h_> heh, well I think when you click on the + is needs to be live
[17:45] <rick_h_> and when you close it/reopen it it's updated
[17:46] <rick_h_> but only at interaction points 
[17:46] <hatch> so what if they scale up a service which doesn't exist anymore?
[17:46] <rick_h_> then we'll have to be smart and bring up a service
[17:47] <rick_h_> or throw an error during the deploy confirmation step
[17:47] <hatch> so now adding a unit deploys a charm?
[17:47] <rick_h_> we've got places to confront the user without moving their UI around on them as they try to type
[17:47] <hatch> :)
[17:47] <rick_h_> we'll probably have to start with the confirmation error, we need that anyway in case of conflicting names/etc
[17:47] <rick_h_> but yea, I should be able to say "oh I wanted a unit of that, sorry rick blew it away, I want it back"
[17:48] <rick_h_> "rick doesn't need mysql any more but I sure do"
[17:48] <hatch> then you need to go deploy it again the usual way
[17:48] <hatch> having a scale up UI deploy charms is a little crazy
[17:48] <rick_h_> ok, still. Regardless of the 'how' I think that once you put the form in front of the user you can't go moving it
[17:49] <rick_h_> if you're entering a username someone just took, I don't delete your data entry, or delete the field. 
[17:49] <rick_h_> I show you an error/message to help you resolve the issue
[17:49] <hatch> and if a new service is deployed you want to mass scale up you have to click the X then the + again to see it?
[17:49] <rick_h_> and then this code gets a lot simpler. It doesn't need to watch the db and such
[17:50] <rick_h_> if you click + and someone adds a service you weren't planning on scaling it already anyway
[17:50] <hatch> Iunno, I disagree 
[17:50] <rick_h_> it wasn't there when you started, you might want to go back and scale that one up before you hit deploy on the bar, but you weren't planning on touching it at the moment you started your interaction
[17:51] <rick_h_> how could you know it was there?
[17:51] <rick_h_> going to be there I guess
[17:51] <hatch> it's just odd that it'll be the only place in the UI that doesn't maintain env state
[17:51] <hatch> the inspector unit list jumps around while you may be working on ti
[17:51] <rick_h_> does the inspector config auto reload if someone does a service upgrade?
[17:52] <rick_h_> right, and everyone hates that darn jumping unit list thing
[17:52] <rick_h_> it's so hostile to users
[17:52] <hatch> well, it's accurate 
[17:52] <rick_h_> and this is a small interaction with very very limited env interaction. It's only giving you an option to do something based on a list. 
[17:53] <rick_h_> hatch: sure it's accurate, doesn't make it nice to use
[17:53] <hatch> I'll remove the binding stuff - but maybe the X should turn to a refresh button or something if the db changes
[17:53] <rick_h_> hatch: hey, I'm all for getting other opinions. 
[17:53] <hatch> it's not very intuitive if the user is living in the machine view and wants to mass scale up and there are no services in the list anymore
[17:53] <rick_h_> hatch: I'm just sharing mine, I think the code can be simpler and easier to use without the event watching
[17:54] <hatch> oh for sure
[17:54] <rick_h_> if the users live in machine view I think we've failed imo
[17:54] <rick_h_> but that's a different discussion
[17:55] <rick_h_> which we can have in our upcoming 1-1 :P
[17:55] <hatch> hah, well I'm totally confused of the direction of the new no-inspector UI 
[17:55] <hatch> which may mean people live in there
[17:55] <rick_h_> you and me both. Had a chat with luca bout that yesterday
[17:56] <Makyo> jujugui quick review/qa: https://github.com/juju/juju-gui/pull/278
[17:56] <hatch> I'm hoping he changed his mind? :)
[17:58] <hatch> Makyo I think that your branch needs to redirect the user to the default of sectionA
[17:59] <hatch> thoughts?
[17:59] <hatch> so their url actually changes I mean
[17:59] <rick_h_> +1 redir like we do for /fullscreen and such
[17:59] <Makyo> Okay.
[17:59] <rick_h_> to end up in a good place
[18:00] <redir> wha?
[18:00] <hatch> Makyo that may mean that it'll need to be done in the 'validator' which is yet to be written
[18:00] <hatch> redir I think rick_h_  meant to say me or Makyo  :)
[18:00] <rick_h_> redir: huh?
[18:01] <Makyo> hatch, +1 on redirecting, but if the validator has yet to be written, that's outside the scope of this branch.
[18:01] <rick_h_> oh redir as in short for redirct
[18:01] <hatch> haha
[18:01] <redir> :) 
[18:01] <rick_h_> sorry, poor naming choice there redir :P
[18:01] <redir> long running joke
[18:01] <hatch> Makyo yeah, definitely, so would that mean this branch needs to be benched?
[18:01] <hatch> Or land as-is and fix later?
[18:01] <rick_h_> I guess, now I'm wondering...give redir a task it ends up on Makyo. like a fine waxed car
[18:02] <hatch> lol
[18:02] <Makyo> hatch, Either or. I'm loathe to have wasted time on it while things diverge further.  Can we add an XXX comment and land?
[18:05] <hatch> yeah that should be fine
[18:17] <bac> if robbie *just discovered* juju.academy does that mean he slept through the lightning talks?
[18:24] <hatch> bac haha
[18:27] <Makyo> Oh, neat, we actually got that URL.
[18:29] <Makyo> Have it up on the book site now: http://book.exploring-juju.com/
[18:30] <hatch> nice :)
[18:30] <hatch> look at all you guys, being good juju community peoples
[18:31] <alexpilotti> hi guys, is there a way to have a password field in the charm’s properties on the gui?
[18:32] <hatch> alexpilotti do you mean the password for the GUI/
[18:33] <alexpilotti> hatch: in a new charm, we need to specify among the properties a password
[18:33] <hatch> oh ok, well atm that's just a typical field
[18:33] <hatch> I'm guessing you want it to be a *** while you type?
[18:33] <alexpilotti> hatch: the “service settings” in teh GUI
[18:34] <alexpilotti> hatch: yep, typical password edit field
[18:34] <hatch> yeah, at the moment that's not supported but there have been some mumblings. Would you be able to file a bug requesting this feature?
[18:34] <hatch> https://bugs.launchpad.net/juju-gui
[18:34] <alexpilotti> hatch: sure
[18:34] <hatch> thanks
[18:37] <redir> bac: test_search.py:TestReindex.test_reindexed_no_client_charms deletes the non text index from the ini. Is that intentional?
[18:38] <bac> redir: don't know.  let me look.
[18:38] <alexpilotti> hatch: done: https://bugs.launchpad.net/juju-gui/+bug/1317228
[18:38] <_mup_> Bug #1317228: Passwords fields should be supported in the charm service settings <juju-gui:New> <https://launchpad.net/bugs/1317228>
[18:39] <alexpilotti> hatch: is there a way to hack this in a quick and dirty way? We just need it for a demo
[18:39] <hatch> hmm
[18:40] <hatch> lemme take a look
[18:44] <bac> redir: i don't understand that test.
[18:44] <redir> bac: me either
[18:46] <rick_h_> alexpilotti: hatch this should be on juju. They need to support the idea in their config.yaml 
[18:46] <bac> redir: but this is why es data all disappear...
[18:46] <rick_h_> I guess it can be on both
[18:46] <redir> bac Yes, AFAICT.
[18:46] <alexpilotti> rick_h_: I agree
[18:46] <rick_h_> alexpilotti: what's the demo? Can you tweak the list of config values so the password is at the end/off the screen?
[18:47] <hatch> rick_h_ I've also shown him where we render the config UI and the template in PM
[18:47] <rick_h_> alexpilotti: or hard code the value in the fork of the charm and remove it from the config
[18:47] <alexpilotti> rick_h_: we’ll do that if we have no other chance :-) 
[18:47] <bac> redir: if you have the cycles, would be nice to ingest some stuff, disable that test, run make test, and then ensure your index is still there.  if so, perhaps just leave that test disabled until we can re-write it sanely.
[18:48] <rick_h_> alexpilotti: ok, we're up against a wall for ODS demo atm so not a lot of time until after next week to look at better solutions
[18:48] <redir> bac affirmative
[18:48] <rick_h_> those are the things I can think of off the top of my head to get by for the moment
[18:49] <bac> redir: and if it solves the problem then i'll buy you a beer at our next meeting.
[18:49] <hatch> ok stepping out for lunch
[18:49] <hatch> bbl
[18:59] <redir> bac was there a bug for that or just a general annoyance?
[19:00] <bac> latter
[19:11] <redir> merge problems:/
[19:11] <redir> bac: I should be doing something like "bzr merge ../trunk" yes?
[19:12] <bac> redir: do you have a current trunk branch?  if not: bzr merge lp:charmworld
[19:12] <redir> I went to trunk and did bzr pull
[19:12] <redir> but I'll try merge lp:charmworld
[19:13] <bac> and it is on revno 508?
[19:13] <bac> redir: what was the merge problem you saw?
[19:13] <redir> yup
[19:14] <redir> some conflicts that seemed easy enough, but I wind up with a mongo_services object that is undefined
[19:15] <bac> redir: sounds like bad conflict resolution
[19:15] <bac> compare api/__init__.py with trunk
[19:19] <jcsackett> rick_h_: where are the docs on how to set up tmux like you have it, where it just auto starts with tabs?
[19:20] <redir> bac yeah that doesnt' seem like it merged very well at all
[19:21] <redir> and test failures. lemme try again
[19:27] <bac> jujugui: http://qa.manage.jujucharms.com/heartbeat is alive again, after a long hiatus
[19:27] <jcsackett> bac: \o/
[19:28] <kadams54> rick_h_: let me know if you have a moment to talk about my branch… at a decision point here.
[19:28] <bac> turns out, some services on canonistack using orangesquad credentials did not specify admin-secret or control-block in environments.yaml.  juju made up strings for those values, but used unicode values that swift could not handle.  thus swift went crazy for everything associated with orangesquad.  at least that's how i understand it from sinzui's telling.
[19:29] <kadams54> bac: help me out here… what's that do and what changes now that it's back up?
[19:30] <bac> kadams54: for you, nothing.  :)
[19:30] <kadams54> :-)
[19:30] <rick_h_> kadams54: otp will ping after
[19:30] <bac> kadams54: but for those working on charmworld dev, it is a canonistack-hosted qa machine that automatically gets updated with tip when changes land
[19:31] <bac> kadams54: manage.jujucharms.com and staging.manage.jujucharms.com run in our production environment and can only be touched by webops and can't have auto-deploys
[19:32] <kadams54> Ah, so no test/qa environment while this was down
[19:32] <kadams54> Just push to production and cross fingers?>
[19:32] <bac> kadams54: no, have webops deploy to staging but have no environment to investigate directly if things went wrong
[19:33] <kadams54> (y)
[19:36] <redir> bac: you have a second to pair up on these two failing tests? 
[19:37] <bac> redir: give me a sec to grab a beverage.  will ping you.
[19:37] <redir> k
[19:42] <rick_h_> kadams54: pong, ready to chat?
[19:42] <kadams54> Yup
[19:42] <bac> redir: daily hangout room?
[19:42] <bac> redir: oops.  i'll make on
[19:42] <rick_h_> jcsackett: http://uploads.mitechie.com/books/tmux_p1_1.pdf
[19:42] <redir> sure
[19:42] <kadams54> Well, let me grab my headphones and take a quick bio break, but mostly yeah :-)
[19:42] <bac> s/on/one/
[19:42] <rick_h_> kadams54: k
[19:42] <jcastro> rick_h_, http://lightswitch05.github.io/commit-cloud/#juju/juju-gui
[19:43]  * redir waits
[19:43] <rick_h_> jcastro: :)
[19:44] <bac> redir: https://plus.google.com/hangouts/_/76cpi4tbcce7jf0nq4j7nufuq0?hl=en
[19:45] <jcsackett> rick_h_: oh dear, a pdf.
[19:45] <rick_h_> jcsackett: :P
[19:46] <redir> bac: google says that party is over:)
[19:46] <jcsackett> rick_h_: this appears to be actual documentation.
[19:46] <jcsackett> i believe you just RTFMed me. :p
[19:46] <jcsackett> thanks. :)
[19:46] <rick_h_> jcsackett: I gave you a book on it
[19:47] <rick_h_> it's a pragmatic prog book, it's short
[19:47] <jcsackett> indeed. you have a book on make too, right? is that digital or physical?
[19:48] <rick_h_> http://uploads.mitechie.com/books/Managing_Projects_with_GNU_Make_Third_Edition.pdf
[19:48] <jcsackett> much obliged.
[19:48] <kadams54> rick_h_: https://plus.google.com/hangouts/_/72cpigd0956186nv27ogmbtm10
[19:57] <kadams54> rick_h_: gonna make sure CI builds are green and then https://github.com/juju/juju-gui/pull/276 will be ready for hand-off
[19:58] <rick_h_> ok
[19:59] <Makyo> hatch, +/-1 on my branch?
[20:06] <hatch> Makyo oops sorry 
[20:07] <Makyo> np, lunch ran a little long, had to get a new super on the beehive before the rain moved in.
[20:07] <hatch> lettr' rip
[20:07] <hatch> lol beehive
[20:07] <hatch> your neighbours must hate you
[20:08] <Makyo> We won't be around them long.  And besides, the problem here is hornets and yellowjackets, rather than honeybees, which mostly just leave you alone.
[20:09] <Makyo> And paperwasps. Hate those.
[20:09] <jcsackett> rick_h_: got a moment to chat?
[20:09] <rick_h_> jcsackett: sure
[20:12] <hatch> ahh yeah we have yellowhacket problems a lot
[20:12] <hatch> paperwasps up north moreso
[20:12] <hatch> those guys are agressive
[20:16] <jcsackett> Makyo: you got a moment to chat?
[20:16] <Makyo> Sure thing
[20:16] <jcsackett> https://plus.google.com/hangouts/_/gv2j7meqfalczxf3ggmfbk236qa?authuser=2&hl=en
[20:18] <Makyo> jcsackett, Sorry, left in the middle of you saying something, whoops :(
[20:27] <hatch> rick_h_ so I'm going to remove that databinding-like support from the mass scale up UI. I'll email design and ask them to put together an interaction for 'the service list has changed, now what?' story
[20:28] <rick_h_> hatch: sounds +1 to me 
[20:28] <rick_h_> and blame me for everything :P then luca will disagree because it's me and you can get it back into place 
[20:33] <hatch> lol!
[20:33] <hatch> sent
[20:33] <hatch> So what you're telling me is that Luca has a predisposition to hate every idea you have......good to know ;)
[20:34] <rick_h_> pretty much, you guys should get along great :P
[20:34] <jcsackett> Makyo: i was just saying "have a good evening".
[20:34] <hatch> haha, I like to think we do!
[20:34] <Makyo> Oh!  You too :)
[20:34] <bac> redir: i'm back in the same hangout
[20:35] <jcsackett> thanks. :)
[20:37] <hatch> :'( I hate deleting good code
[20:37] <hatch> wahhhhhh
[20:37] <alexpilotti> hatch rick_h_: nailed it :-) https://github.com/cloudbase/juju-gui/commit/0ead46bdf2aa019e8a0b656ab797f52ce9515a82
[20:38] <hatch> alexpilotti :D
[20:38] <rick_h_> alexpilotti: so if you submit that to core it takes it?
[20:38] <rick_h_> alexpilotti: that's my main concern
[20:38] <hatch> I was pretty sure core would reject it though :)
[20:38] <alexpilotti> rick_h_: testing now
[20:39] <hatch> I hope it doesn't
[20:39] <hatch> that would be pretty nice if it "just works"
[20:39] <alexpilotti> in case either we hack core as well or we just go with a hack
[20:40] <hatch> much hack, so hacky
[20:40] <alexpilotti> hatch: everything is legal for putting a demo together :-) 
[20:40] <bac> abentley: hi, do you have a couple of minutes to help redir and i get a bzr branch unconfused?
[20:41] <abentley> otp.  back at you soon.
[20:41] <hatch> so true, so true, tbh your changes to the front end aren't really hacky at all
[20:41]  * rick_h_ goes afk for a few
[20:44] <alexpilotti> hatch: looks like we have a wiiner by just adding it here: http://bazaar.launchpad.net/~go-bot/juju-core/trunk/view/head:/charm/config.go#L55
[20:45] <alexpilotti> as in: “password”:  schema.String(),
[20:45] <hatch> oh very cool - 
[20:46] <hatch> I suppose a password field in the UI should be able to be toggled visisble
[20:46] <hatch> so it's a bit more work for a real implementation
[20:46] <abentley> bac: Okay, what's going on?
[20:46] <hatch> but it's good to see that it's not a ton more work
[20:46] <alexpilotti> yeah, but still very easy
[20:47] <bac> abentley: can you join our hangout?  https://plus.google.com/hangouts/_/gqzq6ltup6vkgfnqieoltnr74aa?hl=en
[20:48] <abentley> bac: It's says "This party is over.  But you can start a new one."
[20:48] <bac> abentley: sorry, https://plus.google.com/hangouts/_/gqzq6ltup6vkgfnqieoltnr74aa?hl=en
[20:48] <bac> oh, thats the same one.
[20:49] <bac> hmmm
[20:49] <abentley> bac: Can you just invite me?
[20:49] <bac> abentley: done
[20:50] <bac> abentley: reed invited you
[20:53] <Makyo> Hail storm, may lose power.
[20:53] <hatch> Makyo no underground powerlines there?
[20:53] <hatch> or is the hail THAT big ;)
[20:55] <Makyo> Underground in the neighborhood, but the main lines are above ground leading to the neighborhood.
[20:55] <Makyo> And they're notoriously fragile
[20:56] <hatch> ahh yeah that's what it's like here, although not super fragile (depends on the area)
[20:56] <alexpilotti> hatch rick_h_: tx a lot guys! With your help this went really fast!
[20:57] <hatch> alexpilotti happy to help!
[21:17] <abentley> redir: My guess about how 510 happened is that you did "bzr merge ../trunk" and then "bzr revert .".  "revert ." will reset the files but not the merges.  You want "bzr revert" (no dot) for that.
[21:17] <redir> abentley: thanks for your help
[21:19] <hatch> abentley the bzr master
[21:19] <hatch> I think he has a 9th degree bzr black belt somewhere
[21:20]  * hatch whispers to redir "abentley wrote bzr"
[21:26] <abentley> hatch: Well, not just me.  Martin Pool led the project, and I made major contributions like the merge/revert/pull filesystem manipulation.
[21:27] <hatch> so you did all the hard stuff? ;)
[21:29] <abentley> hatch: There was plenty of hard stuff to go around.  The current repository format, for example, uses a mind-melting compression technique by Robert Collins.
[21:29] <hatch> :-) just can't take a compliment 
[21:38] <hatch> hey rick_h_  are you back yet?
[21:56] <hatch__> our test suite is so busted I put a .only on the machine panel view tests and it runs the browser _machine dispatch tests too
[21:56] <hatch__> colour me confused!
[22:10] <rick_h_> hatch: back what's up?
[22:10] <hatch> rick_h_ hey, I'm just writing more tests now, but take a look at my new implementation of the scale up view. I left the DOM manipulation stuff in there so that when it re-renders when the user clicks the 'refresh' button all of their stuff will still be there
[22:11] <rick_h_> hatch: k, sounds like a good plan. Saw the email go by. I like making it depend on the user asking for it
[22:12] <hatch> yeah - I now only pass the serviceList in, and emit an event for adding units
[22:13] <rick_h_> hatch: cool, that sounds nice
[22:13] <hatch> I figured it would, it was your idea :P
[22:13] <rick_h_> :P
[22:13] <hatch> haha, but it was right
[22:13] <rick_h_> hey, we're ending up nicely in the middle, that's a good answer to most problems
[22:14] <hatch> design by committee 
[22:14] <hatch> oh wait
[22:14] <rick_h_> :P
[22:14] <hatch> that's usually a bad thing
[22:14] <hatch> lol
[22:14] <rick_h_> once in a while multiple heads make one smart decision
[22:15]  * rick_h_ runs away now 
[22:15] <hatch> :) cya
[22:15] <rick_h_> alexpilotti: did you end up patching the GUI? Do we need to get a patch in?
[22:15] <rick_h_> alexpilotti: or you have something that works for you for now?
[22:16] <rick_h_> ok, /me really runs now
[22:16] <alexpilotti> rick_h_: for the demo is good, IMO it can also work as the base for a subsequent merge:
[22:16] <alexpilotti> rick_h_: https://github.com/cloudbase/juju-gui/commit/0ead46bdf2aa019e8a0b656ab797f52ce9515a82
[22:17] <rick_h_> alexpilotti: cool, let's make sure to work together on that then. I'd love to see some outside stuff head in and appreciate your willingness to poke through it
[22:17] <alexpilotti> rick_h_: here’s teh corresponding juju-core patch: http://bazaar.launchpad.net/~alexpilotti/juju-core/juju-core/revision/2706?start_revid=2706
[22:17] <rick_h_> alexpilotti: ah cool, did need a small patch there then. Good to konw
[22:17] <rick_h_> know
[22:17] <rick_h_> alexpilotti: <3 you rock
[22:18] <alexpilotti> rick_h_: tx! It was easier then expected! :-)
[22:18] <hatch> it's good to hear the GUI is pretty easy to work on for external contributors 
[22:20] <alexpilotti> it’s a very neat project, indeed
[22:21] <hatch> thanks :) 
[22:21] <hatch> it's come a long way
[22:49] <hatch> rick_h_ if you get a moment the mass scale-up UI changes are done and pushed - if it passes review feel free to shipit
[22:51] <hatch> kadams54 are you around?
[23:06] <huwshimi> Morning
[23:07] <hatch> morning huwshimi 
[23:07] <hatch> huwshimi I'm curious how your branch is coming along and if you had any questions about it. I have to take off soon but would love to see that thing land in the am :)
[23:08] <huwshimi> hatch: Sure, I'll see how I go :)
[23:09] <hatch> shall I check back in later?
[23:10] <huwshimi> hatch: There's still a bunch of work I need to do to get all the updates working correctly and test written.
[23:10] <hatch> ahh ok, well I have to run out for supper for a few hours, so when I get back I'll check back in
[23:10] <hatch> If you don't get it finished mind passing it off to me?
[23:11] <hatch> maybe fire off an email with the details etc
[23:11] <huwshimi> hatch: Sure, will do!
[23:12] <hatch> awesome
[23:28] <huwshimi> hatch: Did you want to merge my last set of changes into your unplaced-units branch?
[23:34] <hatch> umm, which changes are those?
[23:34] <hatch> I've got it up for the final review/qa
[23:35] <hatch> huwshimi mind putting the diff up in a gist?
[23:35] <huwshimi> hatch: Sure.
[23:35] <huwshimi> hatch: It borrows a lot from you branch
[23:36] <hatch> man I'm pissed, I can't find my Three sim card :/ 
[23:37] <huwshimi> hatch: How do I get a diff of all changes in this branch, including uncommitted changes?
[23:38] <hatch> `git diff develop`
[23:38] <hatch> will diff it from develop
[23:38] <hatch> I gota run
[23:38] <hatch> I'll take a look when I get back
[23:39] <huwshimi> hmm... that won't work as develop has changed. I'll figure it out.