[12:48] <bac> hi frankban, thanks for the great review!  i've reproposed and would like if you'd give a look, especially to the url encoding bits.  https://codereview.appspot.com/26740043
[13:09] <gary_poster> rick_h_, hey.  Dunno if hatch will be around today (sick).  If it gets later with no reply from him on your branch, please ask around for someone else to follow up.
[13:11] <gary_poster> rick_h_, I also can give answer to hatch's last question, if desired
[13:14] <rick_h_> gary_poster: ok will do. It needs two reviews and he was generally cool with things and said he was debating a LGTM but wan't to check on using deltas
[13:14] <rick_h_> gary_poster: so I'll rope someone in for a second review/QA while I tinker with it per hatch's review 
[13:14] <gary_poster> ok cool
[13:15] <rick_h_> gary_poster: if you know the 'why' for hatch appreciate the reply. (and I can see as well) 
[13:15] <gary_poster> can be roped if desired, though I have interruptions for next hour or so
[13:15] <gary_poster> ok will reply
[13:15] <rick_h_> gary_poster: rgr, thanks
[14:04] <frankban> bac: looking
[14:06] <rick_h_> jujugui updated per hatch's review and looking for a second review/qa please https://codereview.appspot.com/26290043/ 
[14:06] <hatch> morning
[14:06] <hatch> still sick, but not enough to miss :)
[14:07] <rick_h_> hatch: chicken noodle soup for your lunch today, rock on
[14:07] <frankban> hatch: we are two
[14:09] <hatch> yup
[14:09] <hatch> I had to dig in the freezer for some
[14:09] <rick_h_> you mean the back porch? :P
[14:10] <hatch> lol it's not QUITE cold enough every day for that
[14:10] <rick_h_> we had -7C the other day. Getting cold too early this year
[14:10] <hatch> woah! I had no idea it got that cold there
[14:11] <rick_h_> yea, we get down into some negative F range pre-wind chill
[14:11] <rick_h_> but that's usually more Jan weather than mid-nov
[14:11] <rick_h_> shoot, had our first snow before all the leaves fell 
[14:14] <hatch> frankban: out of curiosity why can't guiserver receive a 'watch' rpc call from the gui and then send 'fake' deltas down the wire which we can react to? Why do we have to essentially long-poll for them instead?
[14:15] <hatch> rick_h_: I LGTM'd I'm still not sold on the util object vs class but I'll let it go ;)
[14:16] <rick_h_> hatch: rgr, did you see my point though that there will never be more than one 'instance' since that data is the same? I think that's what led me more utils vs object
[14:16] <hatch> yeah so I was thinking in that case it could be an extension on another clas....like say....app :)
[14:16] <rick_h_> hatch: well that and just refactoring the methods didn't have an object to start (well it was an extension, but on their own)
[14:16] <rick_h_> hatch: :P right but then you need a 'fake app' to test and such. Ugh
[14:17] <rick_h_> hatch: but I admit it's something that can go a few diff ways without being too crazy
[14:17] <hatch> no no, you can just var myext = new MyMyExtension()
[14:17] <hatch> yeah that's why I didn't argue over it :)
[14:17] <rick_h_> hatch: except this.env doens't exist in new MyMyExtension
[14:17] <hatch> implementers choice....for now!
[14:17] <rick_h_> wheee! I won the joy of this lovely branch with all the live ec2 QA/testing work yay me
[14:17] <hatch> myext.env = envStub;
[14:18] <hatch> :P
[14:18] <rick_h_> bah, invisible properties to the test reader then "what's this 'magic' attribute'
[14:18] <rick_h_> go get your soup early
[14:18] <frankban> hatch: no technical reasons, just a design decision. we decided to reuse a pattern already present in juju-cure (the megawatcher) and to not introduce a new one. Even if it feels more natural to just push changes from the server, the more I think about it the more I feel we made the right decision, especially considering that the deployer can eventually be implemented in core.
[14:19] <rick_h_> gotta love how things to first written and depoyed in python to get re-written in go down the road potentially
[14:19] <hatch> frankban: does the 'longpolling'  introduce any potential performance/race conditions or is it simply a flag on the guiserver side that says 'when this comes up, notify the user here'
[14:19]  * rick_h_ wishes the config-changed hook to go faster...faster
[14:20] <rick_h_> hatch: think node-like :P
[14:21] <gary_poster> the latter, hatch
[14:23] <hatch> ahh cool cool
[14:24] <frankban> hatch: it's longpolling-like but in the same connection, so I don't see too much performance degradation. It just mimics a request/response over a wss connection. If races are discovered, that's a bug. In theory, when the client calls Next, it receives all the messages not yet received if there are, otherwise the next new event when it is generated
[14:26] <hatch> sounds good
[14:26] <hatch> I was mostly curious
[14:26] <hatch> rick_h_: is someone else doing the qa on your branch or would you like me to?
[14:26] <rick_h_> hatch: I was hoping to rope Makyo into the second review and qa, but if you've got bandwidth to qa would appreciate it
[14:27] <rick_h_> hatch: not sure what your live juju env is looking like these days
[14:28] <hatch> I have a juju core instance locally for lxc and setup for ec2
[14:28] <rick_h_> hatch: ok cool, this is only for ec2-land so if you can qa would appreciate it
[14:28] <rick_h_> hatch: tried to put some cut/past instructions on there and note the various code paths
[14:29] <hatch> on it
[14:29] <rick_h_> still working on a success for all 4 paths myself with various bundles
[14:29] <rick_h_> keep finding new bugs or corner cases in things 
[14:34] <gary_poster> hey frankban, I copied quickstart over to ppa:juju/stable yesterday
[14:35] <gary_poster> I think maybe "releasing" it can be copying it over from the beta ppa?
[14:35] <gary_poster> going forward as a process I mean
[14:35] <gary_poster> what do you think?
[14:35] <rick_h_> jcastro: used it for his blog post yesterday http://www.jorgecastro.org/2013/11/14/from-0-to-hero-in-a-few-minutes/
[14:36] <jcastro> yes, mwahaha, you can't remove it now
[14:37] <rick_h_> lol, trapped by a blog post
[14:37] <gary_poster> :-) cool
[14:37] <hatch> haha
[14:38] <hatch> jcastro: hey do you know anyone who knows nginx really well? I'd love it for the http interface for my ghost charm :)
[14:38] <jcastro> we used to
[14:38] <frankban> gary_poster: cool thanks, sounds good. 
[14:38] <jcastro> he did the setup in the wordpress charm
[14:38] <gary_poster> great
[14:39] <jcastro> hatch, is just straight up theft from wordpress not feasible?
[14:39] <hatch> not sure I haven't looked into it
[14:39] <hatch> I just figured we needed an nginx charm
[14:39] <hatch> there are some, but none are promoted
[14:43] <rick_h_> woot, it's working. Double bundle deploys, one is scheduled. party on
[14:43] <frankban> bac: thanks for the changes, just added a comment. do you have an example charmworld URL to use to wwatch deployments count?
[14:43] <hatch> :)
[14:44] <bac> frankban: can't yet as juju gui and quickstart aren't sending them yet
[14:44] <bac> frankban: i mean they are not yet sending the optional BundleID so it doesn't get triggered
[14:45] <bac> frankban: i'll probably update the GUI today to do that
[14:46] <frankban> bac: ack
[14:47] <bac> frankban: so i think the best QA is just deploying a bundle and seeing that nothing blows up.
[14:47] <rick_h_> bac: my branch plays around with that stuff so watch out 
[14:47] <frankban> bac: I'll check the guiserver logs
[14:47] <rick_h_> bac: the good thing is that the deployBundle call takes a 'name' parameter that it looks like no one uses, just passes null
[14:48] <rick_h_> sweet, "bundle 1 completed" "bundle 2 starting"
[14:48] <frankban> rick_h_: the gui will use it once we have bundle disambiguation I guess
[14:48] <rick_h_> frankban: oh! that's what the name is for
[14:49] <rick_h_> frankban: makes sense. I was going to bring up that gary_poster should add that to his list of 'bundle features needed' as well
[14:49] <gary_poster> rick_h_, ack.  added
[14:50] <gary_poster> ty
[14:52] <frankban> bac: is you branch merged with ~juju-gui trunk?
[14:52] <bac> frankban: which branch?
[14:53] <frankban> bac: lp:~juju-gui/charms/precise/juju-gui/trunk/
[14:53] <bac> frankban: are you asking if i've pulled the latest changes from the charm trunk into my branch?  no, i haven't
[14:53] <bac> frankban: i'll do that and make sure there are no conflicts and tests pass.
[14:54] <frankban> bac: thanks, then I'll QA
[14:58] <luca__> how is everyone/everything today? All going good?
[14:58] <rick_h_> hatch: actually, nothing here should be ec2 specific. I was using quickstart to initially bring things up and that required ec2. 
[14:58] <hatch> oh now you tell me
[14:58] <rick_h_> hatch: but that speed is offset by the other changes. Sorry to lead you to ec2 there 
[14:58] <rick_h_> hatch: heh, yea I got thinking "why did I have to dothis on ec2?" 
[14:59] <rick_h_> but hey, I got some good qa notes/bugs on ec2 yesterday/today :)
[14:59] <gary_poster> hey luca__ .  all good.  releases have gone well to good reaction.  I have some jaas thoughts I want to share with you and ale before Tuesday on what we think we ought to start with next for jaas (hint: we think our previous plans are still necessary for jaas)
[15:00] <luca__> gary_poster: cool, we should schedule something for Monday
[15:00] <gary_poster> agree
[15:01] <hatch> rick_h_: updated status for deployment: 0
[15:01] <hatch> that is kind of...odd
[15:01] <hatch> like what's the 0 for?
[15:01] <bac> frankban: merged, unittests pass, pushed
[15:01] <rick_h_> hatch: yea, I'm hoping with the naming /id stuff bac is doing we can make that nicer
[15:01] <rick_h_> hatch: it's the deployment id, we don't have anything else to call it
[15:01] <rick_h_> hatch: but you can do parallel imports so we have to be able to tell notifications apart
[15:02] <gary_poster> luca, you and ale only have 4:30-5:00 Monday.  Will schedule.
[15:02] <hatch> how about "Updated status for deployment id: 0"
[15:02] <hatch> :)
[15:02] <gary_poster> luca__, I should say :-P
[15:02] <rick_h_> hatch: I like small edits :)
[15:02] <hatch> haha, just wait, it's still running, there may be more
[15:03] <luca__> gary_poster: ok
[15:03] <rick_h_> hatch: all good, thanks for trying it
[15:03] <luca__> gary_poster: add Peter too if you think he should be there
[15:03] <gary_poster> luca__, he won't be at Tuesday meeting will he?
[15:03] <gary_poster> prep for that is what this is about in my book
[15:03] <gary_poster> aligning among ourselves
[15:04] <gary_poster> I wonder if I should give you a preview today so you can warn others if you think it is necessary :-)
[15:04] <luca__> gary_poster: he won't be at the tuesday meeting
[15:04] <gary_poster> ok
[15:04] <gary_poster> luca__, you have 30 min today sometime?
[15:05] <hatch> rick_h_: so both discource and postgres dropped onto the canvas almost right away and I only saw a single notification
[15:05] <luca__> gary_poster: sure, I'm in a cloud installer call from 4-5 but I can jump on after that
[15:05] <hatch> bug?
[15:05] <gary_poster> luca__, isn't that your EoD?
[15:06] <luca__> gary_poster: sort of, it's ok though
[15:06] <rick_h_> hatch: right, but they're still loading right? not green
[15:06] <frankban> bac: please fix a lint error introduced by your last change
[15:06] <hatch> postgres turned green without a notification
[15:06] <hatch> still waiting on discourse
[15:06] <gary_poster> ...ok luca__ I'll schedule and try to make it fast :-)
[15:06] <bac> gah
[15:06] <rick_h_> hatch: right, it'll wait until it's done and relations are done to say it's completed
[15:07] <rick_h_> hatch: there's not a ton of updates unless it errors then you get a notification the instant things error
[15:07] <rick_h_> otherwise it's "Started" ....wait a bit ... "Completed"
[15:07] <luca__> gary_poster: :)
[15:07] <hatch> ohh ok, I was under the impression that it had one on each machine being spun up
[15:07] <rick_h_> hatch: if you deploy another one right now you'll get notified it's "scheduled" and then when the first bundle is done it'll to go "Started" and then "completed"
[15:07] <hatch> but that wouldn't make any sense
[15:07] <hatch> because you can see it in the canvas
[15:08] <rick_h_> hatch: yea, it's more of a 'how is my bundle doing' state and the big thing was that errors would fall silently so this is providing a "Did it work or fail" summary notification
[15:08] <frankban> hatch: yeah it would be like having subtitles
[15:08] <rick_h_> lol, "Juju Gui, now with french sub-titles"
[15:08] <frankban> :-)
[15:08] <jcastro> hey rick_h_, I forgot to ask yesterday, the ability to deploy --to in a bundle? Is that v2? or v3? 
[15:08] <jcastro> I want to have an all  in one discourse instance, including gui/bootstrap
[15:09] <rick_h_> jcastro: so that should owrk from the deployer now. Not sure what's up with that on the quickstart front. frankban on the radar?
[15:09] <hatch> discourse sure takes a while to spin up
[15:09] <jcastro> yeah I know it works with proper deployer
[15:10] <gary_poster> jcastro, shoudl work from deployer now, yes.  won't be visible or changeable in GUI though.  When that changes is currently up for debate.
[15:10] <rick_h_> hatch: yea, it's got to pull the world of ruby from gems, github, etc
[15:10] <jcastro> but now that I have quickstart I want to point people towards that instead of "raw" deployer
[15:10] <bac> frankban: done
[15:10] <hatch> oh jeebus I forgot it was ruby
[15:10] <gary_poster> lol
[15:10] <hatch> ruby.....because python wasn't....we've got nothing
[15:10] <gary_poster> lol
[15:11] <rick_h_> gary_poster: yea, but quickstart could support it even though the gui doesn't have a representation
[15:11] <hatch> haha
[15:11] <jcastro> hatch, man you want a good time, you think that's bad ... deploy the cloudfoundry bundle and debug-log that
[15:11] <gary_poster> rick_h_, yeah, was agreeing with you on that.
[15:11] <jcastro> rick_h_, I was thinking more from a "just ignore that section and pass it on to deployer"
[15:11] <hatch> haha
[15:12] <jcastro> that way we could do "all in one" bundles for people to deploy and just say "they don't show up in the gui properly but we'll fix that later."
[15:12] <gary_poster> yeah, think that works now
[15:12] <frankban> jcastro: quickstart deploys bundles using the guiserver, which then uses the last deployer version. so it should work
[15:12] <jcastro> also, I had this crazy dream trying to figure out a nickname for bundles that are all in ones, instead of "one shots" as I've been calling them
[15:12] <rick_h_> frankban: oh, whenI looked at the source the --to was a special flag picked up by code the guiserver path wasn't using
[15:12] <jcastro> I'm going to start calling them happy meals.

[15:13] <jcastro> self contained, all in one boxes.
[15:13] <jcastro> I knew you'd get a kick out of that
[15:13] <gary_poster> :-)
[15:13] <rick_h_> where's my toy!
[15:13] <jcastro> frankban, ok I'll give it a shot now
[15:14] <jcastro> how is --to documented in the bundle file?
[15:14] <frankban> jcastro: cool, let me know how it goes. rick_h_: I am referring to http://pythonhosted.org/juju-deployer/config.html#placement
[15:14] <jcastro> so to: 0
[15:15] <jcastro> should work?
[15:15] <frankban> jcastro: give it a try
[15:15] <frankban> (never used myself)
[15:16] <jcastro> hey bac
[15:17] <jcastro> did you guys ever finish off that bundle doc and hand it off to nick?
[15:17] <jcastro> we should probably land that soon
[15:17] <jcastro> I can finish it off today if you'd like
[15:17] <frankban> bac: deploying
[15:17] <bac> jcastro: i spoke to nick about your comments and he said he'd take care of it
[15:17] <bac> jcastro: probably last week
[15:18] <hatch> ya know I just read a blog post yesterday about why distributing ruby apps suck....now I see why first hand
[15:18] <hatch> lol
[15:18] <jcastro> ok I'll chase him down, thanks
[15:19] <hatch> rick_h_: install hook failed on discourse and I didn't get a notification
[15:20] <rick_h_> frankban: ah, you're right. I was confused back when I missed the juju-client has machine_spec
[15:20] <rick_h_> hatch: hmmm, no notification that the bundle errored?
[15:21] <hatch> nope
[15:21] <hatch> and clicking retry in the gui doesn't appear to do anything....
[15:21] <jcastro> frankban, it didn't error out
[15:21] <jcastro> but it also didn't to: 0, fired up individual instances
[15:21] <jcastro> also, whoever make "juju quickstart ." work, thank you!
[15:21] <rick_h_> hatch: hmm, yea I just noticed that resolve issue on aonther bundle where I did get the error
[15:22] <rick_h_> hatch: can you try another bundle, the wordpress-simple or the mediawiki one?
[15:23] <hatch> yup
[15:23] <hatch> also found a sidebar bug haha
[15:23] <rick_h_> hatch: thanks, I'll try out the discourse onein particular. 
[15:23] <rick_h_> sidebar bug?
[15:24] <hatch> when I opened the unit details it was under the sidebar
[15:24] <hatch> so I closed it
[15:24] <rick_h_> yea, that's intentional
[15:24] <hatch> now I opened it and it no longer has the 'jorge' search results
[15:24] <rick_h_> oh hmm, lovely
[15:24] <hatch> oh well....once fullscreen is gone we can hopefully rely on the yui routing
[15:25] <frankban> hatch, rick_h_ : the deployer can take some time before returning a hook error
[15:26] <rick_h_> frankban: k
[15:26] <jcastro> frankban, should I file a bug?
[15:26] <rick_h_> frankban: yea, I noticed a small lag, but it's purely a wait/see
[15:27] <frankban> jcastro: investigating
[15:27] <rick_h_> hatch: filed the bug on the resolved button
[15:28] <hatch> rick_h_: haha I filed one on retry
[15:28] <rick_h_> doh
[15:28] <hatch> rick_h_: ok I deployed the wordpress bundle it had the 'started' message
[15:28] <hatch> then say....5-10s later it had the 'completed' message
[15:28] <hatch> but both are still yellow
[15:29] <rick_h_> hatch: what ID was that for?
[15:29] <hatch> 1
[15:29] <hatch> both were for 1
[15:29]  * rick_h_ wonders if that was bundle 0
[15:29] <rick_h_> hatch: it said completed? not scheduled and started?
[15:29] <hatch> it said started, then completed
[15:29] <hatch> no scheduled
[15:30] <hatch> so it must think that the discourse one is done? but didn't notify
[15:30] <rick_h_> hatch: yea, if it started the second then it's killed off the first one
[15:30] <hatch> sounds like a bug
[15:30] <hatch> not sure from which end though
[15:30] <hatch> this is tough to debug
[15:30] <hatch> :)
[15:30] <rick_h_> yea, it's been a tough branch to do
[15:31] <hatch> no console errors or anything
[15:31] <rick_h_> and now you're kiling my joy in testing it ok this morning
[15:31] <hatch> well I'm going to start on my 'fail testing charm' and bundle
[15:31] <rick_h_> no console in the charm (and I tried to turn that on) 
[15:32] <rick_h_> gah! /me starts up another ec2 env
[15:32] <hatch> rick_h_:  here is the retrying bug https://bugs.launchpad.net/juju-gui/+bug/1251664 so you can relate it to your bug
[15:32] <_mup_> Bug #1251664: Retrying doesn't appear to do anything <juju-gui:New> <https://launchpad.net/bugs/1251664>
[15:32] <rick_h_> hatch: yea, done. I marked mine  a dupe of that and figure they'll go together
[15:32] <hatch> rick_h_: so I'm going to tear this ec2 instance down, cool? or do you need anything from it?
[15:33] <bac> frankban: so did your deploy and QA complete?
[15:33] <rick_h_> hatch: yea, kill it. I'll run again here. You did hte discource bundle first and then wordpress right?
[15:33] <hatch> yeah
[15:33] <hatch> and the discourse charm failed
[15:33] <rick_h_> hatch: I swear it worked here, but I did different bundles in a different order
[15:33] <rick_h_> I had a different charm fail and such
[15:33] <rick_h_> hatch: rgr
[15:33] <hatch> ohh ok
[15:33] <hatch> well I'm going to write a charm which fails so we can test these things
[15:34] <rick_h_> hatch: rgr
[15:34] <hatch> destroy-environment should have like 3 levels of 'are you sure?'
[15:34] <hatch> which gets more dramatic each time
[15:34] <hatch> "are you sure you want to destroy your environment"
[15:34] <hatch> "all of your data will be lost forever"
[15:35] <hatch> "lost into the deep dark abys that is unallocated memory never to be seen or heard from again, can you really do that to such innocent data"
[15:36] <frankban> jcastro: maybe I've found the problem. hazmat: ping
[15:37] <frankban> jcastro: to double check, could you please try to deploy with "to: '0'" (quoted)
[15:38] <jcastro> got it
[15:44] <jcastro> frankban, that worked
[15:47] <hazmat> frankban, jcastro ack, in meeting, noted re bug
[15:47]  * jcastro nods
[15:47] <frankban> jcastro: ok, thank you, we will need another release of the deployer and of the charm to fix that. in the meanwhile, I think it's fine to use quotes there
[15:47] <jcastro> ok so now with to: and constraints: I am good to go
[15:48] <frankban> jcastro: cool
[15:48] <jcastro> frankban, yeah for now I'll leave the current discourse one in the store and create a different all in one
[15:48] <jcastro> discourse-happymeal <--- just kidding
[15:50] <Makyo> jujugui call in 10
[15:54] <frankban> bac: AttributeError: 'Deployer' object has no attribute 'charmworldurl'. w eboth missed that, used without the underscore in _import_callback
[15:54] <bac> frankban: thanks
[15:55] <frankban> bac: and so I guess that "if" is the only part of that branch code that's not covered
[15:58] <gary_poster> jujugui call in 2
[16:29] <hatch> frankban: before you take off for the day I have a couple questions about Go for my talk tomorrow
[16:29] <frankban> hatch: now is ok
[16:30] <hatch> https://plus.google.com/hangouts/_/calendar/Z2FyeS5wb3N0ZXJAY2Fub25pY2FsLmNvbQ.t3m5giuddiv9epub48d9skdaso?authuser=1
[16:30] <hatch> it'll be really quick :)
[16:31] <rick_h_> lies! don't be fooled frankban 
[16:38] <hatch> lol
[17:15] <benji> I have a charmworld branch up with some refactorings needed for my current work.  I added some comments for the reviewer to make it easier to see what is going on: https://codereview.appspot.com/22190049/
[17:37] <gary_poster> unfortunately reviewer comments don't migrate across patch sets
[17:37] <benji> jujugui: charmworld branch up for review: https://codereview.appspot.com/22190049/  I added some comments for the reviewer to make it easier to see what is going on.
[17:38] <hatch> gary_poster: nope they don't :(
[17:38] <gary_poster> benji will look later if no o ne else takes you up on it :-)
[17:38] <benji> thanks
[17:42]  * rick_h_ curses npm!!!!!!!!!!!!!
[17:46] <hatch> it's down again eh?
[17:46] <rick_h_> yea, so juju set juju-gui-source is full of fail for QA
[17:47]  * rick_h_ takes this branch out to the shed out back
[17:48] <hatch> I've always wondered where that saying comes from
[17:48] <hatch> it would make a mess of the shed
[17:54] <rick_h_> https://twitter.com/npmjs/status/401406454088732672 guess it's coming back wheee
[18:02] <rick_h_> jujugui is manage.jujucharms.com not responding for anyone else?
[18:02] <bac> wfm
[18:02] <rick_h_> bac: ok, thanks
[18:04] <rick_h_> heh, it completed after 1.7M 
[18:15] <rick_h_> hmm, looks like it's something in the inter-tubes http://www.downforeveryoneorjustme.com/manage.jujucharms.com shows it as down as well
[18:16] <rick_h_> hatch: aha! you didn't get the error because there was no error message in the websocket
[18:16]  * rick_h_ goes to check branch and see what to do about a completed with error without a message
[18:51] <gary_poster> benji reviewing
[18:53] <bac> jujuguipals: charmworld review please https://codereview.appspot.com/23330046
[18:53] <gary_poster> benji LGTM
[18:54] <gary_poster> bac reviewing
[18:54] <gary_poster> will not do qa though
[18:54] <bac> gary_poster: you are a reviewing machine
[18:54] <gary_poster> :-)
[18:54] <bac> well, ok then
[18:54] <benji> gary_poster: thanks
[18:55] <gary_poster> welcome
[18:58] <gary_poster> bac, I'm wondering about edge cases for that new search behavior.
[18:58] <gary_poster> bac, for instance, what if I type ~gary demo?
[18:58] <gary_poster> I'd be looking for Gary's demo
[18:59] <gary_poster> Is there some autocomplete rule I should be aware of?
[18:59] <gary_poster> Since the autocomplete is now GUI's only search tool...
[18:59] <gary_poster> it would ne nice if it had the features that m.j.c search had
[18:59] <gary_poster> maybe (?)
[18:59] <bac> well the old autocomplete rule was you'd get a 'name: text' search
[19:00] <gary_poster> I have another call
[19:00] <gary_poster> bac, yeah, we can separate that out into another card/branch for The Future
[19:00] <gary_poster> but
[19:00] <gary_poster> at the least
[19:00] <bac> brb
[19:00] <gary_poster> ok
[19:05] <rick_h_> hatch: got a sec?
[19:07] <hatch> rick_h_: yup
[19:09] <rick_h_> hatch: https://plus.google.com/hangouts/_/7acpi4rj1mataa0gd8t6esan2g?hl=en
[19:19] <gary_poster> bac ping me when you have a sec for a call.  comments will go faster there and you can beat me over the head more readily
[19:20] <bac> gary_poster: now?
[19:20] <gary_poster> cool
[19:21] <bac> gary_poster: ringing
[19:24] <rick_h_> hatch: ok, they both errored here. With crappy error boxes because they've got no error message. However, that's a fix for another branch in another project of code
[19:24] <rick_h_> hatch: let me know what you get and then Makyo can just review if he gets a chance and get this landed
[19:25] <hatch> sounds like a plan - the gui is almost up
[19:28] <Makyo> Will do
[19:29] <hatch> well I THOUGHT it was almost up
[19:30] <hatch> lol
[19:30] <hatch> lxc's apparently take a long time to start
[19:35] <rick_h_> should only the first time you launch your first one
[19:35] <rick_h_> after that it's fast!
[19:38] <hatch> rick_h_: when you say 'fast' like <1m?
[19:38] <rick_h_> hatch: my lxc units pull up in < 2min 
[19:39] <rick_h_> bootstrap is < 1min and juju deploy juju-gui is < 2 or 3
[19:39] <hatch> hmm yeah mine is definitely longer
[19:39] <rick_h_> now setting the branch takes a bit, 10 maybe?
[19:39] <hatch> ~15m total for the gui
[19:40] <hatch> http://www.indiegogo.com/projects/linux-voice
[19:40] <hatch> looks interesting
[19:41] <hatch> unfortunately the price in GBP is a little craycray
[19:41] <hatch> will be over $100/yr for me :(
[19:46] <hatch> yeah I think these lxc's are running at 10m
[19:46] <hatch> maybe it doesn't do multiple lxc creation at once very well
[19:49] <hatch> rick_h_: well it has staged up the bundle properly so yay
[19:50] <bac> gary_poster: i was so proud of my tilde-matches-owner test with bonnie and clyde.  next time.
[19:51] <gary_poster> bac, :-) sorry
[19:56] <hatch> oh c'mon discourse fail already so I can qa ok this!
[19:58] <hatch> yay
[19:59] <rick_h_>  error notification this time?
[19:59] <hatch> uh oh
[19:59] <rick_h_> no, no uh oh allowed
[19:59] <rick_h_> there's no message, that's the known issue part. 
[19:59] <hatch> https://plus.google.com/hangouts/_/7acpjifot1t4vf39qmvgc5if18?hl=en
[20:00] <hatch> ^ rick_h_
[20:01] <rick_h_> yayayayyaay. Makyo so hatch has QA and we're good. 
[20:02] <Makyo> Coolcool,
[20:21] <Makyo> \o/
[20:45]  * bac off to festivities.  have a good weekend.
[20:45] <hatch> you too
[20:45] <hatch> enjoy
[21:06] <gary_poster> bye bac
[21:06] <gary_poster> benji, are you outta here also?
[21:06] <gary_poster> or do you have another hour?
[21:08] <benji> gary_poster: I'm pretty much outta here :)  Did you have something in particular?
[21:08] <gary_poster> benji, cool.  wanted to run a document past you.  it'll wait.  have a great weekend!
[21:08] <benji> gary_poster: something to look forward to
[21:08] <gary_poster> ;-)
[22:05] <hatch> gary_poster: email lgtm :)
[22:05] <gary_poster> hatch, :-) thanks
[22:05] <gary_poster> feel better hatch
[22:06] <gary_poster> have a great weekend everyone
[22:06]  * gary_poster waves
[22:06] <hatch> thanks, you too cya
[23:08] <bac> hatch you still here all by yourself?
[23:08] <rick_h_> heh, hatch can't leave! Moar branches!