[12:32]  * benji reboots
[12:51] <benji> This is the second time I couldn't use -bug with lbox because I get this error: error: ERROR: Failed to update bug task: Server returned 400 and body: milestone_link: Constraint not satisfied.
[12:57] <gary_poster> benji, maybe that would mean something to bac or Curtis?  Sounds registry-related.
[12:57] <benji> It may, I'll check.
[12:58] <bac> it may be the bug isn't linked to a milestone
[12:58] <bac> may be worth looking at a bug that lbox creates and see if it is linked vs the pre-exisint one you're trying to use
[12:59] <bac> on juju-core i don't have permission to manage milestones, priorities, etc on bugs

[13:25] <gary_poster> rogpeppe, great that the next two megawatcher branches landed.  In https://codereview.appspot.com/7727045/diff/5001/state/megawatcher.go  OLD line 13 you deleted a comment that we would need the last revid in the struct.  Is that not true (anymore?), or did you just remove an unnecessary note about the future?
[13:25] <rogpeppe> gary_poster: looking
[13:26] <rogpeppe> gary_poster: it's still TODO. in fact, the revno is added in the next branch in the pipeline
[13:26] <gary_poster> rogpeppe, cool :-) thanks
[13:26] <rogpeppe> gary_poster: BTW even though i've submitted, any comments from yourself would be very welcome.
[13:27] <rogpeppe> gary_poster: i can easily make fixes in upcoming branches
[13:27] <gary_poster> rogpeppe, understood and thanks.  I looked over 241 last night and didn't see anything other than that question.  I'm re-reviewing now and then will look at 242
[13:28] <gary_poster> +1 on change from Remove to Removed in changes btw.  that inconsistency that we introduced bothered me
[13:28] <rogpeppe> gary_poster: cool
[13:29] <rogpeppe> gary_poster: in fact that change was just merging the two Delta implementations which should already have been together, i think.
[13:29] <gary_poster> yeah, I noticed that
[13:29] <gary_poster> did we do that?  sorry, if so
[13:29] <gary_poster> I mean, have two copies of the Delta
[13:30] <rogpeppe> gary_poster: i dunno. somewhere between us, i think.
[13:30] <gary_poster> :-) cool
[13:30] <rogpeppe> gary_poster: it doesn't matter
[13:55] <hatch> morning
[13:57] <Makyo> Herro.
[13:58] <gary_poster> hiya
[13:58] <hatch> after hours of frustration I was able to get my osx > ubuntu vm nfs working
[13:59] <teknico> gary_poster, do we have our call now?
[13:59] <gary_poster> teknico, we do, and I'm even in the chat room now :-)
[14:00] <gary_poster> from calendar
[14:01]  * hatch wonders if gary_poster is always in guichat just hanging out
[14:01] <gary_poster> heh no hatch, just seems that way :-)
[14:02] <hatch> ohh ok ;)
[14:16] <gary_poster> teknico, I lost you again
[14:29] <gary_poster> oops
[14:30] <gary_poster> jujugui call now in guichat
[14:42] <bac> re: "leave your camera home" http://www.nytimes.com/2013/03/04/business/media/photojournalists-in-oakland-face-epidemic-of-camera-robberies.html?pagewanted=all&_r=0
[14:48] <gary_poster> bcsaller, I forgot that we needed the VPN running to see it :-)
[14:48] <gary_poster> the link you gave I mean
[14:50] <bcsaller> yeah, should have mentioned it 
[14:50] <bcsaller> I haven't turned the VPN off since the sprint though
[14:52] <bcsaller> gary_poster: at the bottom of that log is Charm panel False Deploy Button False which is the output of is_displayed on those elements. .click doesn't work when thats false 
[14:53] <gary_poster> :-( gotcha
[14:54] <rick_h_> gary_poster: ping for round 2 
[14:55] <gary_poster> ack rick_h_ .  jujugui, if anyone wants to join discussion with rick_h_ come over to guichat
[15:14] <hatch> so now that I'll be sshing into my vm what shell window manager do you guys prefer? screen?
[15:15] <rick_h_> tmux, the pragmatic programmers book is really good intro.
[15:15] <teknico_> hatch, or byobu if you want a nice wrapper to either of them
[15:18] <hatch> rick_h_: so why tmux over screen?
[15:18] <rick_h_> hatch: so honestly a big part was the book got me over the hurdle for scripting/using it
[15:18] <rick_h_> I can't claim to have ever mastered screen, but my sense is that tmux is more scriptable more easily
[15:19] <rick_h_> so for instance, this is how I work on jujugui: /bin/tgui http://paste.mitechie.com/show/899/
[15:19] <rick_h_> it's scripted startup for a tmux session with 4 windows all setup in the right directory to start work named for function
[15:20] <hatch> oh that's pretty cool
[15:20] <rick_h_> tgui && ta jujugui (aliased in my .zshrc to tmux attach -t) gets me started in my day
[15:20] <gary_poster> "j u j u g u i" pings us all :-)
[15:21] <rick_h_> bah, my apoligies. As someone that doesn't see it I don't realize it. 
[15:21] <gary_poster> np :-)
[15:32] <benji> For future projects we should add an explicit "ping" to the ping-the-world keyword.
[15:33] <hatch> should we though?
[15:33] <hatch> :)
[15:45] <rogpeppe> benji: i just gave you a review. there's one issue we need to solve though. (https://codereview.appspot.com/7554046/diff/1/state/apiserver/api_test.go#newcode404)
[15:45] <benji> rogpeppe: cool, I'll take a look right now
[15:47]  * gary_poster heads to agile meetup lunch.  biab
[16:01] <hatch> rick_h_ you're flying into SFO you said?
[16:01] <rick_h_> hatch: rgr
[16:02] <hatch> I can't fly out of OAK without flying a milk run so I was hoping SFO wasn't too far away
[16:02] <rick_h_> hatch: yea, 55min http://goo.gl/maps/kVzHQ
[16:03] <hatch> oh that should be alright then
[16:04] <rick_h_> hatch: yep, just watch out for time of day. Transit shuts down after 1am and starts around 4am
[16:08] <hatch> ahh]
[16:27] <hatch> so in sshing into my vm and trying to bzr pull I'm given a permission denied error because the keyring is locked (I'm assuming)
[16:27] <hatch> any way I can get that to request a pw?
[16:29] <rick_h_> hmm, it auto does that for me. is python-gnomekeyring installed? `dpkg -l | grep keyring`
[16:30] <hatch> that it is
[16:30] <hatch> it of course works while in the vm via a gui window
[16:30] <rick_h_> yea, I know what you're talking about. I've hit it before but don't recall 'fixing' it. Just it asking for a keyring password the first time and setting it up
[16:31] <rick_h_> abently might know for sure but he's out today
[16:31] <hatch> alright well I'll make a note to research it tonight
[16:31] <hatch> thx
[16:36] <rick_h_> goodspud: ping, any requirements we know about for the charm icons we need to make sure to put to paper in the docs?
[16:37] <rick_h_> goodspud: we're going to require a icon.svg in the charm, so does size/etc matter at that point?
[16:41] <goodspud> rick_h_, svg files should be scalable. We have specific sizes for different presentations of the icons ( 32, 48, 64, 96, 160 ) but if it's a well constructed SVG it should scale to all those sizes
[16:42] <rick_h_> goodspud: ok, if you come across any 'guidelines' we should share with charm authors please let me know so we can make sure we get those into the docs for them.
[16:42] <rick_h_> hatch: speaking of abentley :)
[16:42] <abentley> rick_h_: Hi.
[16:43] <hatch> haha
[16:43] <rick_h_> abentley: hatch was having bzr + keyring issues on a vm he's ssh'd into. Do you have super secret knowledge of how that works? 
[16:43] <rick_h_> abentley: I've always just had it prompt me for a keyring pass and start working
[16:43] <goodspud> rick_h_, our designer (Greg... who hates IRC so you can't ping him) is going to produce a series of style guides and guidelines "at some stage"
[16:44] <rick_h_> goodspud: ok, well we're adding the support and starting to work with charm authors to make sure 13.04 isn't a giant page of 'no icon available' default images. So the sooner the better. 
[16:44] <rick_h_> goodspud: we're working with jcastro to help us work with upstream authors
[16:44] <abentley> rick_h_: I'm not sure what would cause that.  Was this with GPG or SSH?
[16:44] <hatch> I'm ssh'd into the machine
[16:44] <rick_h_> abentley: assuming it's bzr + ssh? hatch, more details?
[16:44] <hatch> yeah I'm ssh'd into the vm
[16:45] <rick_h_> hatch: and what command were you running exacly?
[16:45] <hatch> when I tried bzr pull I got 'permission denied public key'
[16:45] <hatch> `bzr pull`
[16:45] <goodspud> rick_h_, the juju design team has a catch-up meeting tomorrow morning so I'll raise it then
[16:45] <rick_h_> goodspud: thanks! appreciate it. So many moving parts to sync. 
[16:46] <abentley> hatch: Could be a username issue.  Is your username on that machine the same as you normally use?
[16:46] <hatch> nope totally different
[16:46] <hatch> although I ssh'd using my typical username on the vm
[16:46] <goodspud> rick_h_, absolutely. We can't leave our charm authors and Jorge without help
[16:46] <abentley> Are you pulling from Launchpad?
[16:47] <hatch> yes
[16:47] <hatch> I had to go into the vm and bzr pull - it poped up the gui keyring unlock window
[16:47] <hatch> then pulled
[16:47] <hatch> even now I can't bzr pull from the ssh
[16:48] <abentley> hatch: Your LP userid is hatch?
[16:48] <hatch> yes
[16:49] <abentley> hatch: Could you try "bzr info bzr+ssh://hatch@bazaar.launchpad.net/~abentley/bzrtools/bzrtools.dev" please?
[16:50] <hatch> permission denied from the ssh; works from the vm
[16:51] <abentley> hatch: I don't understand.
[16:51] <abentley> hatch: what is "the ssh"?
[16:51] <hatch> my ssh'd terminal window into the vm
[16:51] <abentley> hatch: Okay, did you enable agent forwarding when you sshed?
[16:53] <abentley> hatch: (agent forwarding can be enabled with -A )
[16:53] <hatch> I didn't, just checking the config
[16:53] <hatch> looks like no - let me give that a go
[16:54] <hatch> same error
[16:54] <abentley> hatch: but it works in the VM's terminal window?  Odd.
[16:54] <hatch> yeah that's what I thought haha
[16:57] <abentley> hatch: can you check whether agent forwarding is disabled in the VM's ssh server?  It's "ForwardAgent" in /etc/ssh/sshd_config
[16:57] <hatch> it's commented out
[16:58] <abentley> hatch: uncomment it and set it to yes.
[16:59] <abentley> hatch: Then "sudo service reload ssh"
[16:59] <abentley> hatch: Then log in again with -A
[17:00] <abentley> s/log in/ssh in/
[17:00] <hatch> heh connection refused
[17:01] <hatch> sec ssh might not be running
[17:01] <abentley> hatch: sudo service ssh start
[17:02] <hatch> yeah when I do that it tells me the id  but then when I grep ps all I get is ssh-agent
[17:03] <abentley> hatch: You should be able to see what's going on in /var/log/daemon.log
[17:05] <hatch> when I remove that line it starts working again
[17:05] <hatch> oy
[17:05] <hatch> that file is empty heh
[17:05] <abentley> hatch: Odd.
[17:06] <hatch> yeah this is pretty standard for me - my sysadmin luck is negative
[17:06] <hatch> :)
[17:06] <abentley> hatch: Is the private key also on the vm?
[17:06] <hatch> oh sure - I used to use the VM to code in
[17:07] <abentley> hatch: Could you try sshing into the vm, then using ssh-add to add the key?
[17:10] <hatch> that did it
[17:10] <hatch> :)
[17:10] <abentley> hatch: Okay.  Now we should fix your LP username permanently.
[17:11] <abentley> hatch: I think the simplest way is "bzr lp-login hatch"
[17:11] <abentley> hatch: After that, try ""bzr info bzr+ssh://bazaar.launchpad.net/~abentley/bzrtools/bzrtools.dev" (i.e. without the @hatch)
[17:12] <hatch> that works
[17:12] <hatch> spews out a bunch of auth-agent stuff
[17:12] <abentley> Okay, try your original pull.
[17:12] <hatch> great and we are now working!
[17:12] <hatch> thanks :)
[17:13] <abentley> Good stuff.
[17:13] <abentley> You're welcome.
[17:13] <hatch> can you explain what the issue was?
[17:13] <hatch> as in why the key wasn't being applied by default?
[17:13] <abentley> hatch: The issue was that your SSH username was not "hatch".
[17:14] <hatch> ohh
[17:14] <abentley> hatch: So your key didn't match your username.
[17:15] <hatch> ahh I gotcha that makes perfect sense
[17:15]  * hatch wishes for helpful error messages
[17:15] <hatch> thanks again :D
[17:15] <rick_h_> hatch: got a sec to chat subapps?
[17:15] <abentley> hatch: np.
[17:16] <hatch> rick_h_ see u in guichat
[18:02] <hatch> bcsaller: should I plan on working on the CI tomorrow?
[18:07] <bcsaller> hatch: I am about to propose what I have, I think should go with it, I have the one failing IE test as conditional now
[18:07] <bcsaller> hatch: last two runs were successful
[18:08] <hatch> oh excellent!
[18:16] <gary_poster> great bcsaller.  were you able to isolate the problem to file a bug with selenium?
[18:17] <gary_poster> or come to some other longer term plan?
[18:17] <hatch> jujugui FYI Node 0.10 was released keep an eye out for odd errors in our build processes please :)
[18:18] <gary_poster> uh oh :-) 
[18:18] <bcsaller> gary_poster: at this point I only commented it in the code. I think creating an isolated test might be a good next step, not sure though. 
[18:18] <gary_poster> k
[18:19] <bac> gary is our call in 12 minutes or 60*n+12 minutes?
[18:19] <gary_poster> bac, 11, unless that's a problem
[18:19] <bac> nope, just didn't know if it shifted
[18:19] <gary_poster> cool, yeah
[18:38] <hatch> lunching
[19:10] <hatch> back
[19:12] <hatch> bcsaller: I can assume that this code works as advertised right? You're not going to make me test it are you? :P
[19:12] <gary_poster> lol
[19:12] <bcsaller> funny
[19:13] <hatch> haha
[19:13] <gary_poster> I'll try it :-) at leats in an ec2 environment
[19:13] <bcsaller> I think its possible there are intermittent failures, but the last two runs went fine.
[19:14] <gary_poster> bcsaller, is it trivial for us to have jenkins email us on duccess/fail?
[19:14] <gary_poster> success, even
[19:22] <gary_poster> hatch, where is your doc branch?
[19:23] <hatch> https://code.launchpad.net/~hatch/juju-gui/ci-documentation
[19:23] <gary_poster> ty
[19:27] <rick_h_> curses! mifi hangs when I'm in the middlsle of a lbox propose
[19:31] <bcsaller> gary_poster: didn't see that message but yes, there are outgoing options, email and IRC both maybe configured it looks like
[19:31] <gary_poster> bcsaller, ow that would be great.  trying out the test now on ec2
[19:32] <rick_h_> hatch: jcsackett if you guys get a few min please? https://codereview.appspot.com/7554047
[19:33] <hatch> I'm on it
[19:33] <rick_h_> hatch: ty much kind sir
[19:34] <rick_h_> hatch: if you know how I can make the test more Mock friendly then cool, but failed to see a good way so went full bore with app/subapp objects.
[19:34] <hatch> sure I'll take a look
[19:34] <hatch> I would also like to see these changes reflected in the subapp scaffold branch
[19:34] <hatch> any chance after this lands you can copy/paste the changes there?
[19:34] <rick_h_> ah, ok and this doesn't do anything to the charm yet obviously
[19:35] <rick_h_> hatch: yea, diff isn't too big there at all. 
[19:35] <jcsackett> rick_h_: looking now as well.
[19:35] <rick_h_> hatch: though can't you just merge trunk into the scaffold branch once it lands?
[19:36] <rick_h_> I guess you'd get the browser subapp in there as well, but meh
[19:36] <hatch> yeah I was hoping to keep it 'clean'
[19:36] <hatch> could we merge this commit in?
[19:36] <hatch> I know how to do it in git but not bzr
[19:36] <hatch> :)
[19:37] <rick_h_> h/me wants git cherry-pick :/
[19:38] <rogpeppe> gary_poster: next branch *nearly* ready - one test still to be written (most recent test usefully bailed out some lurking bugs, making me quite happy)
[19:38] <rick_h_> gary_poster: so heads up. I was going to create cards on your board for this config change and for the follow up tweak to the juju-gui charm but I don't have perms. I'm not sure if it matters to you or not?
[19:38] <hatch> rick_h_ darn I saw your merge code and was hoping Y.mix had a blacklist....sadly only whitelist :(
[19:38] <rogpeppe> gary_poster: should be ready by the time you come online tomorrow :-)
[19:38] <gary_poster> rick_h_, will give you perms
[19:38] <rogpeppe> gary_poster: 'cos that's my eod
[19:39] <rick_h_> hatch: yea :(
[19:39] <gary_poster> rogpeppe, awesome!  Will be out tomorrow but will check
[19:39] <bac> hatch: what are you trying to do?
[19:39] <hatch> bac: merge two objects witch a blacklist of property names
[19:40] <bac> i don't understand
[19:40] <bac> this is a bzr problem?
[19:42] <hatch> nope
[19:42] <rick_h_> bac: no, just I've got an update he wants in a side branch he doesn't want to pull all of trunk into
[19:43] <bac> hatch: you could just merge the specific revision from rick_h_'s branch...  but i'm sure you know that.  nm.
[19:44] <hatch> that's what I meant, I know how to do that in git, I don't know how in bzr....YET!
[19:44] <rick_h_> bac yea, I figure I'll do a patch and apply it to his branch
[19:44] <gary_poster> rick_h_, you and orange have perms
[19:44] <rick_h_> bac: I didn't think bzr supported a 'cherr-pick-like' single commit merge
[19:44] <rick_h_> gary_poster: thanks, will add cards on your board as well then. 
[19:44] <gary_poster> cool
[19:45] <bac> from 'bzr help merge': To merge the changes introduced by 82, without previous changes:
[19:45] <rick_h_> gary_poster: this is all story1 stuff? /me isn't caught up on the board terminology
[19:45] <bac>         bzr merge -r 81..82 ../bzr.dev
[19:45] <rick_h_> bac: cool, will try it
[19:46] <gary_poster> rick_h_, sorry this is for orange?  you would be maintenance for us (top lane).  Maybe we should have separate lane for orange stuff.  I'm on call, so let's talk about after
[19:46] <rick_h_> gary_poster: k, going to EOD but yea it's adding features to subapp for our use
[19:47] <gary_poster> rick_h_, ok top lane
[19:47] <rick_h_> gary_poster: rgr, thanks
[19:48] <rick_h_> thanks jcsackett. 
[19:48] <jcsackett> rick_h_: yw.
[19:48] <rick_h_> hatch: packing up for EOD but will look at any comments later tonight. Thanks for looking things over. 
[19:48] <hatch> np thanks for writing that
[19:49] <hatch> bac: excellent
[19:49] <rick_h_> bah, camel case. retraining is hard
[19:49] <hatch> rick_h_ lol the funny part is half of your stuff IS camelCased haha
[19:57] <rick_h_66> I'm trying! 
[19:59] <jcsackett> hatch: it's still unatural to camelcase variables. that's for method names. :-P
[19:59] <hatch> jcsackett: yeah when I was writing python at the sprint I was always going back and adding in _ haha
[19:59]  * jcsackett laughs
[21:05] <gary_poster> hatch, I reviewed https://code.launchpad.net/~hatch/juju-gui/ci-documentation/+merge/153165 .
[21:05] <gary_poster> make some changes, get one more reviewer, and you have a landing. :-)
[21:05] <hatch> thank yous
[21:05] <hatch> :)
[21:06]  * gary_poster is tired
[21:06]  * hatch hands gary a coffee
[21:06] <gary_poster> so long folks!  Have a great Friday and weekend!  See you Monday
[21:06] <gary_poster> :-)
[21:06] <hatch> you too!
[21:06] <gary_poster> thanks
[22:15] <m_3> gary_poster: hey, do y'all have a team review process before changes land in lp:~juju-gui/charms/precise/juju-gui/trunk?
[22:15] <m_3> gary_poster: or is the charm review-queue the first review pass on anything
[22:16] <m_3> doh, just read backscroll
[22:16] <m_3> gary_poster: nm... catch you on the flipside
[22:24] <benji> m_3: yes, we do reviews of the charm; the "Checklist for Preparing for a Review" section of https://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/docs/process.rst largely applies
[22:24] <m_3> benji: thanks!
[22:26] <benji> np