[00:16] <hatch> jujugui lf a review/qa https://github.com/juju/juju-gui/pull/204 plz and thanks
[00:16] <hatch> ^ huwshimi  if you have a chance today because this will then allow you to style the inspector to fit in the sidebar
[00:17] <huwshimi> hatch: I'll take a look
[00:17] <hatch> thanks
[00:18] <hatch> If it's all good can you :shipit: for me plz?
[00:19] <rick_h_> hatch: looking
[00:19] <hatch> DOH ci failure
[00:19] <rick_h_> doh!
[00:19] <hatch> and I JUST ran lint too lol
[00:19] <hatch> so much fail
[00:20] <hatch> almost done 
[00:20] <hatch> NFS makes lint and test running so much faster
[00:20] <hatch> run the full test suite in ~20s now
[00:20] <hatch> would be even faster if it wasn't for the 404's
[00:21] <hatch> fixed
[00:24] <huwshimi> hatch: What's the easiest way to get your branch?
[00:24] <huwshimi> For QA
[00:24] <hatch> huwshimi at the bottom there is a link which says 'command line'
[00:24] <hatch> check out develop and update it to the most recent version 
[00:25] <huwshimi> hatch: At the bottom of what?
[00:25] <hatch> then run 'step 1' from the thing which opens
[00:25] <hatch> the PR
[00:26] <hatch> huwshimi https://www.evernote.com/shard/s219/sh/86a14db3-0e37-4522-8be6-5958ad3e2a1a/63d67cfd49665ea37786a882fc3b78f9
[00:26] <hatch> but just do step 1
[00:26] <hatch> and make sure you're on develop when you run the commands in step 1 :)
[00:33] <huwshimi> hatch: I don't know enough to do a code review, but unless something is broken on my end it is not qaing very wel...
[00:33] <huwshimi> *well
[00:33] <hatch> no?
[00:35] <hatch> what is it doing? The inspector won't render properly in the sidebar if that's what you mean
[00:35] <huwshimi> hatch: So it's ok for it to appear above the browser content etc?
[00:36] <hatch> there should be no browser content
[00:36] <huwshimi> hatch: Well, I can get into a state where both are visible...
[00:36] <huwshimi> hatch: Want a hangout?
[00:36] <hatch> yes plz
[00:37] <rick_h_> wow that is fugly lol
[00:37] <hatch> haha
[00:38] <hatch> it's just not centered :)
[00:39] <rick_h_> ugh, so it renders under the editorial
[00:39] <rick_h_> so remove the top/right nad it starts to fit
[00:39] <rick_h_> hatch: can you override those in your branch at least?
[00:40] <rick_h_> .yui3-juju-inspector left/top hard coded values
[00:40] <rick_h_> and position abs
[00:40] <hatch> yeah I can - I just left that styling alone
[00:40] <rick_h_> hatch: yea, it's just a small set so it's more qa'able and such
[00:40] <rick_h_> set them to inherit and it 'works'
[00:40] <huwshimi> hatch: https://plus.google.com/hangouts/_/76cpi08kvdqlf8ok5huv2frop4?hl=en
[00:40] <hatch> I just want to see huwshimi's issue because it should destroy the charm lists before rendering the inspector
[00:41] <rick_h_> hatch: yea, it didn't
[00:41] <hatch> hmm
[00:41] <rick_h_> hatch: I'm betting because it doesn't have a search result it defaults to a editorial list
[00:41] <hatch> riight but locally it does
[00:41] <rick_h_> hmm, the list is empty, but it's there
[00:41] <rick_h_> bws-editorial
[00:41] <rick_h_> has three empty divs in it in my test
[00:42] <hatch> odd it calls
[00:42] <hatch>       if (editorial) { editorial.destroy(); }
[00:42] <hatch>       if (search) { search.destroy(); }
[00:42] <hatch> before rendering the inspector
[00:42] <hatch> so something else must be broken there
[00:47] <hatch> rick_h_ ok the issue huwshimi found is because we aren't relying on the state to render things into the sidebar
[00:47] <hatch> but that still doesn't explain why the destroy calls aren't working
[00:47] <rick_h_> hatch: well they're doing some work because the containers are empty
[00:48] <rick_h_> hatch: but something is still providing default empty containers
[00:48] <rick_h_> hatch: I think something is redrawing it, again because the state says so
[00:48] <hatch> entirely possible I suppose
[00:48] <rick_h_> hatch: you're probably still hitting the sidebar() function because nothing is saying not to
[00:49] <hatch> right - we need to sit down and outline every possible state combination 
[00:49] <hatch> and map the flow of the state rendering
[00:49] <rick_h_> hatch: right, that's what kadams and I are doing
[00:49] <hatch> oh cool
[00:50] <rick_h_> hatch: we're picking up the state branch and started to pull that out today. We should have an initial 'refactor of current state' tomorrow and can start to update it for the new stuff we need after that
[00:50] <hatch> ok great - so after all the xxx's and the little css cleanup this can land? 
[00:50] <hatch> it's really broken without the state :)
[00:50] <rick_h_> hatch: yes, ok from me
[00:50] <rick_h_> hatch: yes, and that's the reason it can land lol
[00:51] <hatch> haha
[00:51] <rick_h_> hatch: but yea, it's the highest priority atm and we'll get it unblocked and going
[00:51] <rick_h_> but with that we can ask huwshimi to start to style the inspect in the space :)
[00:51] <rick_h_> inspector that is
[00:51] <hatch> sure thing - so next card for me in the AM?
[00:51] <rick_h_> though a working tabbed inspector will be good to get in there as well
[00:52] <rick_h_> hatch: safari CI?
[00:52] <rick_h_> and removing the safari blocker 
[00:52] <rick_h_> hatch: ideally we'll do some releases tomorrow, not sure if we'll get it then or monday atm
[00:53] <rick_h_> hatch: and it'll give us tomorrow to try to get some state work landed 
[00:53] <hatch> ok sounds good
[00:54] <rick_h_> hatch: let me know if you need to chat on the CI thing in the morning. 
[00:55] <hatch> sure thing - I'll probably take a look again to remind myself what the issue was
[00:55] <rick_h_> hatch: yea, I never figure out what the issue was either
[00:59] <hatch> huwshimi there is a card called 'update new inspectors UI to fit within space of the sidebar...' You can probably use that for your styling
[00:59] <hatch> or part of it
[00:59] <hatch> it's a 4 so 2 days worth
[00:59] <huwshimi> hatch: OK.
[01:00] <hatch> rick_h_ I'll remove yours and kadams head off of the safari ci card
[01:00] <hatch> and put mine there
[01:00] <rick_h_> hatch: huwshimi but that's for both of them and some updated UI from luca
[01:00] <rick_h_> hatch: yep thanks, we were going to work on that today but the state stuff is higher priority
[01:01] <hatch> after the CI is up does safari get let in?
[01:01] <hatch> I think that was our last safari issue
[01:01] <rick_h_> hatch: yep
[01:01] <rick_h_> that's the last one
[01:01] <hatch> got it
[12:54] <rick_h_> benji: morning, I'm going to try to do a deploy of charmworld today. Anything on the bundle search issue that I should hold up on?
[12:54] <benji> rick_h_: given that tomorrow is Friday, I wouldn't hold the release
[12:54] <rick_h_> benji: ok, thanks
[13:08]  * frankban lunches
[13:32] <hatch> morning all
[13:39] <rick_h_> morning hatch 
[13:49] <rick_h_> hatch: that's a cute link there 
[14:01] <hatch> rick_h_ :)
[14:04] <hatch> -13C out with a high enough UV index to get a tan right now
[14:04] <hatch> lol
[14:05] <rick_h_> we're around 0C with rain that can't decide if it's wet or frozen
[14:08] <hatch> worst!
[14:08] <hatch> that's like what it's like on the coast sometimes - that's why I don't live there
[14:08] <rick_h_> hah
[14:09] <hatch> if it's raining it's got to be above at least 13C :)
[14:09] <benji> tan or windburn?  no one can tell
[14:09] <hatch> see what I did there with the 13's
[14:09] <hatch> haha
[14:09] <hatch> nope not windy at all because the temperature has been pretty stable
[14:10] <hatch> the best kiting wind is in spring and fall though when there are big swings in temerature
[14:10] <hatch> temperature event
[14:10] <hatch> even
[14:10] <hatch> ugh
[14:18] <hatch> sublime text users, I found a cool window manager https://sublime.wbond.net/packages/Origami
[14:19] <rick_h_> a window manager for your editor? 
[14:19]  * rick_h_ shakes head
[14:19] <hatch> tiling manager?
[14:19] <hatch> pane manager
[14:19] <hatch> lets go with pane manager :)
[14:19] <rick_h_> lol
[14:33] <hatch> jujugui manage.jujucharms.com is down
[14:34] <rick_h_> hatch: yep, working in #webops on it now
[14:34] <rick_h_> bad merge on upgrade
[14:34] <hatch> ohh
[14:34] <hatch> we need a staging server :P
[14:35] <rick_h_> well the cowboy was on prod and not staging so not sure how it'd help atm
[14:35] <hatch> ohh right I forgot about that
[14:36] <rick_h_> warned them the cowboy was there but it still went boom :)
[14:37] <hatch> safari failure could be an ssl issue
[14:37] <rick_h_> hatch: k, interesting and good to know
[14:37] <rick_h_> hatch: hmm, what ssl are we touching? I didn't think it was ssl'd on there
[14:38] <hatch> there are boneafied failing tests though too
[14:38] <hatch> when I run the test through sauce labs there is a safari alert about the ssl not being correct
[14:38] <rick_h_> hatch: duped locally? 
[14:38] <rick_h_> hmm, ok wonder what ssl thing it's hitting. 
[14:41] <hatch> might just be an aws thing
[14:41] <hatch> https://www.evernote.com/shard/s219/sh/72f2a602-ee2a-4ecc-9385-54aa3bc0941f/337790dc870b72c0bd1cdc6480bece24
[14:42] <rick_h_> hatch: hmm, can you look for an avenue to hit up saucelabs about this?
[14:42] <rick_h_> hatch: irc or bug or something?
[14:42] <rick_h_> as you're right, that's before it loads up on our url we're providing them
[14:43] <rick_h_> at least I don't think that's our websocket
[14:44] <hatch> we run a lot of tests
[14:44] <hatch> heh, trying to find the old ones
[14:44] <rick_h_> hatch: heh yea
[14:46] <hatch> interesting...the failures were intermittent before failing all the time
[14:47] <hatch> yup looks like it was the ssl issue https://saucelabs.com/tests/7fc11958a9ff4f859b5b17e79a777f39 just hangs on the 'SafariDriver Client' page but I'm assuming the alert is above the video layer
[14:50] <rick_h_> jujugui call in 10 please kanban
[14:53] <frankban> hatch: IIRC we use secure=false when deploying the GUI for tests, so, no SSL handling should be required. Looking at the jenkins failure, it seems there is a problem instantiating the remote webdriver (http://%s@ondemand.saucelabs.com:80/wd/hub), but not sure
[14:55] <rick_h_> benji: do you recall what the production ingest is these days? Is it still the supervisord run process?
[14:55] <hatch> frankban trying http
[14:55] <hatch> frankban same issue 
[14:55] <benji> rick_h_: I think so; it runs forever (and has enqueueing integrated into it so there is just the one job)
[14:56] <frankban> hatch: yeah, the problem seems to be in setupClass, so before even trying to fetch a browser URL
[14:56] <rick_h_> benji: k thanks for the sanity check
[14:58] <hatch> its redirecting to https
[14:58] <hatch> even when being given an http url
[15:00] <hatch> oh I had secure=true
[15:00] <hatch> heh
[15:00] <benji> I wonder if I'm in the right hangout.
[15:00] <rick_h_> jujugui on a call and running late
[15:00] <rick_h_> hatch: can you run please?
[15:01] <rick_h_> and I'll catch up in a few min
[15:21] <hatch> frankban I've noticed that when I use quickstart on amazon it takes a v.long time to bootstrap - thoughts on putting a message "waiting for provider" pinging the console every 30s to let the user know it's not hung?
[15:21] <hatch> or something to that effect
[15:22] <frankban> hatch: what's the last quickstart message before hanging?
[15:22] <hatch> I closed it....but it was something to the effect of "...Bootstrapping..."
[15:25] <hatch> feel free to tell me I'm stupid :) 
[15:28] <frankban> hatch: they introduced synchronous bootstrapping in 1.17.x. This is why it takes some time. In previous versions, the "retrieving environment status" was the slower bit. I am sure the goal to notify something to the user is worth the effort of spawning a separate thread to ping the terminal. One idea could be printing the synchronous "juju bootstrap" output to the console, but it contains some tecnical data not rea
[15:28] <frankban> lly interesting for the quickstart user I guess
[15:29] <hatch> Yeah - My only concern is for the user experience, so that they don't think it has hung as sometimes provisioning on the providers can take a while
[15:29] <frankban> hatch: what about a slack card to investigate those ideas?
[15:30] <hatch> yeah I'd be fine with that
[15:30] <hatch> slack card in the slack pit
[15:30] <hatch> lol
[15:30] <frankban> :-) cool
[15:34] <hatch> done
[15:38] <kadams54> guihelp Just submitted PR https://github.com/juju/juju-gui/pull/207 for refactoring state out of browser. As noted in the PR, it's just the first round; rick_h_ has plans… evil plans… for subsequent cleanup.
[15:38] <hatch> lol
[15:38] <hatch> on it
[15:38] <kadams54> Thanks
[15:42] <hatch> rick_h_ https://saucelabs.com/account it looks like it's running the selenium tests twice for each browser?
[15:59] <hatch> kadams54 review done
[16:02] <hatch> rick_h_ I think we should prioritize removing those http requests from the tests - the test runs now take over 40mins with safari in there :O
[16:03] <hatch> maybe timebox it at 1 point?
[16:18] <frankban> rick_h_: James page raised a concern re: quickstart in main/juju-core not in main. Please take a look at #juju when you are available
[16:22] <rick_h_> frankban: looking
[16:22] <frankban> rick_h_: thanks
[16:27] <kadams54> hatch: yeah, I'd like to see save() and update() disappear from the API entirely, but even if that isn't possible, maybe we can at least simplify.
[16:27] <hatch> kadams54 yeah - this state stuff is super confusing for pretty much everyone but rick_h_  :P So any way we can simplify it the better hehe
[16:27]  * hatch figures that's how rick_h_  felt about the viewlet stuff
[16:27] <hatch> :)
[16:27] <rick_h_> :)
[16:27] <kadams54> lol
[16:28] <rick_h_> like I said in the interview, what you throw comes back at you. We all have different brains
[16:28] <kadams54> OK… so you all saw our seating arrangement in standup… rick_h_ is behind me.
[16:28] <hatch> hahaha
[16:28] <kadams54> Considering his status as a ninja team lead, I find this very disconcerting.
[16:28] <kadams54> I need to get in before him and grab the back desk.
[16:29] <kadams54> Have my back against a wall and all that.
[16:29] <hatch> that still leaves you exposed from above 
[16:29] <hatch> maybe also be UNDER the back desk
[16:30] <kadams54> If I see rick_h_ scuttling across a ceiling, exorcism-style… I'm outta here ;-)
[16:31] <hatch> rick_h_ I think CI is borked
[16:31] <hatch> might need to restart the vm
[16:31] <hatch> http://ci.jujugui.org:8080/job/juju-gui/630/console
[16:31] <kadams54> Is that why my merge build failed? I was having a WTF moment…
[16:32] <hatch> yeah EADDRINUSE
[16:32] <rick_h_> hatch: sec ,just have to kill the process
[16:32] <hatch> ok cool
[16:32] <rick_h_> give me a minute, getting hammered from 4 sides 
[16:33] <hatch> I can try it
[16:33] <hatch> I've never done any the azure stuff
[16:34] <hatch> ohh I need the env details
[16:34] <hatch> ok I'll just wait :)
[16:38] <rick_h_> process killed, try again hatch kadams54_ 
[16:38] <hatch> trying again
[16:38] <hatch> rick_h_ did you get kadams54_  creds for Jenkins?
[16:38] <rick_h_> hatch: hmmm, probably not
[16:38] <rick_h_> :)
[16:39] <hatch> I can queue his up for now
[16:39] <kadams54_> lol
[16:39] <hatch> or if you wanted to show him
[16:39] <rick_h_> hatch: thanks, yea busy atm appreciate the help
[16:39] <kadams54_> I have access to Jenkins
[16:39] <hatch> oh ok cool
[16:40] <hatch> go to the juju-gui project
[16:40] <hatch> go to 'Build with Parameters'
[16:40] <kadams54_> Hmm, I don't see that…
[16:40] <hatch> and type origin/pr/<yourpr#>/merge
[16:40] <hatch> ok then you aren't logged in
[16:40] <rick_h_> right, he needs a login
[16:41] <kadams54_> Ah, yes.
[16:41] <hatch> ok I'll queue yours up
[16:41] <hatch> you can learn later :)
[16:41] <kadams54_> Thanks
[16:42] <hatch> queued
[16:43] <hatch> now I need to figure out how to work on this deployer
[16:43] <hatch> python...bzr...sheesh I'm going back in time here :P
[16:43]  * hatch ducks
[16:44] <kadams54_> Hah.
[16:44] <kadams54_> OK, lunching…
[16:44]  * rick_h_ goes for lunch afk
[16:47] <hatch> this is a pretty cool technique for styling selects http://www.bennadel.com/blog/2594-Using-Transparent-Select-Menus-To-Create-Styled-Menu-Roots.htm
[17:18] <lazyPower> pythonista TDD question: rails/rspec testing has this concept of loading fixture data after mocking out calls to an external api. I assume to achieve this i just import json and create a var with json.loads(open file descriptor) to get this? or is there a module I should be using
[17:18] <lazyPower> because python testing fixtures appear to reference a different area of the harness
[17:25] <hatch> frankban still around?
[17:25] <frankban> hatch: yes
[17:25] <hatch> got a second to give me a hand getting the juju deployer running in a virtualenv?
[17:26] <frankban> hatch: sure
[17:26] <hatch> awesome, so I followed the Installation instructions in the README exactly
[17:26] <hatch> (there are only 3 steps) :)
[17:26] <hatch> running it on Raring in vagrant
[17:27] <hatch> and now when I try and run it I get this error https://gist.github.com/hatched/b5f95ae4b378307f8690
[17:27] <hatch> sorry, Saucy I mean
[17:28] <hatch> it says it's missing a module so I'm guessing the installation is missing a step
[17:29] <frankban> hatch: yes, maybe, apt-get install python-bzrlib
[17:29] <hatch> installing
[17:30] <hatch> u da man
[17:30] <hatch> thx
[17:30] <hatch> :)
[17:30] <hatch> I'll add that to the docs
[17:30] <frankban> hatch: yes, it should be added, thanks
[17:31] <hatch> oh awesome, the tests don't pass
[17:31] <hatch> rofl
[17:31] <frankban> oh... error?
[17:33] <hatch> ahh it needs bzr to run the tests
[17:34] <hatch> I really like how easy python is to read
[17:34] <hatch> the tracebacks are pretty unhelpful, lots of indirection
[17:34] <hatch> but that just might be how it's written
[17:36] <hatch> oh boy the tests actually pull from a remote repo
[17:37] <hatch> 1 failure 2 errors
[17:37] <hatch> getting better
[17:41] <hatch> 1 failure
[17:41] <hatch> blarg
[17:42] <lazyPower> hatch: bzrlib is a crazy dependency and will give you random failures on clean environment building for testing.
[17:42] <lazyPower> it proxies through 6 locations to fetch the package
[17:42] <hatch> lol 
[17:42] <lazyPower> the random failures are thanks to one of those proxies timing out
[17:43] <hatch> so I should blame kapil for using a test which goes over the wire? :)
[17:43] <hatch> annnd Safari is back running on CI
[17:43] <hatch> boo yeah
[17:43] <lazyPower> hatch: this is exactly what I was talking about earlier. I need to mock an api request
[17:43] <lazyPower> and load "fixture data" to mock the response.
[17:44] <lazyPower> eg: stuff json in the mocked response so the code i'm testing continues with fake data.
[17:44] <hatch> yeah I can't help you there - with js, no problem - with Python, no idars
[17:44]  * lazyPower dies a little inside
[17:44] <lazyPower> i had so much hope hatch, you got my hopes up and dashed them
[17:44] <frankban> lazyPower: the mock library works well for those needs
[17:45]  * rick_h_ is back from lunch
[17:45] <lazyPower> frankban: im' mocking the request.post, can you point me for how to do the response? should i just json.loads(data) and assign it to response_object.data.return_value?
[17:45] <lazyPower> is that the proper method? or is there a module/library for helping do all of that setup?
[17:46] <frankban> lazyPower: to be clear, I am referring to http://www.voidspace.org.uk/python/mock/
[17:47] <lazyPower> frankban: from mock import patch, Mock
[17:47] <lazyPower> using the same lib, its got magickmock
[17:50] <frankban> lazyPower: in http://bazaar.launchpad.net/~juju-gui/juju-quickstart/trunk/view/head:/quickstart/tests/test_utils.py#L681 there is an example of a way to mock urllib.urlread
[17:50] <hatch> rick_h_ so I'd like to prioritize those http requests in the tests if we could...the CI is getting long in the tooth and causing timeeout issues now that Safari is in there
[17:51] <lazyPower> frankban: you're my new hero, thank you!
[17:51] <hatch> lazyPower what is your language of choice?
[17:51] <rick_h_> hatch: create a bug and card in maint. Where's it causing time issues? I thought we had 10min windows on each sauce run. We're no where near a 10min run 
[17:52] <hatch> rick_h_ sometimes the http request just hangs
[17:52] <hatch> no idea wy
[17:52] <rick_h_> hatch: in the on deck backlog please
[17:52] <hatch> sounds good
[17:52] <rick_h_> hatch: right, but do we have evidence that mocking the http requests avoid this?
[17:52] <frankban> lazyPower: welcome. Hope you find it helpful to obtain the same for whatever call you need to mock
[17:52] <rick_h_> I see dots, do we have anything to point to that connects them?
[17:52] <hatch> rick_h_ well if it doesn't make the http request it can't hang on it :)
[17:53] <rick_h_> hatch: ok, so where is the failure hanging on the http request?
[17:53] <frankban> lazyPower: in general, quickstart interacts with external data sources a lot, and so mock is used pervasively in the tests
[17:53] <hatch> http://ci.jujugui.org:8080/job/juju-gui/628/console
[17:54] <hatch> yuss passing juju-deployer tests
[17:54] <hatch> ok now I can get to work
[17:54] <hatch> well it's lunch
[17:56] <hatch> this of course was just the most recent failure
[17:56] <rick_h_> hatch: yea, I'm just trying to find evidence of the connection
[17:56] <rick_h_> hatch: are you saying this is the safari issue? Or is that just a side note here?
[17:57] <hatch> oh no it's just an issue - but because we now also have safari test runs are nearing 40mins
[17:57] <hatch> that's getting a little too long
[17:57] <hatch> imho
[17:57] <rick_h_> hatch: right, ok but that's not causing failures. That's different
[17:58] <hatch> well that one I linked you hung on that http request
[17:58] <rick_h_> ok that's fair I guess. last I looked we were at 26min with safari, will see
[17:58] <rick_h_> hatch: righ but it's the last line of output, what indicates 'hung'?
[17:58] <rick_h_> hatch: what makes this obvious vs a sauce issue, or something else?
[17:58] <hatch> I had to kill it at like 50mins which means it was probably sitting on that line for 20mins :)
[17:58] <rick_h_> right
[17:58] <rick_h_> our end does not handle sauce going away
[17:59] <rick_h_> so that time isn't a real time
[17:59] <rick_h_> so your merge that landed: Took 27 min
[17:59] <rick_h_> per jenkins
[17:59] <hatch> right I suppose
[18:00] <rick_h_> :) just keeping you honest 
[18:00] <hatch> lol that's fine
[18:00] <rick_h_> ok, I'm for fixing things but it feels like we've got 1) safari issue, not an issue now? 2) Tests take longer with 4 full browsers, we should fix 3) intermittent failures, cause unknown
[18:00] <hatch> safari issue appears to not be an issue
[18:00] <rick_h_> or is there more direct info and ^ is wrong
[18:01] <hatch> it 'just works' 
[18:01] <rick_h_> lovely
[18:01] <hatch> so Safari is now unblocked as well
[18:01] <hatch> no more warning
[18:01] <rick_h_> hatch: oh, did you land that as well in your diff?
[18:01] <hatch> yeah it was so trivial of a change
[18:01] <rick_h_> hatch: awesome ty much!
[18:02] <hatch> I added a test for it too so it's all good 
[18:02] <hatch> np
[18:02] <hatch> we should focus some QA'ing on it though
[18:02] <kadams54> woot
[18:02] <hatch> just to be safe
[18:02] <kadams54> I can help with that
[18:02] <rick_h_> hatch: yes, it's a friday card
[18:02] <hatch> oh cool
[18:02] <rick_h_> hatch: and I'm not going to do a gui release this week 
[18:02] <rick_h_> hatch: I'm going to wait for now, we only released charmworld/quickstart this cycle
[18:02] <hatch> probably a good idea - it's a little in flux atm :)
[18:02] <rick_h_> yep, agree with you
[18:03]  * rick_h_ takes meds for agreeing with hatch :P
[18:03] <hatch> lol!!
[18:03] <kadams54> hatch: did you get a chance to re-queue my PR merge build? (#206)
[18:03] <hatch> kadams54 yep I think it's running now
[18:03] <hatch> sec
[18:05] <hatch> kadams54 commented in the PR
[18:05] <hatch> you can shipit now 
[18:05] <hatch> kadams54 oh it's running again because trunk changed
[18:06] <hatch> http://ci.jujugui.org:8080/job/juju-gui/633/
[18:06] <hatch> oh well, I'm sure it'll all be good :)
[18:06] <rick_h_> lol
[18:07] <rick_h_> all good, ship ship ship! :)
[18:07] <kadams54> Yeah, rick_h_ just pointed out that build #632 was for PR 207; just didn't show in the Github conversation since it was kicked off manually
[18:07] <hatch> yeah we should probably fix that
[18:07] <kadams54> Since I've seen at least one good CI build, I'm fine doing :shipit:
[18:07] <hatch> ....todo
[18:07] <hatch> :)
[18:07] <kadams54> Assign it to the new guy
[18:07] <kadams54> Oh…
[18:07] <kadams54> Wait…
[18:07] <hatch> lol
[18:08] <hatch> I definitely want work done on the test suite - just need to convince people to stop assigning us feature tasks :P
[18:09] <kadams54> I've been telling rick_h_ the same thing!
[18:09] <kadams54> We tried to convince Mark R. yesterday.
[18:09] <kadams54> He was less enthusiastic ;-)
[18:09] <hatch> haha
[18:10] <rick_h_> hatch: hey, you knew machine view in a hurry was coming
[18:10] <rick_h_> it's #1 because honestly we're less than a month from vegas and they'll want to see it almost ready there
[18:10] <rick_h_> hatch: so I'm +1 on the idea, but let's remember where we're at :)
[18:11] <hatch> while() { printf("you knew %s in a hurry was coming", $project); }
[18:11] <rick_h_> hatch: now that's not fair. I recall weeks of maint at the end of the year 
[18:11] <hatch> hahahaha
[18:11] <rick_h_> :P
[18:12] <hatch> so after lunch I'm going to get going on this deployer stuff
[18:12] <hatch> now that i have it passing the tests
[18:13] <rick_h_> woot
[18:21] <benji> rick_h_: I'm stumped; the indexing problem I thought existed actually doesn't and now the unindexed bundle is suddenly indexed on prod
[18:22] <rick_h_> benji: ummm, ok
[18:22] <rick_h_> benji: well that's good that the problem doesn't exist. That would be a big use case hole. 
[18:22] <benji> my professional diagnosis is
[18:22] <benji> glitch in the matrix
[18:23] <rick_h_> benji: and if it's on prod now, we did the deploy today wihch kicked something in the pants
[18:23] <benji> yeah, that's what I was thinking
[18:23] <rick_h_> benji: which leads me to wanting that magic "clear the index and try again" button :/
[18:23] <rick_h_> benji: but yea, ok then. Thanks for chasing ghosts
[18:23] <rick_h_> benji: guess we'll call it a 'can't dupe' for now
[18:23] <benji> we need a "done" column (with scare quotes) for cards like this
[18:23] <rick_h_> lol
[18:24] <rick_h_> "done...for now"
[18:24] <benji> heh
[18:24] <rick_h_> benji: think you can do either of the other two cards before you get done? Or maybe hand off to bac for monday?
[18:24] <rick_h_> benji: and just call this one a wrap for now
[18:24]  * benji looks
[18:26] <benji> I should be able to do the bulk of the "add maintainers field" card by EOTM (end of team membership).
[18:27] <rick_h_> benji: cool thanks. It'll be a pure test land as we don't have any charms with that yet 
[18:27] <rick_h_> benji: thanks
[18:27] <benji> sounds good
[18:40] <rick_h_> jujugui reminder that we'll be doing planning poker and scheduling work for the next two weeeks tomorrow. If you've got time away you'd like to schedule please get it in so I can plan around it
[19:06] <hatch> rick_h_ is good friday or easter monday a holiday?
[19:06] <rick_h_> hatch: not in the US. next holiday is Monday, May 26Memorial Day
[19:07] <rick_h_> per https://www.opm.gov/policy-data-oversight/snow-dismissal-procedures/federal-holidays/#url=2014
[19:07] <hatch> ohh ok I'll have to check in Canada then
[19:08] <hatch> looks like it depends which religion I am
[19:08]  * hatch flips coin
[19:08] <rick_h_> Good FridayApril 18, FridayNational except QC
[19:08] <rick_h_> Easter MondayApril 21, MondayQC
[19:08] <rick_h_> is what I see?
[19:08] <hatch> QC....just can't play with the other kids
[19:08] <rick_h_> lol
[19:18] <hatch> holy smokes the kanban is all cleaned up
[19:18]  * hatch opens the backlog
[19:18] <hatch> *BOOM*
[19:19] <rick_h_> lol
[19:19] <rick_h_> welcome to my world
[19:21] <hatch> ugh the deployer has no comments
[19:23] <hatch> is this the best place for the python api docs? http://docs.python.org/2/
[19:23]  * hatch feels like captain obvious right now
[19:24] <rick_h_> hatch: good place to start
[19:25] <hatch> yeah I just want to reference the native api's make sure I'm using them properly
[19:30] <kadams54> Hah!
[19:30] <kadams54> 5 years of python development and I never thought about that
[19:30] <hatch> rofl!!
[19:30] <kadams54> I just googled "python <api term>"
[19:30] <hatch> what have you used?
[19:30] <kadams54> And went with the first hit :-)
[19:30] <hatch> haha
[19:30] <hatch> that's awesome
[19:31] <hatch> in js world you google `mdn <whatever>` so that you get the mdn docs for it :)
[19:31] <kadams54> Yup
[19:31] <kadams54> :-)
[19:32] <kadams54> OK, heading out now. Will check back in tonight to get a full 8 hours today.
[19:32] <rick_h_> kadams54: thanks for the great state work today
[19:32] <rick_h_> hopefully your brain still functions :P
[19:32] <hatch> k and v must be some convention in python land for for loops?
[19:33] <hatch> kadams54 lata 
[19:33] <kadams54> Yeah, k = key, v = value
[19:34] <kadams54> You'll see either depending on how lazy/succinct the dev was ;-)
[19:34] <kadams54> Not just for looping though - pretty much any place involving key/value pairs
[19:35] <hatch> rick_h_ when you have a moment for a quick hangout I have a question about some methods
[19:35] <rick_h_> hatch: sure thing
[19:36] <hatch> rick_h_ I figured it out
[19:36] <hatch> @classmethod first parameter is the class
[19:36] <rick_h_> hatch: yep
[19:37] <hatch> apparently you can just call a class with params to create a new class
[19:37] <hatch> interesting....
[19:37] <rick_h_> yep
[19:38] <rick_h_> hits the class's __init__ (initializer())
[19:39] <hatch> yeah that's pretty cool
[19:39] <hatch> ok code change complete....now to figure out how to use it....
[19:40] <hatch> https://gist.github.com/hatched/42dce5430e713fd83cc8 heh huge diff
[20:04] <hatch> umm ok using juju-quickstart in vagrant gave me the browser in the terminal....
[20:04] <hatch> lol wth
[20:05] <rick_h_> woot
[20:05] <hatch> apparently it's running w3m
[20:05] <rick_h_> <3 w3m, it's my mutt html email viewer
[20:06] <hatch> of course it is
[20:06] <hatch> lol
[20:06] <rick_h_> that and links2 for cli browser work
[20:06] <hatch> the GUI does not work very well in w3m haha
[20:07] <rick_h_> lol
[20:07] <rick_h_> no, no it does not
[20:07] <hatch> we should probably check if w3m is installed before opening up people into it :)
[20:08] <rick_h_> if that's your default browser go with it 
[20:08] <hatch> yeah I suppose hey?
[20:11] <rick_h_> jujugui I'm out. Have a nice evening folks. Time to go fight rush hour.
[20:12] <hatch> cya!
[20:12] <hatch> now I just need to find the unstable ppa for juju-core
[20:13] <hatch> ahah devel
[20:22] <Makyo> jujugui custom d3, requesting 2 QAs; most of the changes are hidden in ignored files: https://github.com/juju/juju-gui/pull/208
[20:22] <hatch> <3 You're using failtester :D 
[20:24] <Makyo> It's small and fast on LXCs :3
[20:24] <Makyo> :3
[20:24] <Makyo> :)
[20:24] <Makyo> Man
[20:24] <Makyo> Fingers went nuts
[20:24] <hatch> haha
[20:24] <Makyo> Having some left-brain/right-brain mixups.
[20:25] <hatch> :)
[20:27] <Makyo> Crap, if the CI fails, I know what it is.
[20:27] <hatch> it did
[20:27] <hatch> :)
[20:28] <Makyo> It's some D3 cruft creeping into the tests.
[20:45] <hatch> and of course my deployer python fix could not be as easy as I had hoped :)
[20:57] <hatch> Makyo is there a way I can run a python script and then trigger the debugger to stop at a specific spot for me to step through?
[20:57] <hatch> pdb doesn't mention a 'debbuger' like statement
[20:57] <hatch> and I don't really want to step through the whole thing
[20:57] <Makyo> hatch, import pdb; pdb.set_trace() where you want it to stop.
[20:58] <hatch> cool then I could go...
[20:58] <hatch> python -m pdb ./deployer/bin/juju-deployer -v --config ../restcomm.yaml -e amazon
[20:58] <hatch> is that the correct syntax?
[20:59] <hatch> I'm spoiled by the chrome dev tools :D
[20:59] <Makyo> That's the whole line.  `import pdb; pdb.set_trace()` and it will stop wherever that occurs inthe code.  No need for the -m
[20:59] <hatch> ohh ok cool
[20:59] <Makyo> Equivalent to `debugger;` in js
[21:00] <hatch> nice
[21:01] <hatch> what I woudln't give for a damn docbloc in the deployer code
[21:45] <hatch> wb
[21:52] <hatch> rick_h_ if you have a moment to chat about this deployer thing lemme know
[22:05] <huwshimi> Morning
[22:13] <hatch__> morning
[22:29] <rick_h_> hatch: joining AU call now
[22:29] <rick_h_> huwshimi: morning
[22:42] <hatch> lol that was odd
[22:46] <hatch> oops I forgot destroying services leaves the machine hanging around