[11:01] <rick_h_> morning party people
[11:01] <rick_h_> TGIF
[11:54] <kadams54> guihelp https://github.com/juju/juju-gui/pull/325 is ready for QA and review
[11:55] <rick_h_> kadams54: got it, will look in a sec thanks
[11:56] <rick_h_> kadams54: can you pull the WIP from the title? 
[11:56] <kadams54> Sure… though my thoughts were that someone else would take over and land that branch.
[11:56] <rick_h_> kadams54: I think we're down a few fokls today so not sure it'll move today
[11:56] <kadams54> OK
[11:57] <rick_h_> if you're back on monday we can review/qa today but I think half the team is out 
[11:57] <rick_h_> but cool, I'll take a look and if it's cool/close will try to get it landed. If not, we can catch up monday
[11:57] <rick_h_> and get outta here and enjoy the weekend man
[11:58] <rick_h_> the chilly, cold, wet,  ugh weekend :/
[11:58] <kadams54> hah
[12:01] <kadams54> Alright, I'm out. (Though I already spotted a typo in the comments, likely due to some errant Vim commands, that will need fixing.)
[12:38] <bac> hi tvansteenburgh, you pinged me last night after i was AFK.  what's up?
[13:00] <tvansteenburgh> bac: nvm, it's already fixed :)
[13:00] <bac> tvansteenburgh: my kind of problem
[13:04] <redir> morning
[13:04] <rick_h_> morning redir 
[13:04] <jcsackett> morning, all.
[13:06] <redir> very celebrate! wow
[13:06] <rick_h_> heh, I'm falling over tired over here so you guys will have to prop me up for meetings kthx
[13:06]  * redir props
[13:16] <bac> redir: what are you celebrating?
[13:16] <redir> morning party
[13:17] <bac> oh
[13:17] <redir> heh
[13:17] <redir> still mainlining coffee
[13:17] <bac> that's not quite as festive as i'd imagined
[13:17] <rick_h_> that's what I missed this morning. Didn't make my coffee
[13:17] <rick_h_> oh moka pot, here I come!
[13:18] <redir> I do have that doge meme in my head since dinner last night.
[13:18] <redir> :/
[13:18] <rick_h_> hah
[13:23] <rick_h_> jujugui ci is rebooting and such fyi
[13:24] <bac> redir: how was your couscous dinner?
[13:24]  * rick_h_ is testing out running landscape across our CI server ans such
[13:27] <redir> I can't kill vim
[13:27] <redir> bac it was really good
[13:27] <redir> pretty inexpensive fresh pasta
[13:27] <redir> wine <10 a glass
[13:27] <redir> and wow. very quality
[13:28] <bac> cool.
[13:28] <redir> how do I unfreeze vim
[13:28] <redir> ?
[13:28] <rick_h_> you froze vim? wow
[13:28] <rick_h_> open a terminal and `sudo killall (g?)vim` 
[13:29] <rick_h_> (not sure if you're running vim or gvim
[13:30] <bac> looks like he did 'killall weechat'
[13:30] <rick_h_> lol, reboot when all else fails
[13:31] <bac> hey, anyone have experience with SMART hard drive warnings?
[13:31] <rick_h_> If I see one I buy a new hard drive
[13:31] <rick_h_> about the end of my experience with them
[13:31] <bac> yeah, but does BAD mean you have time to recover?
[13:31] <rick_h_> not sure
[13:32] <redir> I don't know if it was vim or tmux
[13:32] <redir> no key resopnses
[13:32] <redir> in that term
[13:32] <rick_h_> dropped ssh connection?
[13:32] <redir> kill vim was just responing under new pid
[13:32] <redir> tried killing tmux and that killed it all
[13:32] <redir> local vim
[13:32] <rick_h_> lol
[13:33] <redir> slowly trying vim. using for editing configs only first
[13:33] <redir> can't imaging trying to write code modally
[13:33] <rick_h_> :) it's super awesome
[13:34] <redir> :)
[13:34] <rick_h_> I had a bunch of intro videos but they seemed to have been pulled :(
[13:34] <redir> so edit
[13:34] <redir> much powerful. wow
[13:35] <rick_h_> hmm, my blip account was removed it seems. 
[13:35]  * redir refrains from googling blip
[13:36] <redir> vague memory of blip is surfacing. Keeps taking longer to find things in my wetware
[13:37] <rick_h_> https://www.youtube.com/watch?v=XXJO_Swmdnw is the one I put on youtube. I'll have to try to find my other orig videos and upload them or someting
[13:38] <rick_h_> ooh, here we go. i did upload #3 and #4 as well https://www.youtube.com/watch?v=KVAeelM-0QI https://www.youtube.com/watch?v=SzrcMilnre8
[13:39] <jcsackett> for some reason hearing your voice in a youtube video weirds me out.
[13:39] <rick_h_> heh, not surprising
[13:40] <rick_h_> wow, 2010? Time flies
[13:57] <redir> bac I don't know that it can measure if you have time to recover
[13:57] <redir> I think those smart tools just tell you that things are failing
[13:58] <redir> OK importing stuff into the jcorestore to start adding search
[14:06] <rick_h_> redir: huh?
[14:07] <rick_h_> redir: not sure that's something you should bite off atm. There's a lot more there than meets the eye. 
[14:08] <redir> http://bit.ly/1ox5YpO
[14:08] <rick_h_> redir: if there's no smaller bugs to tackle, I'd suggest chatting about some intro task we need for the next step in our store process
[14:08] <rick_h_> redir: yea, that's a loaded bug and a half there
[14:08] <redir> http://bit.ly/1ox66Wv
[14:08] <redir> only two left
[14:09] <redir> really
[14:09] <redir> importing charms anyhow
[14:09] <rick_h_> redir: ok cool, then let's put those on ice and start to look at the upcoming tasks we plan on planning-poker'ing on monday and see if we can start something there
[14:09] <redir> open to a chat if you are awake
[14:09] <rick_h_> redir: cool yea, understood
[14:09]  * redir looks at on deck
[14:09] <rick_h_> yea, jump in the standup room? I might have to bail as I'm expecting a call but no idea when it'll arrive
[14:11] <redir> jumping
[14:22]  * rick_h_ goes to make coffee
[14:27] <hatch> hey all, what do you think of my latest blog post? http://fromanegg.com/post/85890866087/unidirectional-data-flow-architecture
[14:35] <bac> hatch: your page does not load in safari
[14:35] <rick_h_> hatch: cool
[14:35] <hatch> bac, it's just you :)
[14:35] <hatch> rick_h_ thx
[14:38] <bac> that is unlikely
[14:39] <hatch> analytics shows people from Safari and I have safari
[14:39] <hatch> s/from/on
[14:50] <jcsackett> jujugui: call in ten.
[14:50] <bac> drats, it seems to be an orangesquad holiday
[14:52] <redir> hatch: do users "visit" urls?
[14:52] <hatch> hah, sure, why not? :)
[14:52] <hatch> do you have better wording:
[14:52] <hatch> ?
[14:53] <redir> hatch: I don't really know. I just understood gui to not be URL driven
[14:54] <hatch> it's VERY url driven now
[14:54] <hatch> :)
[14:54] <redir> you mean with the new work going in?
[14:55] <hatch> redir yeah - many interactions update the URL so that it's sharable 
[14:55] <redir> it may have been before too. I just had this conception that it loaded and you did stuff and state changed but the url didn't
[14:55] <hatch> yeah, well the url only changes when the state is potentially sharable
[14:56] <hatch> so, viewing an inspector? sharable, dragging a machine around, not sharable
[14:56] <redir> and it devises state from the URL
[14:56] <hatch> on the first pass yes
[14:56] <hatch> subsequent passes the url is updated from state changes
[14:56] <hatch> because the state is more detailed than the url needs to be
[14:58] <redir> right and app state isn't really a resource
[14:58] <redir> AFIU
[14:58] <hatch> well, it's the resource which determines what the app is doing
[14:59] <rick_h_> jujugui call in 1
[15:23] <jcsackett> react does look cool.
[15:24] <rick_h_> yea, I generally hate the whole mixing of definitions/model stuff in the HTML, but it does the thing I like of "here's some data redraw" really really well
[15:24] <bac> jcsackett: given that aaron and curtis are not here today, could i bug you about some charmworld archeology?
[15:24] <jcsackett> bac: oh dear. i suppose so. :p
[15:24] <bac> jcsackett: specifically bug 1096131 and its companion branch https://code.launchpad.net/~abentley/charmworld/login-config/+merge/142974
[15:24] <jcsackett> bac: if you want to hangout, give me about 5 min.
[15:24]  * jcsackett needs more coffee
[15:24] <_mup_> Bug #1096131: login/logout buttons do not update correctly <charmworld:Fix Released> <https://launchpad.net/bugs/1096131>
[15:25] <jcsackett> oh wow, i probably will have nothing to contribute on that, but give me a moment to make coffee and look at it and then i can try and answer questions.
[15:36] <bac> jcsackett: back?
[15:39] <jcsackett> bac: back.
[15:40] <redir> I see what you did there
[15:40]  * jcsackett lauchs
[15:42] <bac> jcsackett: you make a hangout?
[15:44] <jcsackett> bac: just tried to do video from the msg you sent me on g+
[15:44] <jcsackett> shall i try again?
[15:44] <bac> yes, or just paste the url
[15:44] <bac> i can't figure out how to start a hangout on the phone
[15:45] <redir> so both core store and cw want to use mongo.juju['charms'] for persistence
[15:46] <redir> but differently
[15:48] <rick_h_> redir: yea, well the two were indepenant
[15:48] <rick_h_> independent
[15:48] <redir> tried to cheat and index the charms imported by charmload
[15:49] <rick_h_> lol
[15:49] <redir> got the full family fued XXX
[15:49] <redir> s/fued/feud
[15:49] <rick_h_> woot! got my power cables for muy nucs
[15:50]  * redir imagines rick_h_ doing victory dance with power cables
[15:50] <rick_h_> damn, I ordered 3' cables on purpose!
[15:51]  * rick_h_ grumbled
[15:51] <redir> short victory dance?
[15:51] <rick_h_> yea, not short enough I guess
[15:52] <rick_h_> oh well, not going to send them back over it
[15:52] <rick_h_> it's on a rack, I don't need 6' of cables. The plug is 12" from the box
[16:05] <hatch> haha
[16:06] <hatch> I needed a ethernet cable a while back, the only one I had was 100ft long
[16:06] <hatch> it needed to go 2'
[16:06] <hatch> :D
[16:47] <redir> doesnt' look like a nything sets the version for migrations in the DB
[16:48] <rick_h_> redir: ? the migation tool chain itself marks the versions
[16:49] <redir> Datastore is not currently versioned
[16:50]  * redir reads more code
[16:51] <rick_h_> redir: oh, you have to init it
[16:51] <rick_h_> make db_init? /me has to go look
[16:51] <hatch> guys - there was a problem connecting to my NAS, I need to contact my system administrator
[16:52] <redir> rick_h_: that is kind of what I mean
[16:52] <hatch>  /msg hatch
[16:52] <hatch> :D
[16:52] <redir> I was figuring that make run would set the current version or something
[16:52] <rick_h_> redir: yea, it should have
[16:52] <rick_h_> I've not touched this in a long time so catching up
[16:53] <rick_h_> hmm, wtf. The upgrade process makes sure it's initialized
[16:54] <rick_h_> redir: check out 'ensure_initialized'
[16:54] <rick_h_> so not sure what's up. 
[16:55] <redir> k, will keep digging. thought I'd see if anyone knew off the top of their head
[16:59] <rick_h_> guihelp anyone seen mass failures of tests that attempt to set focus? They cause script errors in FF and chrome
[16:59] <hatch> rick_h_ is this in test-server?
[17:00] <rick_h_> hatch: yes
[17:00] <redir> got it
[17:00] <hatch> the browser needs to be in focus
[17:00] <hatch> else they will fail
[17:00] <rick_h_> hatch: https://github.com/juju/juju-gui/pull/326
[17:00] <rick_h_> yea, it's got focus, or thought it did
[17:00] <rick_h_> even chrome?
[17:00] <hatch> yeah even chrome
[17:01] <hatch> TypeError: 'null' is not an object (evaluating 'chosenOne.simulate')
[17:01] <rick_h_> ok, it had focus and dies in YUI in the event handling 
[17:01] <rick_h_> no, not that
[17:01] <rick_h_> Uncaught TypeError: Cannot read property 'className' of null 
[17:02] <rick_h_> e.mix.removeClass dom-base-min.js:8
[17:02] <rick_h_> e.mix.toggleClass
[17:02] <hatch> ahh I see it
[17:02] <hatch> I'll have to pull it down to see
[17:02] <hatch> I'll check
[17:03] <rick_h_> hatch: thanks, yea love another set of eyes to see if you can dupe it or what not
[17:03]  * rick_h_ goes to get food stuffs annoyed
[17:10] <hatch> rick_h_ when I run the tests separately they pass
[17:14] <rick_h_> hatch: yea, if I run them individual they're fine
[17:14] <hatch> the problem is in test_browser_search_widget.js
[17:14] <rick_h_> k, I'm heading back there. 
[17:14] <rick_h_> whatever error is in there is non-obvious it seems. I'll go back through what's changed in there
[17:15] <hatch> yeah I looked at the diff....and wow, what a diff lol
[17:15] <hatch> the issue may not be in the test file per-se, it might be in the code it's running too
[17:15] <rick_h_> yea
[17:15] <rick_h_> stepping away for food and will restab it with a giant knife
[17:15] <hatch> sure
[17:20] <hatch> rick_h_ the issue is with the test: 'should support setting search string'
[17:20] <rick_h_> lol, two lines
[17:21] <hatch> yeah - would you like me to continue on it or do you want to take it from here?
[17:21] <rick_h_> hatch: cool thanks, will start to walk wha that does
[17:21] <hatch> ok cool
[17:21] <hatch> hopefully it doesn't something really bad and cascading test failures are actually a good thing lol
[17:23] <rick_h_> hah, heh it does a focus
[17:23] <rick_h_> hatch: so it's back to the focus issue
[17:27] <hatch> :(
[17:29] <rick_h_> hatch: yea, comment out the line 'input.focus()' and tests pass
[17:29] <hatch> I'm curious as to what changed in that branch to cause it to fail
[17:29] <rick_h_> yea, you and me both
[17:30] <hatch> from the obscure test messages it seems like maybe input doesn't exist?
[17:30] <hatch> or an event issue
[17:30] <rick_h_> I'm wiring some debug/try/catch stuff aroud that line
[17:30] <hatch> +1
[17:33] <hatch> ooooo sexy http://www.autoblog.com/2014/05/16/2015-nissan-370-z-nismo-revealed-pics/
[17:33] <hatch> Sometimes I wish I had somewhere to drive to
[17:38] <hatch> https://github.com/rdio/jsfmt
[17:38] <rick_h_> I was wondering how long it'd take you to find that
[17:39] <hatch> haha
[17:40] <hatch> I think we do a pretty good job at our layouts but maybe this will be better for the chaining bits than gjslint :)
[18:17] <hatch> rick_h_ any luck?
[18:17] <rick_h_> otp
[18:23] <redir> what's otp?
[18:23] <redir> I keep reading one-time-password and I know that is wrong
[18:28] <hatch> on the phone
[18:28] <hatch> or "on the potty"
[18:28] <hatch> I read it as the second
[18:28] <hatch> -always-
[18:28] <hatch> lol
[18:30] <redir> great
[18:30] <redir> such porcelain 
[18:31] <redir> helps though
[18:32] <redir> much appreciate
[18:33] <hatch> lol
[18:35] <rick_h_> on the phone :P
[18:35] <rick_h_> interviews are fun fun fun wheeee
[18:35] <rick_h_> hatch: no, I'm angry and closed the PR and going to try to find a way to do that work better by starting over and trying to find some incremental steps
[18:36] <rick_h_> hatch: running tests all along the way better to catch when I make the testing gods angry
[18:36] <hatch> well...we have always had issues with focus()
[18:36] <rick_h_> yea, but not like this
[18:36] <hatch> no, this is an odd one
[18:36] <rick_h_> every focus call in the suite, simulate or otherwise, is throwing a JS error down in YUI land and causess the suite to bomb out
[18:37] <rick_h_> I started commenting out every failing test, everyone one was around focus stuff
[18:37] <rick_h_> after I got to 7 I stopped and decided my branch is evil and must be exorcised
[18:38] <hatch> hmm
[18:38] <hatch> this is less than ideal
[18:38] <rick_h_> you're telling me
[18:40] <jcsackett> hatch or rick_h_, i am trying to replace a method on a view with a stub, but the stub isn't getting called when the event fires (trying to more directly test event listenting than just assuring 'on' gets called in bindEvents)
[18:40] <jcsackett> the actual method is, instead, as though no stub were created.
[18:40] <jcsackett> is replacing something bound via 'on' in initializer not possible?
[18:40] <hatch> are you stubbing the prototype?
[18:40] <rick_h_> jcsackett: show me the money! ... I mean code
[18:40] <hatch> you'll need to stub the method before the event handler gets called
[18:40] <hatch> er
[18:41] <hatch> event binder
[18:41] <rick_h_> jcsackett: you have to stub it on the live instance 
[18:41] <jcsackett> hatch: and stub it on the prototype, not on the view itself?
[18:41] <rick_h_> jcsackett: do it on the instance of the view
[18:42] <hatch> well you should stub it on the live instance if you can
[18:42] <rick_h_> not the View class
[18:42] <hatch> but if you can't then you need to do it on the prototype
[18:42] <hatch> before the instance is created
[18:42] <jcsackett> rick_h_, hatch: i'm doing it on the live instance. i'll try prototype and create new instance.
[18:42] <rick_h_> jcsackett: code, it should completely work if you're on the instance
[18:43] <hatch> rick_h_ unless the event is bound before it can be stubbed
[18:43] <rick_h_> well the event should be bound to a callback
[18:43] <rick_h_> that is stubable at any time on the instance
[18:43] <hatch> depends on how the event is created, it may be creating a bound instance of the callback, not calling the method you think it is
[18:43] <rick_h_> then it sholdn't do that to be more testable and refactorable :P
[18:44] <hatch> node.on('click', cb, this) 
[18:44] <hatch> in this case, cb is a bound function, not the original one
[18:44] <rick_h_> right, I understand, but I'd push that we update that to node.on('click', this._onClick, this)
[18:45] <hatch> same problem
[18:45] <hatch> the stubbing has to be done before that binding
[18:45] <jcsackett> hatch, rick_h_ https://pastebin.canonical.com/110371/
[18:46] <hatch> jcsackett yeah that's not going to work
[18:46] <hatch> you're stubbing the method after it's been bound 
[18:47] <rick_h_> man I swear we do this. 
[18:47] <hatch> I thought I had a test which tests what you're doing though
[18:47] <hatch> just checks that the on method is called properly
[18:47] <hatch> you're testing if the yui event system works
[18:47] <hatch> (which it does.....we hope)
[18:47] <rick_h_> no, you're testing that the callback does the right thing based on event data passed into it
[18:48] <rick_h_> hatch: yea, I mean true in this case, but we've got a lot of tests that catch events stuff
[18:49] <hatch> https://github.com/juju/juju-gui/blob/develop/test/test_machine_view_panel.js#L186
[18:49] <hatch> yeah - it's just that those tests are fraught with issues that we seem to always run into
[18:49] <hatch> heh
[18:49] <rick_h_> hatch: oh, but I don't use the stub code 
[18:50] <hatch> I'm pretty sure that this test tests exactly what you're trying to do jcsackett but skips the yui event handling
[18:50] <rick_h_> I just view._showDraggingUI = function(ev) { done(); }
[18:50] <rick_h_> jcsackett: ^
[18:50] <rick_h_> don't use the makeStub, but just change the function. It's on an instance, you don't have to reset it, and you can do whatever assertions you want in the function you create
[18:55] <jcsackett> rick_h_: i tried that too and it didn't work.
[18:55] <jcsackett> hatch: i'm doing this because just seeing if 'on' gets called doesn't seem like much either.
[18:56] <hatch> jcsackett I'm not sure I understand?
[18:57] <rick_h_> jcsackett: push a branch up please. 
[18:58] <hatch> jcsackett I'm pretty sure to do what you want to do you will need to stub the method out on the prototype of a NEW view, not the one created in the beforeEach
[18:58] <hatch> it'll have to be done before you actually call `new`
[18:58] <hatch> if I'm understanding what you're doing correctly
[18:58] <jcsackett> hatch: ok, i'm game for trying that.
[18:59] <hatch> if THAT doesn't work, then you have other problems :-)
[19:02] <hatch> jcsackett if you still have problems after that we can pair on it
[19:02] <hatch> if you like
[19:03] <jcsackett> nope, that fixed it.
[19:03] <redir> bac all your tests pass?
[19:04] <jcsackett> of course, now we return to the question, hatch, of whether this approach has any value--do you really think just asserting that 'on' was called for each event is sufficient?
[19:04] <jcsackett> i feel uncomfortable seeing that, but if others think that's enough, i don't want to add more tests to a not super fast suite.
[19:04] <hatch> well your test is definitely more thorough 
[19:04] <jcsackett> hatch: dig.
[19:04] <hatch> but since so much is 'faked', the other view, the callback ect
[19:05] <hatch> you're testing a) the event was attached b) that the proper callback is called
[19:05] <hatch> removing YUI from that equasion you're left with that the proper method was called with the proper args
[19:06] <hatch> know what I mean?
[19:06] <hatch> I'm not saying you SHOULDN'T write your test....I just question what it adds over what's already there (assuming YUI works) :)
[19:07] <jcsackett> hatch: well, that's the question i'm asking. b/c truthfully, i would rather replace the test checking that 'on' was called with three tests checking each event after fire. but if that's not *actually* an improvement, it's slower test run time for nothing.
[19:07] <jcsackett> well, not so much slower test run time, but more tests for nothing.
[19:08] <redir> how do I checkout bzr branch to a different revno
[19:08] <redir> ie: bzr switch -b test -r510
[19:08] <redir> still checks out 511
[19:09] <hatch> jcsackett well I suppose if you used the 'real' token view to emit the event via it's own mechanisms then it would be a good integration test
[19:09] <hatch> know what I mean?
[19:12] <jcsackett> hatch: yeah, but the last thing we need is more integration tests masquerading as unit tests. not saying integration tests would be bad.
[19:12] <jcsackett> i think, basically, my testing experience says "test the right events are fired and test the right behavior happens when an event is received"; checking 'on' is called doesn't feel like the latter to me, but perhaps it is.
[19:13] <hatch> but isn't that what you;re doing right now? creating an integration test? the current test calls the method in question, and makes sure that method does what it's supposed to do
[19:13] <hatch> which is kind of the definition of a unit test
[19:14] <hatch> so this test is saying "yes on() was called with the proper arguments" 
[19:14] <jcsackett> sure; i suppose that's true.
[19:14] <hatch> whereas yours is saying "yes the callback gets called when it receives this event"
[19:14] <jcsackett> you make a very good point.
[19:14] <redir> found it
[19:14]  * jcsackett has no love of js events and tests
[19:14] <jcsackett> :p
[19:15] <hatch> hah, sometimes I make sense :D
[19:19] <bac> redir: you see test failures in trunk?
[19:19] <redir> i'll checkout trunk in a second
[19:19] <redir> but I am on a fresh branch from trunk, so should be OK
[19:20] <redir> bac now working my way back on rev at a time., but still seeing fails
[19:20] <redir> so I have something broken
[19:48] <hatch> jcsackett so what did you end up deciding on? :)
[19:48] <jcsackett> hatch: i took your point--there's better work to do then shaving that yak.
[19:48] <hatch> oh Kay!
[19:57] <redir> bac wrong version of elasticsearch running
[19:57] <redir> fixed most. I still see on though
[20:07] <hatch> grabbing lunch
[20:07] <hatch>  /making
[20:11] <rick_h_> redir: sending frankban an email saying you were looking at the dep stuff. Please make sure to shoot an email when you EOD 
[20:11] <rick_h_> redir: even if it's "I didn't get around to it" so that he knows the status
[20:12] <redir> rick_h_: yeah trying to figure out why I have test failure now that I didn't have before
[20:12] <rick_h_> redir: all good, just don't want to leave it hanging
[20:18]  * rick_h_ heads out for the day. Have a good weekend all!
[20:34] <redir> bac you gone/
[20:34] <redir> ?
[20:34] <redir> jcsackett: ?
[20:34] <bac> redir: ?
[20:35] <redir> trying to understand why this test is failing but am failing to understand what it is testing even
[20:35] <bac> redir: what test?
[20:35] <bac> paste?
[20:35] <redir> test_search.py:TestUpdate.test_simple_change_dynamic_to_static_mapping
[20:36] <bac> oh, that looks like a fun one
[20:38] <redir> mmm
[20:38] <bac> redir: all of the test in the two test_search.py files pass for me...
[20:39]  * redir shakes computer
[20:40] <redir> kaaaahhhhhnnnn
[20:40] <bac> redir: so, in summary, it fails for you on trunk?
[20:40] <redir> bac yes
[20:41] <bac> wait, i was on revno 510.  trying again with 511.
[20:41] <redir> bac I converted to a lightweight checkout
[20:41] <bac> redir: you are on 511 with no mods?
[20:41] <redir> so totally fresh build today
[20:42] <redir> bac yea
[20:42] <bac> Ran 102 tests in 30.792s
[20:42] <bac> OK
[20:42] <redir> me deletes checkout and starts fresh again
[20:43] <bac> if it fails again, please paste the output.
[20:44] <redir> files not in mapping is the gist of the failure
[20:50] <jcsackett> what's the logic for when we should use the event tracker vs just using this.on($event)?
[20:51] <bac> jcsackett: use the event tracker if your level of indirection is less than 5
[20:51]  * jcsackett blinks
[20:52] <jcsackett> bac: is that an actual answer, or am i missing a reference? and if it's the former, i don't follow. :p
[20:52] <bac> it was a bad joke
[20:53] <redir> I laughed
[20:54] <hatch> jcsackett I suppose, whenever the event is being atttached to something that may not be removed when the instance is destroyed
[20:54] <hatch> so if the event is on the instance...well then there isn't a ton of risk because when the instance goes, so does the event. If it's on a dom node however.....
[20:54] <hatch> it's really a piece of mind thing though
[20:55] <bac> as in "i'll give you a piece of my mind"?
[20:56] <hatch> lol, just like that, yes
[20:57] <redir> Eddie would be proud
[21:00] <jcsackett> hatch: awesome, that makes perfect sense, thanks.
[21:00] <hatch> coolio, np
[21:04] <redir> is there a charm to install charmworld?
[21:05] <redir> we have an email list?
[21:05] <redir> jujugui@ or something?
[21:06] <bac> there is a charmworld charm
[21:06] <hatch> redir yes i'll pm it to u
[21:06] <redir> bac is it useful for developing
[21:06] <redir> ?
[21:06] <redir> hatch: merci
[21:06] <bac> not really
[21:06] <redir> boo
[21:08] <rick_h_> jcsackett: always use event tracker. Any time you do this.on() it leaves behind a handle that isn't cleaned up
[21:08] <bac> redir: you use bundle:~bac/charmworld-local/5/charmworld-local  to stand-up a charmworld with es and mongo on their own machines using quickstart if you want
[21:09] <bac> redir: probably not a useful exercise for friday afternoon, though
[21:09]  * redir pulls a handful of hair out. the tests  pass this time.
[21:09] <bac> yay, i think
[21:10] <bac> ok, i'm getting threatening stares from the dog so i'm taking him out.  see y'all later.
[21:10] <redir> later
[21:16] <redir> wher does bzr shelve store shelves
[21:16] <hatch> in the ether 
[21:16] <hatch> hah
[21:16] <redir> did I just delete my shelf by removing the lightweight checkout
[21:16] <redir> ?
[21:16] <hatch> tbh im not sure
[21:16] <hatch> is there a parent .bzr dir?
[21:17] <redir> sigh
[21:17] <redir> looks like I lost my shelf
[21:17] <hatch> :(
[21:17] <redir> don't know why I would have though that would be in the repo not the lightweight chekcout
[21:17] <redir> silly me
[21:19] <redir> I did a lightweight checkout from trunk and switched to a feature branch
[21:20] <redir> then shelved
[21:20] <redir> then redid the lightweight checkout and it is gone. I thought it would be in the new feature branch created next to trunk but it appears it was in teh lightweight co 
[21:23] <redir> c'est la vie
[22:07] <hatch> redir yeah, sorry there aren't a lot of bzr pros around any more
[22:07] <redir> luckily it was only a couple files
[22:08] <redir> which were still open in my editory
[22:08] <redir> so I ahve it. were is large i would have been more cautious
[22:08] <redir> whatevs
[22:09] <hatch> oh nice - sublime auto updates to the file on disk so I don't have that 'safety net' hehe
[22:09] <hatch> I should probably look into changing that 
[22:12] <redir> hatch: it does if the directory is the same. If you remove a dir from under it those files should still be around
[22:13] <redir> in sublime
[22:14] <hatch> oh that doesn't happen to me, the file goes blank
[22:15] <hatch> rick_h_ hey how goes the GSOC?
[22:36] <redir> hatch: hmm st2 or st3
[22:38] <hatch> st2
[22:41] <redir> st3 here
[22:43] <redir> which just seems to have crashed
[22:45] <hatch> heh, I'm sticking with st2 until some other brand makes it - it looks like Atom might be the next best
[22:45] <hatch> eventually
[22:52] <redir> eow later
[22:52] <hatch> enjoy your weekend