[00:22] <gary_poster> hey huwshimi.  I tried to tweak some text in your branch.  Lemme get it up, one sec.
[00:27] <huwshimi> gary_poster: Is this for the interfaces tab?
[00:27] <huwshimi> (now related charms)
[00:28] <gary_poster> huwshimi, hadn't gotten to that.  was on features
[00:28] <huwshimi> ah right
[00:32] <hatch> rick_h: still around?
[00:32] <rick_h> hatch: kinda
[00:32] <hatch> I'm trying to start up tmux with a config but it appears to be ignoring the tmux.conf
[00:33] <hatch> my startup command is `gnome-terminal -e tmux --maximize`
[00:33] <rick_h> hatch: it's .tmux.conf?
[00:33] <hatch> it is
[00:33] <rick_h> and in your ~ dir?
[00:33] <hatch> if I go `tmux source-file .tmux.conf` once it starts
[00:33] <rick_h> so start a terminal (gnome-terminal)
[00:33] <hatch> then it executes it properly
[00:33] <rick_h> and then `tmux` and see if you get any errors?
[00:34] <hatch> well I'm in tmux
[00:34] <hatch> `-e tmux`
[00:34] <hatch> actually if I do that again
[00:34] <rick_h> hatch: right, just wondering if launching it that way isn't displaying some error in the conf file
[00:34] <hatch> it also doesn't open it
[00:34] <hatch> ohh
[00:38] <hatch> ahh there we go
[00:38] <rick_h> cool
[00:38] <hatch> I had a detached session
[00:39] <hatch> so it wasn't re-loading it
[00:39] <hatch> sorry to bother :)
[00:39] <rick_h> gotcha, cool
[00:41] <hatch> trying to figure out how to make a real shortcut for ctrlp
[00:41] <hatch> having to type :CtrlP is a little excessive
[00:42] <rick_h> hatch: ctrl-p should do it
[00:42] <rick_h> unless you've got something else on the keymapping
[00:43] <hatch> yup I had
[00:43] <hatch> fixed
[00:43] <hatch> heh
[00:44] <gary_poster> huwshimi, https://codereview.appspot.com/12734043/ LGTM with comments, only one of which might be annoying to address
[00:45] <huwshimi> gary_poster: Thanks, I'll take a look
[00:45] <gary_poster> Thanks huwshimi.  I won't be around (hopefully!) so if you need to make a change to what I've done, consider yourself to have received a blanket blessing. :-)
[00:46] <huwshimi> gary_poster: Thanks :)
[00:46] <hatch> don't worry, I'll be back in a couple hours
[00:46] <hatch> so I can reject it for you
[00:46] <hatch> :P
[00:46] <gary_poster> :-P
[12:17] <frankban> gary_poster: morning, do you have time for a quick call?
[12:17] <gary_poster> hey frankban, absolutely
[12:18] <gary_poster> frankban, in guichat
[12:18] <frankban> gary_poster: cool thanks
[12:46] <gary_poster> rick_h, thanks for taking up huw's branch.  want me to take a look at it, or are you just going to land it?  either would be fine
[12:46] <gary_poster> (I mean your version of the branch)
[12:47] <rick_h> gary_poster: if you're ok with the change at the bottom of https://codereview.appspot.com/12853043/diff/1/app/subapps/browser/views/charm.js?column_width=80 I'm happy to land it from here
[12:47] <rick_h> gary_poster: basically I think the real issue was trying to activate a non-existant tab and wanted to check/fix that
[12:48] <rick_h> gary_poster: this means old urls will default to the summary tab vs the 'redirect' approach
[12:48] <gary_poster> rick_h, sounds good to me, and code looks good.  ship it. :-)
[12:48] <rick_h> gary_poster: rgr, thanks
[13:02] <frankban> gary_poster: I was thinking: do we really need to watch a single deployment or is it ok to watch them all, leaving to the client the joy to filter changes if it is interested in only one deployment? 
[13:09] <gary_poster> frankban, lol
[13:10] <gary_poster> frankban, uh, I guess it could be all?  And then the client remembers which one it cared about?
[13:10] <gary_poster> and if you reload the page, it doesn't matter, because it is all the same anyway?
[13:11] <jcsackett> gary_poster: hopefully quick question for you on a todo you've noted in models/charm.js. it's the bit about verifying if is_subordinate or subordinate is passed from the env.
[13:11] <gary_poster> jcsackett, gotcha, yeah?
[13:11] <jcsackett> i was wondering how to go about verifying that on both py and go? i need to verify two other things being passed up as well.
[13:12] <jcsackett> i'm *guessing* i can check py with rapi.
[13:12] <jcsackett> but i have no idea about go.
[13:12] <jcsackett> thoughts?
[13:13] <frankban> gary_poster: yes, and the first message when you watch all is the complete history  of all the deployments, except for the completed ones, in which case you just see them in a completed status
[13:13] <jcsackett> alternatively we can punt on this and leave the checks in place for now; i've audited the code and there was no meaningful cleanup to do until we delete models.Charm, and this stood out as one possible leftover, but i suppose it's not pressing.
[13:14] <gary_poster> jcsackett, yeah you can use rapi.  For go, three thoughts.  First, IIRC if you start the GUI up in dev mode the log will include socket communications.  You could certainly hack it to do so.  Second, in Chrome I think you can see the socket communications. Third, benji added a control-shift-d option to save the websocket log to a file.  I don't remember the details, but it might be ideal.
[13:15] <gary_poster> jcsackett, if it's easy and/or relatively easy and interesting, sure, let's do it. :-)
[13:15] <jcsackett> gary_poster: would that approach work in sandbox? or do i need to set up a juju deployment of some sort with gojuju?
[13:15] <gary_poster> frankban, huh...all completed deployments since the beginning of time?
[13:16] <gary_poster> jcsackett, if we have implemented this in the sandbox, then yes.  actually...
[13:16] <gary_poster> one sec
[13:16] <gary_poster> looking
[13:17] <frankban> gary_poster: we can set a timeout to clean up old deployments, this is something we need to do also in the case we watch a single deployment
[13:18] <gary_poster> jcsackett, no sandbox is not good enough.  the sandbox is the thing we need to change, if we are wrong.
[13:18] <jcsackett> gary_poster: ah, so i need to get a working gojuju and deploy out with that, then inspect a deployment.
[13:18] <gary_poster> jcsackett, right now the sandbox sends is_subordinate but I think it is wrong, for py, go, or both
[13:18] <gary_poster> jcsackett, exactly
[13:18] <benji> gary_poster: did I miss the fact that Aaron was going to be out today?
[13:19] <jcsackett> gary_poster: ok.
[13:19]  * jcsackett goes to look up juju docs for getting a working go juju.
[13:20] <gary_poster> benji, I dunno.  I don't remember Aaron being out today.  jcsackett or adeuring do you happen to know?
[13:20] <jcsackett> gary_poster, benji: i don't remember him saying he was out today...next week or this friday, maybe.
[13:20]  * jcsackett checks canonicaladmin
[13:21] <adeuring> I can't remeber this either...
[13:21] <gary_poster> frankban, true...I didn't think that we would need it for the single deployment case but I see what you meamn
[13:21] <gary_poster> frankban, so yeah, I caould buy that :-)
[13:21] <jcsackett> benji: he's listed out next week, not today (or any of this week).
[13:22] <benji> I didn't know canonicaladmin would tell me that.  Thanks.
[13:22] <gary_poster> thanks jcsackett (I was thinking I didn't have canonicaladmin visibility because I didn't manage...silly me).  Yeah benji, the calendar link lets you see the next two weeks
[13:22] <jcsackett> benji: mind you, it's not always accurate.
[13:22] <gary_poster> heh
[13:22] <gary_poster> yeah
[13:23] <jcsackett> it once reported me as being out on "national holiday leave" for three months.
[13:23] <gary_poster> my holiday is not in, and none of my previous holidays are in because they have not been formally approved :-/
[13:23] <gary_poster> benji ^^^
[13:24] <benji> k
[13:26] <benji> abentley: good morning; let me know when you get settled, I'd like a quick call about my branch
[13:27] <abentley> benji: I'm free to chat.
[13:27] <benji> abentley: cool, I have to go outside to get my camera :) one second and I'll be there
[13:49] <hatch> morning
[13:53] <gary_poster> morning
[13:54] <hatch> I set up zsh, tmux, vim yesterday
[13:54] <hatch> well 'started'
[13:55] <hatch> it's pretty cool, I can now type tgui and it opens up a new tmux window with it ready to dev on the gui
[13:55] <gary_poster> hatch, on a vm you mean
[13:56] <hatch> nope in ubuntu
[13:56] <hatch> opening up the terminal opens it up automatically in a new zsh tmux session
[13:56] <hatch> then I navigate to the dir I want to work in and `tgui`
[13:57] <hatch> wait a few seconds and then it's all set up
[13:57] <hatch> I still can't use vim very fast though :)
[13:57] <gary_poster> hatch, I guess I don't see what is all set up :-) other than vi in a tmux
[13:58] <hatch> oh well it splits the window, makes, the builds, sets the root dir for ctrlp
[13:58] <gary_poster> oh, ok, cool
[13:58] <hatch> and because I found I switch branches a lot
[13:59] <hatch> all I need to do is navigate to a new branch and type `tgui` and it opens up a new window ready to go
[13:59] <hatch> so I can switch between them using ctrl+b+[0-9]
[13:59] <hatch> I fully expect something to break because it went a little too smooth setting this all up
[14:01] <antdillon> bcsaller, Makyo Hi, do either of you guys have sometime to help me with new relation behaviour?
[14:03] <hatch> antdillon: I believe your 2 to 1h early respecitvely
[14:03] <hatch> anything I can help you with?
[14:05] <Makyo> I'm in, but don't know anything more about it at the moment.  At least, not off the top of my head.
[14:10] <antdillon> Makyo, hatch, Thanks, its about adding drag and touch to create a relation between the service blocks
[14:10] <Makyo> antdillon, is there a document somewhere for this?
[14:11] <antdillon> Makyo, hatch I have the hit detection working 
[14:11] <antdillon> Makyo, Unfortunately not, Luca asked me to create a fork of the gui and get a prototype of some thoughts working
[14:12] <antdillon> Makyo, All he told me was he wanted to drag a server block to touch another then to wait a second or two to create a relation
[14:12] <Makyo> antdillon, just wrt touch interaction?  Touch has been on the plate since I started at Canonical almost a  year ago, and I even have one of our N10s for that work :)
[14:12] <hatch> so what's the question? :)
[14:14] <antdillon> hatch, Makyo Is there a simple way to create a relation between two service blocks without a line?
[14:14] <rick_h> hatch: the issue when I tried to help him was that he can detect a hit, but he wants to create the relation line aftter that point and the code is setup that it's based off the click/drag start/end and not a good way I could see to suggest "call XXX to get the relation line going"
[14:14] <antdillon> Makyo, Oh you have plans for this work already?
[14:14] <luca> Makyo: hatch not using Ubuntu touch, nothing to do with mobile
[14:15] <Makyo> antdillon, no, different touch.
[14:15] <Makyo> luca, antdillon, does this take into account ambiguous relation types, or selection of available relate-able services?
[14:15] <Makyo> Because, at the very least, all you should need to do are fire the proper events against the topo.
[14:16] <Makyo> That will create lines, pop up menus, etc.
[14:16] <hatch> yeah I was just reviewing the code here
[14:16] <antdillon> Makyo, I started to us the ambiguousAddRelationCheck function but seems tided in with the dragged line
[14:16] <hatch> so you want to drag one service onto another service to create a relation
[14:16] <hatch> the services then....bounce appart?
[14:17] <antdillon> Makyo, I can't seem to find a function that takes 2 service ids connects them if they pass the tests
[14:18] <antdillon> hatch, At the moment all I want is to create a relation if they overlap
[14:19] <Makyo> antdillon, alright.  hatch, you seem really eager, and I think we're going to step on each other's toes if we keep this up.  You want to take this?
[14:19] <hatch> antdillon: see 'addRelationEnd' in topology/relation.js
[14:19]  * Makyo bows out.
[14:19] <hatch> Makyo: sure.....unelss you wanted
[14:19] <hatch> :)
[14:19] <hatch> sorry
[14:19] <Makyo> hatch, go ahead, I'm not going to just add to this mayhem.
[14:19] <hatch> haha
[14:19] <antdillon> hatch, Yes got 'addRelationEnd'
[14:20] <hatch> antdillon: ok then you see the db.relations.create() call
[14:20] <antdillon> Makyo, Thanks for helping so early in your day
[14:20] <antdillon> hatch, Yes, that does the work
[14:20] <Makyo> antdillon, I start at 8, so 20 minutes ago, not so early :)
[14:20] <hatch> oh right Makyo we r on the same time
[14:20] <hatch> this day....
[14:21] <Makyo> hatch, YEah, except for one week or whatever.  Yesterday was recovery from travel, so I was in an hour late, working an hour late.
[14:21] <hatch> oh where did ya go?
[14:22] <antdillon> hatch, So you think creating a new function in relation.js to take two ids and just run the db code?
[14:22] <hatch> well no heh
[14:22] <Makyo> Just down to Denver.
[14:22] <hatch> Makyo: ahh
[14:22] <hatch> antdillon: you also need to add relation wrt the env
[14:22] <hatch> so that it will update everything via the deltas
[14:22] <hatch> when it returns
[14:23] <hatch> that's the key part there
[14:23] <hatch> buuuut
[14:23] <hatch> you might be able to hack it
[14:23] <hatch> by copying the code on line 881
[14:23] <hatch> db.relations.create() and then firing db.fire('update')
[14:24] <hatch> I believe that'll then fire the proper UI methods to draw the relation
[14:24] <Makyo> hatch, antdillon - you will also have to guess at the relation type, FYI.
[14:24] <Makyo> While we're being hacky.
[14:24] <hatch> Makyo: yeah I was gona say to create a relation with two services, copy those values
[14:24] <hatch> ^ antdillon
[14:24] <hatch> then use those as static values in your 'drop' method
[14:24] <hatch> since it's just a prototype and all
[14:25] <antdillon> hatch, Ok I'll copy the code on and re-factor a new function
[14:26] <hatch> antdillon: the only catch to this approach is that you will need to always pick the same two services in your demo else it'll break :D
[14:27] <hatch> but it's easier to write hah
[14:29] <antdillon> hatch, Yeah, I'll get it working for 2 services that I know can connect then get some checks in before. Think luca wants the service to grey out if they are not compatible as you drag one around
[14:31] <hatch> I'm a little concerned
[14:32] <hatch> what happens when you drag one over another one but you're just reorganizing them
[14:32] <hatch> or you accidentally drop it on another one
[14:33] <hatch> just throwing those out there :)
[14:33] <hatch> I actually like the idea I'm just not sure how it will work in reality
[14:33] <antdillon> You have to be holding the service block to connect and when you touch them luca wants a timer to appear and if you keep them connected it makes the relation
[14:34] <antdillon> I suppose the example I think of is menu items on xbox kinect
[14:36] <hatch> ok well the kinext interaction is irritating :P
[14:36] <hatch> lol
[14:36] <hatch> I always want to 'push' in the air to select the menu
[14:36] <antdillon> Lol me too! but been asked to try it :)
[14:37] <hatch> kinext enabled gui?
[14:37] <hatch> :P
[14:38] <antdillon> Think, minority report :)
[14:41] <antdillon> hatch, Think I could fake it by calling addRelationEnd with the endpoints?
[14:41] <hatch> how we are talkin!
[14:41] <antdillon> hatch, Just need to work out what module is meant to be
[14:42] <hatch> I think it's the environment
[14:42] <hatch> sec I'll start up an instance
[14:43] <hatch> aww crap it's not made yet....making
[14:43] <antdillon> I've got the endpoints array to send through
[14:45] <hatch> ok almost there
[14:46] <hatch> antdillon: it's actually a RelationModule
[14:46] <antdillon> hatch, Which would be created on start drag?
[14:47] <hatch> just looking that up for ya
[14:48] <hatch> your actually going to be IN the relation module
[14:48] <antdillon> Thing is the hit code is in service.js which needs to call relation.js
[14:50] <hatch> antdillon: looks like the second param to scene {} events in relation is the relation module
[14:50] <hatch> in relation.js
[14:50] <hatch> so can you move your call there?
[14:52] <antdillon> I can call there form service.js?
[14:53] <hatch> if you do that then you'll probably need to pull the relation module instance from the topology modules object
[14:53] <hatch> the topo stuff is organized a little odd because it's done by composition
[14:54] <hatch> topo is like brown playdo because it's full of all the other colours
[14:54] <antdillon> hatch, Yeah seems like the super controller of all the modules
[14:55] <antdillon> Odd, topo.models is undefined ?
[14:57] <hatch> antdillon: guichat? it'll probably be easyer :)
[14:58] <antdillon> hatch, Sure, hangout?
[15:11] <hatch> antdillon: hangouts crashed :/
[15:11] <antdillon> hatch, Ah, branch is here: c
[15:11] <antdillon> lp:~ya-bo-ng/juju-gui/test-prototype
[15:11] <hatch> ok on it, give me a second to look at it
[15:12] <hatch> and by second I mean a few minutes for it to make
[15:12] <hatch> heh
[15:12] <antdillon> hatch, Thanks, I'll get tea
[15:50] <gary_poster> jujugui call in 10, kanban now
[15:50] <hatch> yeah....what he said!
[15:53] <gary_poster> hatch, :-) do you mind if I run today since I'll be gone a week and a half afterwards? :-)
[15:54] <hatch> not-at-all
[15:54] <gary_poster> thanks
[15:54] <hatch> it's a tough crowd
[15:54] <hatch> good luck
[15:54] <hatch> :)
[15:54] <gary_poster> lol thanks
[15:54] <gary_poster> he luca, I'll ping you for a quick call in about 35 minutes or so?
[15:54] <gary_poster> Also, is ale coming back or is she gone for day?
[15:58] <gary_poster> hey rick_h, huw's css most recent change to summary page was wrong :-( now change log and description ignores whitespace
[15:58] <gary_poster> that was something he added; it was working when I gave it to him last night
[15:58] <gary_poster> rick_h, not your problem.  sorry.  I'll email him
[15:59] <rick_h> gary_poster: ah, noticed that change and meant to qa it but had your ok. sorry about that
[15:59] <gary_poster> arosales, could you take a look at charm details and see if you are OK with new "Related Charms" "Code" and "Features" tabs?  Features tab has biggest diff to content
[15:59] <gary_poster> jujugui orangesquad call in 1
[15:59] <gary_poster> np rick_h 
[16:00] <luca> gary_poster: Ale is out for the day
[16:00] <gary_poster> luca, darn.  ok will send email
[16:00] <luca> gary_poster: no problem for pinging me in a bit for a call
[16:00] <gary_poster> thx
[16:03] <arosales> gary_poster, will do. In a meeting atm
[16:03] <arosales> do you mind if i get you that feedback by eod?
[16:26] <gary_poster> arosales, not at all.  I'm out for a week and half starting tomorrow, so please give it the juju-gui list
[16:27] <benji> the October sprint page says to book flights by July 8.
[16:27]  * benji fires up the time machine.
[16:27] <jcsackett> Makyo: calling now.
[16:28] <jcsackett> Makyo: it claims you are not available.
[16:28] <Makyo> jcsackett, probably pidgin getting in the way.
[16:31] <rick_h> jujugui who wants to chat sticky headers? meet up in guichat
[16:32] <hatch> there
[16:51] <arosales> gary_poster, will do, thanks for the ping.
[16:52] <gary_poster> rick_h, hatch you done?  if not, you want me around?
[16:52] <hatch> we are done
[16:52] <gary_poster> what's the resolution?
[16:53] <hatch> the timebox will need to be like 4 days
[16:53] <hatch> :)
[16:53] <gary_poster> ok
[16:53] <hatch> so in our oppinion it's probably low priority compared to others
[16:53] <gary_poster> would it help to pair or is this a single engineer task?  I get the impression that pairing might be good on this.
[16:54] <gary_poster> wellll...it's low priority compared to getting the inspector done on time
[16:54] <hatch> yeah I think pairing would help
[16:54] <hatch> there are so many issues surrounding the dynamic content
[16:54] <hatch> I can run them past you if you want
[16:54] <hatch> i'm in guichat
[16:54] <gary_poster> do you have possible solutions?
[16:54] <gary_poster> ok I'll join
[16:54] <rick_h> gary_poster: yea, want a summary? I'd like your feedback on if we can push back slightly for a less fluent version
[16:55] <gary_poster> rick_h, yeah, guichat?
[16:55] <rick_h> gary_poster: rgr
[17:32] <rick_h> hatch: so I'm going to grab that checkbox bug to get my feet wet. Let me know if there's something else you think I should hunt at
[17:33] <hatch> sure thing - just remember that's a little more involved because of the databinding
[17:33] <rick_h> hatch: yea, hoping it'll get my feet wet on that stuff
[17:33] <rick_h> and at least has some limited scope to keep inside of
[17:33] <hatch> a potentially easier one would be 'import config file does not work'
[17:34] <rick_h> hatch: ok, will take your advice
[17:49] <bac> benji, abentley: i'm seeing odd behavior with the enqueue script.  can either of you explain http://paste.ubuntu.com/5982047/  noting that ~bac != ~abentley
[17:49] <abentley> bac: The prefix controls charms, but not bundles.
[17:50] <abentley> bac: So you will get my bundle no matter what you do.
[17:50] <bac> abentley: so any running of enqueue will get all of the bundles all of the time?
[17:51] <abentley> bac: Yes.  I consider it a minor bug, but if we get significant numbers of bundles, we'll probably want to fix it.
[17:52] <bac> abentley: well it is a bit surprising.  but now that i know what's happening i can adjust.
[19:19] <benji> abentley: I'm having some late-breaking test failures on my branch, but we should probably put together our plan for the rest of thsi week and next so Gary can see/comment upon it today.
[19:20] <abentley> benji: let's do a call in 15.
[19:20] <benji> sounds good
[19:39] <bac> gary_poster: my appt got canceled so i'm not going to be out.
[19:39] <gary_poster> bac, ok, thanks for heads up
[19:53] <hatch> we really need to shrink the footer and header of the gui
[19:54] <hatch> with browser chrome on my laptop I have maybe 500px of vertical height hah
[19:59] <hatch> a higher resolution laptop would also solve that problem :)
[20:00] <hatch> does anyone remember who styled the zoom controls?
[20:00] <hatch> ^ rick_h it was you right?
[20:01] <rick_h> hatch: I reviewed/landed ant's changes
[20:02] <hatch> ahh ok, well he isn't on the kanban so looks like you're getting the credit :P
[20:02] <rick_h> wheee
[20:02] <gary_poster> heh
[20:05] <gary_poster> rick_h, +1 on the bugfix you are working on.  Afterwards, the only big thing to do for being feature complete is to add the constraint section to the ghost inspector--or are you doing that hatch?  Otherwise I'd suggest hatch giving a pre-imp on that
[20:05] <hatch> either or - I can preimp regardless
[20:07] <gary_poster> hatch, is it roughly separate from the rest of what you are doing?  the scale up/down is post-deployment, so separate, yeah?
[20:07] <hatch> yeah it's totally separate
[20:07] <gary_poster> cool
[20:08] <hatch> there might be some template sharing
[20:08] <hatch> will*
[20:08] <gary_poster> right, that's where the pre-imp would come in handy
[20:08] <hatch>  should?
[20:08] <hatch> heh
[20:08] <rick_h> gary_poster: k, thanks for the heads up
[20:08] <gary_poster> :-)
[20:15] <hatch> now that the viewlets are split out they sure looks awesome
[20:15] <hatch> they have regained some of their previous glory
[20:16] <bac> abentley, benji: care to do a review: https://code.launchpad.net/~bac/charmworld/bundle-results/+merge/179987
[20:16] <abentley> bac: Will do.
[20:17] <bac> thanks abentley
[20:26] <hatch> bcsaller: kickin around?
[20:26] <bcsaller> hatch: yeah, was going to eat soon though
[20:26] <bcsaller> whats up?
[20:26] <hatch> ok real quick
[20:26] <hatch> unit_count is not firing change events through the databinding when it's value is changed
[20:27] <hatch> was wondering the best way to track this down
[20:27] <hatch> the bindings are being 'added'
[20:27] <bcsaller> it was though, that is your memory as well?
[20:27] <hatch> so it sets the proper initial value
[20:27] <hatch> at first I thought so
[20:27] <hatch> but I'm not so sure it was ever working
[20:27] <bcsaller> hatch: that initial value isn't just the template?
[20:27] <hatch> nope
[20:28] <bcsaller> I'd thought it was showing the number of units when we tested scaling with the current UX
[20:28] <hatch> well why don't you go eat I'll work on another part and when you're back we can run through this
[20:28] <bcsaller> I'd put a log in _updateDOM and start there 
[20:28] <bcsaller> ok
[20:28] <bcsaller> I'll ping later
[20:28] <hatch> enjoy!
[20:31] <hatch> bcsaller: I got it....of course right after I ask lol
[20:31] <hatch> enjoy your lunch
[20:43] <bac> abentley: i see the ingester complains about the bonnie charm.  do we give feedback to ~charmers when problems are seen?
[20:43] <abentley> bac: No.
[20:50] <bcsaller> hatch: what was it?
[20:52] <hatch> bcsaller: if you open the inspector too fast it doesn't work
[20:53] <bcsaller> hatch: our init routine is broken?
[20:53] <hatch> yeah I haven't had a chance to really narrow it down but if you deploy a service and right away dclick it to open the inspector it doesn't update
[20:54] <bcsaller> hmm, that will need a card if you don't track it down now, that will hit people
[20:56] <hatch> yeah I'm trying to find a real way to repro 'do all this really fast' isn't really an acceptable repro step :)
[21:12] <gary_poster> hatch, fwiw there is a card with this description: "ghost inspector: when you click "confirm" and successfully convert to a real service, close the ghost inspector and automatically open the service inspector (or similar)"
[21:12] <gary_poster> hatch, that's a great way to trigger the problem you describe, it sounds like :-)
[21:13]  * gary_poster stepping away for a bit but will be back to finish a couple of emails
[21:17] <bac> abentley: thanks for the _id explanation
[21:18] <abentley> bac: np.
[21:19] <abentley> bac: I was actually wrong, in that the code you changed was already broken, because it was indexing before _id was set.
[21:20] <bac> abentley: your solution sounds good
[21:21] <abentley> bac: Cool.
[21:22] <hatch> so they say that the Chevy Volt has 10M lines of code controlling it
[21:22] <hatch> using the mythical 10 lines per day
[21:22] <hatch> that would have taken 1M days
[21:22]  * hatch is skeptical of their claim :P
[21:23] <hatch> make that 1M developer days
[21:25] <bac> hatch: have you seen how productive rick_h is?  those detroit dudes are agile and adroit.
[21:25] <abentley> hatch: Did they say they wrote all the code from scratch?
[21:26] <hatch> bac: sure but sometimes they need a few $B from the government because they forget what they were doing for 10years :P
[21:26] <abentley> bac: The version I've heard is that average developers produce about 10 LOC, great developers 100 LOC and poor developers 1 LOC.
[21:26] <hatch> abentley: I hope not haha
[21:27] <hatch> 100 LOC/day? maybe for a code monkey
[21:28] <abentley> hatch: 100 LOC isn't absurd.  I don't hit that every day, but I often do.
[21:29] <hatch> well I suppose
[21:29] <hatch> we have ~45k loc in js in the gui
[21:29] <hatch> which is much less than 100loc/day but I'm not sure how many ft ppl could say we were on it
[21:30] <hatch> 4?
[21:30] <hatch> but that includes comments and closing curly brackets hah
[21:32] <bac> abentley: your change works.  thanks.
[21:38]  * bac dogwalks
[21:39] <hatch> abentley: yeah I suppose I could see 100loc if you include curly's and comments
[22:11] <hatch> bcsaller: do you have any objection to me sending the prevVal through to the viewlet update method?
[22:12] <bcsaller> hatch: you have to properly pull it from POJO observe changes as well (it is there but called different) if its part of the interface
[22:12] <bcsaller> I had that in the original conflict branch as well so I think its a fair idea
[22:14] <hatch> oh right I forgot about the POJO stuff
[22:16] <hatch> bcsaller: ot: do you also use ctrlp for your file searching needs?
[22:16] <bcsaller> hatch: I use http://vim.spf13.com/ which includes CtrlP
[22:17] <hatch> ahh cool I'll have to look into that
[22:17] <hatch> I see all these fancy themes and then I look at mine
[22:17] <hatch> heh
[22:18] <hatch> using zsh and tmux I have no idea where half of the settings are coming from lol
[22:18] <bcsaller> spf13 was me not wanting to learn about the world of vim plugins, I mostly haven't had to
[22:19] <hatch> what does your terminal 'stack' look like?
[22:24] <huwshimi> Morning
[22:25] <rick_h> huwshimi: morning
[22:26] <rick_h> huwshimi: landed your branch with a tweak for the hash urls. gary_poster mentioned that the css changes broke the white-space respecting bits of the changelog and such. not sure if he emailed you about that or not
[22:27] <huwshimi> rick_h: Ah thanks. He did not :(
[22:29] <gary_poster> huwshimi, hey, sorry, yeah.  The way the whitespace was for the description and changelog was intentional
[22:30] <gary_poster> and (at least somewhat) important
[22:30] <gary_poster> pre-something or other?
[22:30] <huwshimi> gary_poster: Being proken onto three lines?
[22:30] <huwshimi> broken
[22:30] <gary_poster> it looked right in my branch
[22:30] <gary_poster> huwshimi, maybe there was a case it which it was bad, and I'd be happy to look at it
[22:30] <gary_poster> huwshimi, but the goal is:
[22:31] <rick_h> huwshimi: if there's a newline in the changelog content, or the desciption, we respect it in the html output
[22:31] <gary_poster> we honor whitespace, we still let it wrap, and we wrap long words (usually urls) if necessary
[22:31] <rick_h> basically it was people doing - lists in changelogs and such and not having them go into a single line of output when displayed
[22:32] <gary_poster> right, and descriptions too
[22:33] <bcsaller> hatch: I didn't understand the question. I run a vim terminal with 3 or 4 windows and then on another tab I'll run a split console with make devel, make test-server and a shell each in one split using terminator.
[22:33] <rick_h> huwshimi: see https://jujucharms.com/precise/memcached-7/ vs http://comingsoon.jujucharms.com/precise/memcached-7/ changelog output
[22:33] <rick_h> (you have to open up the changelog to see the one in particular)
[22:34] <huwshimi> gary_poster: Ah I see
[22:35] <gary_poster> thanks huwshimi, rick_h 
[22:35] <gary_poster> biab
[22:36] <huwshimi> gary_poster: Probably worth getting Luca to take a look at what we should do, it looked a bit funny having the description broken onto a new line.
[22:36] <huwshimi> Also, there where semantic html issue with that specific implementation, but that's not an issue
[22:36] <huwshimi> (as in, easily fixed)
[23:32] <hatch1> rick_h: I ended up getting weechat to work by adding the stable ppa and installing the most recent version
[23:33] <hatch1> just in case you were also looking at doing it, you'll want to run the same ppa
[23:51] <gary_poster> huwshimi, ack.  I am out for next week and a half.  Please fix up to where it was roughly before, and then shoot out an email to Luca with the other issue you see.
[23:56] <huwshimi> gary_poster: OK will do