[00:09] <huwshimi> hatch: This bug still exists: https://bugs.launchpad.net/juju-gui/+bug/1321558
[00:09] <_mup_> Bug #1321558: Destroying a service leaves inspector visible <juju-gui:Triaged> <https://launchpad.net/bugs/1321558>
[00:12] <huwshimi> hatch: Also, your caching branch is lovely!
[00:21] <rick_h_> huwshimi: hmm, that was marked as fixed. The card for that was done by Makyo 
[00:21] <huwshimi> rick_h_: Was the one for hiding the ghost inspector on deploy?
[00:22] <huwshimi> *that the
[00:22] <rick_h_> huwshimi: no, that bug you linked above on the destroying leave the inspector open
[00:22] <rick_h_> huwshimi: moved the card into urgent maint. 
[00:22] <rick_h_> Makyo: ^ 
[00:22] <huwshimi> rick_h_: Oh, I mean, didn't Makyo do the one about hiding the ghost inspector on deploy
[00:23] <rick_h_> huwshimi: not sure, I just did a search on the bug number in the kanban board and found the card
[00:23] <huwshimi> oh I see
[00:23] <rick_h_> I'll have to chase down the branch that was submitted and see what is up
[00:24] <rick_h_> huwshimi: but please make sure to note that one and the card in an email summary of the QA results please
[00:24] <hatch> huwshimi thanks :)
[00:24] <huwshimi> rick_h_: Will do, I have some small visual cleanups that I'll do myself today
[00:24] <rick_h_> huwshimi: awesome thanks
[00:28] <hatch> is comingsoon very slow for you guys?
[00:28] <hatch> oh maybe it's just me
[00:28] <rick_h_> hatch: no
[00:28] <hatch> huwshimi in your bug, how do you reproduce it?
[00:29] <hatch> can you add steps because I am not able to reproduce on comingsoon
[00:37] <huwshimi> hatch: I've added them to the bug: https://bugs.launchpad.net/juju-gui/+bug/1321558
[00:37] <_mup_> Bug #1321558: Destroying a service leaves inspector visible <juju-gui:Triaged> <https://launchpad.net/bugs/1321558>
[00:38] <hatch> huwshimi thanks, the bug only happens with ghost services not deployed ones
[00:38] <hatch> should be an easy fix the url isn't changing so just needs to fire a changestate event
[00:39] <hatch> good catch though
[00:40] <huwshimi> hatch: Ah yes, you are right. I thought I had reproduced it on a deployed service, but can't seem to now.
[00:41] <hatch> yeah, just looked, huwshimi  if you have time today you could probably bang out a fix for it real quick-like :)
[00:41] <hatch> think you might have time?
[00:41] <hatch> if not I can probably do it while watching some tv tonight heh
[00:43] <hatch> huwshimi here is the fix (sans tests) https://gist.github.com/b85f7d0ebdbf05ee0632
[00:43] <hatch> :)
[00:44] <huwshimi> hatch: It's ok I'll do it
[00:44] <rick_h_> hah! just used the chrome dev tools "copy a cURL" feature. sweetness
[00:45] <huwshimi> hatch: Unless you get to it first :)
[00:45] <hatch> rick_h_ haha cool, I've always wanted to use that :)
[00:45] <hatch> huwshimi true, although I have to start cooking supper right away so it won't be for a few hours for sure
[00:46] <rick_h_> needed a QA bundle file so went to the gui, went to code, loaded the bundle file and copied the curl command from the network tab to download it :)
[00:46] <hatch> keep me posted if you do tackle it
[00:46] <hatch> haha nice nice
[00:46] <huwshimi> hatch: Yep, I'll let you know if I start
[00:48] <rick_h_> bwuhahaha BradCrittenden you rule. <3 this
[01:00] <rick_h_> 920563
[03:27] <hatch> huwshimi I'm going to fix that bug now
[03:27] <huwshimi> hatch: OK :)
[03:27] <hatch> just watched some House of Cards and Orange is the new Black
[03:28] <hatch> need a break
[03:28] <hatch> lol
[03:28] <rick_h_> lol
[04:08] <hatch> huwshimi bug is fixed if you want to take a look for review/qa if you find some time
[04:09] <huwshimi> hatch: Ah sure, let me take a look
[04:09] <hatch> huwshimi I'm hopping offline, if alls good feel free to shipit
[04:09] <huwshimi> hatch: Sure
[04:09] <hatch> thanks, have a good night
[04:10] <huwshimi> hatch: You too
[08:55] <frankban> morning rogpeppe1: is juju/charm ready to be used?
[08:56] <rogpeppe1> frankban: yeah
[08:56] <rogpeppe1> frankban: i'm just about to push a branch that changes juju-core to use it
[08:57] <frankban> rogpeppe1: cool
[09:05] <frankban> rogpeppe1: could you please review https://github.com/juju/juju/pull/73 ?
[09:07] <rogpeppe1> frankban: looking
[09:07] <frankban> thanks
[09:09] <rogpeppe1> frankban: the PR doesn't seem to update dependencies.tsv - is that because it's been done in a previous PR?
[09:09] <frankban> rogpeppe1: yes, http.go was moved to external testing some days ago
[09:10] <rogpeppe1> frankban: LGTM then
[09:10] <frankban> rogpeppe1: thanks
[09:11] <frankban> rogpeppe1: I'll start the store migration right after you merge your current branch
[09:11] <rogpeppe1> frankban: cool. am currrently running the tests.
[09:20] <rogpeppe1> frankban: https://github.com/juju/juju/pull/74
[09:20] <frankban> rogpeppe1: looking
[09:21] <frankban> rogpeppe1: could you please create a juju/store repo and give me permissions?
[09:21] <rogpeppe1> frankban: sure
[09:22] <rogpeppe1> frankban: i wonder if the repo should be named "charmstore". what do you think?
[09:23] <frankban> rogpeppe1: it will also be a bundle store in the future. So I guess store can be ok, but that's not a strong opinion
[09:23] <rogpeppe1> frankban: bundles are bundles of charms, really
[09:23] <rogpeppe1> frankban: i'll raise it in #juju-dev
[09:23] <frankban> rogpeppe1: yeah
[09:27] <frankban> rogpeppe1: what about github.com/bmizerany/assert and deps? were they missing?
[09:27] <rogpeppe1> frankban: yup
[09:28] <frankban> rogpeppe1: LGTM
[09:59] <rogpeppe> frankban: i've created the repo and added juju-hackers as collaborators
[10:00] <rogpeppe> frankban: github.com/juju/charmstore
[10:00] <frankban> rogpeppe: cool, thanks. I'll wait for your branch to land and then start mgrating the store
[10:02] <frankban> rogpeppe: you have a conflict
[10:02] <rogpeppe> frankban: oh, darn
[11:01] <frankban> rogpeppe: how is it going?
[11:02] <rogpeppe> frankban: running tests again after merging
[11:02] <rogpeppe> frankban: worker/uniter/debug just timed out
[11:02] <frankban> rogpeppe: :-/
[11:03] <frankban> rogpeppe: some of the tests seems to have some weakness
[11:03] <rogpeppe> frankban: but just passed when i ran it again
[11:03] <rogpeppe> frankban: yeah
[11:03] <rogpeppe> frankban: it took 0.2s to run the second time
[11:03] <frankban> rogpeppe: heh
[11:07] <rogpeppe> frankban: my computer just decided to reboot randomly
[11:08] <frankban> :-/
[11:08] <rogpeppe> once upon a time if the kernel panicked, you'd see some kind of a message
[11:08] <frankban> rogpeppe: so what do you think about this plan: I will 1) migrate store 2) add README etc... 3) change core to use external store in the few places it is imported. You a) wait for 2 (add README etc) b) add to charmstore the server entry points (e.g. cmd/charmd/main.go), including README updates on how to start the charmstore server and c) remove those bits from core
[11:14] <frankban> rogpeppe1: ^^^
[11:14] <rogpeppe1> frankban: i haven't seen anything, sorry
[11:15] <frankban> rogpeppe1: so what do you think about this plan: I will 1) migrate store 2) add README etc... 3) change core to use external store in the few places it is imported. You a) wait for 2 (add README etc) b) add to charmstore the server entry points (e.g. cmd/charmd/main.go), including README updates on how to start the charmstore server and c) remove those bits from core
[11:17]  * rogpeppe1 thinks
[11:19] <rogpeppe1> frankban: how about, instead, migrating store and cmd/{charmd,charmload,charm-admin} all together. then there's nothing in core that imports store
[11:20] <rogpeppe1> frankban: because those commands feel like they're more part of the charm store than juju-core itself
[11:20] <rogpeppe1> frankban: i will suggest that in #juju-dev
[11:22] <frankban> rogpeppe1: charm-admin depends on juju/cmd. That said, the result is the same, b) and c) are about doing that move. My proposal is just to proceed with incremental steps, so that mechanical branches are really mechanical
[11:22] <frankban> rogpeppe1: so, focus on the goal of having an external store, and then move the commands where they belong
[11:23] <rogpeppe1> frankban: ah, i see
[11:23] <rogpeppe1> frankban: yeah, your approach seems fine
[11:23] <frankban> rogpeppe1: cool
[11:30] <frankban> rogpeppe1: uhm: your merge failed: godeps: cannot parse "/mnt/jenkinshome/jobs/github-merge-juju/workspace/tmp.o7sFxEIu8x/RELEASE/src/github.com/juju/juju/dependencies.tsv": cannot find directory for "github.com/bmizerany/assert": not found in GOPATH
[11:30] <rogpeppe1> frankban: oh frick
[11:30] <rogpeppe1> frankban: thanks
[11:31] <rogpeppe1> frankban: i'll remove that dependency for the time being
[11:32] <frankban> rogpeppe1: +1
[11:34] <BradCrittenden> morning rick_h_
[11:35] <frankban> rogpeppe1: created the cards for the plan above
[11:36] <rogpeppe1> frankban: lovely, ta
[12:08] <rick_h_> bac: morning
[12:08] <bac> hi rick_h_.  what was your message from last night about?  the discussing in vague terms my awesomeness.
[12:09] <rick_h_> bac: QA went well for me yesterday. Had one note where if the terminal window is small, and you go in to 'use' one of the environments, you have to scroll down with the down arrow before you can select buttons
[12:09] <rick_h_> bac: oh, just was so cool to deploy a bundle and such from OSX. 
[12:09] <bac> yeah, pretty sweet
[12:11] <bac> rick_h_: is that term size issue os x specific or would that be the case on linux too?
[12:12] <rick_h_> bac: I think it'll be any terminal. I don't notice it because of the bigger display/terminals I use on linux vs OSX the default is so small
[12:13] <rick_h_> bac: so I was debating about filing a bug and wanted to see if anyone else ran across it during qa
[12:14] <bac> rick_h_: i tested the interactive stuff when i first started the process but have not made it a part of general QA as the interactive piece has been static.  so i'm glad you saw this issue.
[12:16] <rick_h_> bac: just tried it out here on linux and yep, it's just a general thing with the UI. I happened to have a terminal of *just* the right height where I could seee the buttons, but there was a small amount of scoll available
[12:17] <rick_h_> bac: so definitely nothing block about and not even sure it's something we can do something about
[12:19] <frankban> rick_h_: we can make the buttons always visible (like the status bar): I would consider this a minor/nice to have and not a release blocker.
[12:21] <rick_h_> frankban: cool, I'll file a bug then for now.
[12:21] <rick_h_> bac: but QA went well for me and was very exciting to try out after writing docs and emails all day :)
[12:22] <bac> rick_h_: cool.  i'll wait for kyle to have a go and then do the release if all is good.
[12:22] <rick_h_> bac: sounds good
[12:41] <bac> frankban: if you have a moment could you review https://codereview.appspot.com/103310043  -- it has updates to the HACKING doc for new release procedures.  You may want to read the whole section carefully, not just the changes in this branch.  I've landed a few mods there self-reviewed.
[12:42] <frankban> bac: I will
[12:42] <frankban> rogpeppe1: could you please take a look at https://github.com/juju/charmstore/pull/1 ?
[12:42] <rogpeppe1> frankban: looking
[12:43] <rogpeppe1> frankban: LGTM
[12:43] <frankban> rogpeppe1: thanks
[13:06] <frankban> rogpeppe1: another one? https://github.com/juju/charmstore/pull/2
[13:06] <rogpeppe1> frankban: looking
[13:07] <rogpeppe1> frankban: LGTM
[13:07] <frankban> rogpeppe1: thank you!
[13:16] <jcsackett> morning all.
[13:17] <rick_h_> morning jcsackett 
[13:17] <rick_h_> jcsackett: can you assis with release today? QA/review Huw's branch and do some QA please. 
[13:17] <rick_h_> assist that is
[13:18] <jcsackett> rick_h_: was already planning on it--saw your email.
[13:18] <rick_h_> jcsackett: ty much
[13:18] <jcsackett> i'll start with Huw's branch and then start whacking the GUI. we have specific areas we're worried about?
[13:19] <rick_h_> jcsackett: we're just making the inspector left release. So with no flags, just does anything in the GUI have an issue before we release and update jujucharms.com with it
[13:20] <jcsackett> no flags, got it.
[13:28] <frankban> rogpeppe1: last one for the store: https://github.com/juju/juju/pull/76
[13:28] <rogpeppe1> frankban: cool
[13:28] <rogpeppe1> frankban: looking
[13:28] <frankban> thnaks
[13:28] <frankban> bac: review done
[13:28] <bac> ty
[13:29] <rogpeppe1> frankban: LGTM
[13:29] <frankban> rogpeppe1: thank you, merging
[13:42] <jcsackett> rick_h_: huw's branch is good; there's no reason to hold off on shipping it, is there?
[13:43] <rick_h_> jcsackett: nope thanks
[13:44] <frankban> bac: replied
[13:59] <hatch> github added a 'jump to file' button
[14:00] <hatch> kadams54 did you see my comment on your PR?
[14:01] <kadams54> I did.
[14:01]  * rogpeppe1 lunches
[14:02] <bac> frankban: yeah, that step was attempting to do two things: use pre-booted env and remote bundle.  i'll beef up the description.
[14:02] <kadams54> Here's what I think is happening: the machine view panel… er… view has at least one child view, which means the child view's container is connected to a child node.
[14:02] <kadams54> So when container.empty() is called, the child node is removed
[14:03] <kadams54> And when the destructor is called on the child view, it attempts to empty its container and throws an error because there's no longer an associated DOM node.
[14:03] <bac> rick_h_: the date in the first sentence of https://docs.google.com/a/canonical.com/document/d/1PI4XPNxVUP3mXqce-jxtT5KgqdZoTuvJZ71W-mSiCZg/edit  does not match the later date
[14:03] <kadams54> getDOMNode returns null
[14:07] <hatch> kadams54 right, but there should be no child view rendered into the createMachine view
[14:07] <hatch> if there is then something is wrong
[14:07] <hatch> create machine view should be managing it's own child views (if there are any)
[14:09] <kadams54> I think there are quite a few child views… machine headers, service scale up, create machine, etc.
[14:09] <kadams54> The one that started erroring when I changed to container.empty() was service-scale-up-view.js
[14:09] <hatch> yeah....but create machine and scale up are siblings
[14:09] <hatch> not parent/child
[14:09] <kadams54> Maybe, but not in the DOM
[14:10] <hatch> well then the DOM structure is incorrect
[14:11] <hatch> you can't have sibling views that require one to be rendered into the other
[14:11] <kadams54> machine-view-panel.js, line 848 - the view passes a node as the container for ServiceScaleUpView
[14:11] <kadams54> That node is a child of MV's container
[14:12] <hatch> right
[14:12] <hatch> so why does another child of machine-view-panel destroy that node?
[14:13] <kadams54> Another child doesn't destroy it
[14:13] <kadams54> machine-view-panel itself destroys it, when container.empty() is called in machine-view-panel's destructor
[14:13] <bac> kadams54: you still willing/have time to do the quickstart QA this morning?
[14:13] <kadams54> bac: Yeah, I started on that last night
[14:13] <bac> oh, cool
[14:14] <hatch> kadams54 no the empty() is called in 'createMachineView' not 'machineViewPanel'
[14:14] <hatch> kadams54 https://github.com/juju/juju-gui/pull/375/files#r13618728
[14:15] <rick_h_> bac: ty, updated
[14:16] <kadams54> hatch: Ah, that's my problem :-) For some reason I changed line 901 in machine-view-panel.js :-)
[14:17] <hatch> lol oh boy
[14:17] <jcsackett> rick_h_: one minor bug that i believe is linked to inspector left https://bugs.launchpad.net/juju-gui/+bug/1328932
[14:17] <_mup_> Bug #1328932: "tutorial" link under "help & feedback" sends you to /sidebar and does nothing <juju-gui:New> <https://launchpad.net/bugs/1328932>
[14:17] <jcsackett> not remotely done looking yet.
[14:17] <rick_h_> jcsackett: rgr, ty looking
[14:18] <hatch> rick_h_ jcsackett I'll take it
[14:18] <rick_h_> hatch: rgr ty
[14:29] <bac> frankban: here is a new section http://paste.ubuntu.com/7628821/  - i've tested that the steps work.
[14:31] <hatch> hmm looks like onboarding can never BE rendered any longer, good catch jc
[14:39] <frankban> bac: looks good
[14:39] <hatch> rick_h_ low priority but should probably get some new assets from UX https://bugs.launchpad.net/juju-gui/+bug/1328936
[14:39] <_mup_> Bug #1328936: onboarding now puts the inspector in the incorrect location <juju-gui:New> <https://launchpad.net/bugs/1328936>
[14:40] <rick_h_> hatch: oh ouch, yea. Not sure I agree on low priority though
[14:40] <rick_h_> luca: ^
[14:41] <luca> rick_h_: ah yeah
[14:41] <rick_h_> luca: I feel like that should block our release today. 
[14:41] <luca> rick_h_: if I remember right, they are just images that Spencer made.
[14:42] <rick_h_> hatch: what's the file name? 
[14:42] <luca> rick_h_:  is that correct?
[14:42] <rick_h_> luca: correct
[14:42] <rick_h_> I'm trying to find the one we're using right now
[14:43] <hatch> umm, I broke it, lemme get it back working and grab the file name :)
[14:43] <hatch> juju-ui/assets/images/non-sprites/onboarding/3-inspector.png
[14:44] <hatch> rick_h_ luca  the issue we will have though is that the charmbrowser will be rendered underneath the new inspector image
[14:44] <hatch> so it's more work than simply changing the image
[14:44] <rick_h_> hatch: oh, but we can work with this image
[14:44] <rick_h_> hatch: we just have to relocate it and cover the sidebar
[14:45] <hatch> it'll only cover part of it
[14:45] <hatch> which may look worse :)
[14:45] <luca> rick_h_: Spencer can create a new image of the inspector
[14:45] <rick_h_> right, but I mean cover the sidebar (entirely) and then put this image on there
[14:45] <luca> rick_h_: he’s busy doing the google mocks but once he’s done he can send one over
[14:45] <rick_h_> luca: ok, but we'll have a height issue regardless
[14:45] <rick_h_> We have to solve this better than updating the image
[14:45] <hatch> the sidebar is 100% height, so that image will need to be like 3000px tall to accommodate all screens 
[14:46] <luca> hatch: I see :)
[14:46] <rick_h_> right, thus we use a smaller image that's the 'top part' of a demo inspector, cover all of the sidebar and have that kindn of floating in place
[14:47] <hatch> heh, a mask in a mask
[14:47] <rick_h_> :)
[14:47] <hatch> I foresee problems in out future
[14:47] <hatch> our!
[14:49] <rick_h_> huw can do it :)
[14:50] <hatch> well we could create a fake service and show the inspector for that service
[14:50] <hatch> that's probably going to be the end goal
[14:53] <luca> rick_h_: hatch do you need me to action anything?
[14:54] <hatch> rick_h_ I'm not sure we want to try and do this pre-release
[14:55] <hatch> I think there will be dragons here which may end up causing us to push release
[14:59] <hatch> jujugui call in dos
[14:59] <hatch> jujugui call in Un
[14:59] <jcsackett> rick_h_, hatch: i've got another one: https://bugs.launchpad.net/juju-gui/+bug/1328941
[14:59] <_mup_> Bug #1328941: Deploying a local charm shows a compacted inspector <juju-gui:New> <https://launchpad.net/bugs/1328941>
[14:59] <rick_h_> jujugui on the phone with ramm at the moment, might be late
[14:59] <hatch> ok I can run it
[14:59] <hatch> jcsackett ok can you make a card in urgent plx
[14:59] <jcsackett> hatch: yup, marking the bug as high too. unless we feel "critical" is better.
[15:00] <hatch> jcsackett high is fine, we'll do it right away either way
[15:01] <hatch> jujugui call now
[15:04] <rick_h_> jcsackett: ^ antdillon 
[15:17] <bac> kadams54: thanks for your help doing the QA.  please ping me when you're done.
[15:17] <kadams54> bac: will do
[15:20] <hatch> the tow truck drivers are driving around and honking the horn in front of peoples cars to get them to move it before they tow it....that's pretty nice
[15:20] <hatch> I mean...the big yellow signs have only been here for 5 days....
[15:20] <hatch> but still nice :)
[15:34] <hatch> jujugui lf a review/qa for https://github.com/juju/juju-gui/pull/379 plz and thx
[15:36] <frankban> hatch: looking
[15:36] <hatch> thanks
[15:39] <hatch> jcsackett looking at your screen shots remind me of what internet was like in the 90s :P
[15:41] <jcsackett> hatch: yeah; it's something weird with shutter.
[15:41] <jcsackett> i get great screenshots, and then the moment shutter does anything with them, they turn into horribly compressed jpegs without any chance of recovering them.
[15:41] <frankban> hatch: when I visit a charm details page and then close the panel, the onboarding is shown. Is that the expected behavior?
[15:41] <jcsackett> i haven't figured out what's going on--it didn't used to have this issue.
[15:42] <hatch> frankban if you dismiss it once then that doesn't happen, correct?
[15:42] <frankban> hatch: yes
[15:42] <hatch> frankban tough to say.... luca ^
[15:43] <hatch> frankban I'm pretty confident that that is how it should stay...
[15:43] <frankban> hatch: ok
[15:44] <hatch> you don't want to necessarily miss out on the onboarding just because you clicked a link to view some charm details
[15:44] <hatch> at least thats my reasoning
[15:44] <luca> hatch: frankban you mean that when you visit Juju for the first time and you’ve been linked to a charm details and you close the details the onboarding shows?
[15:45] <hatch> luca no if you click a link to charm details
[15:45] <hatch> but you've never been to juju before
[15:45] <hatch> we show the details w/o the onboarding
[15:45] <hatch> but when you then close those details, we show the onboarding
[15:46] <frankban> luca, hatch: I think you are describing the same path...
[15:46] <hatch> oh.....yeah, I read it wrong
[15:46] <frankban> and you are both right
[15:46] <hatch> English is hard...
[15:46] <hatch> lol
[15:47] <luca> hatch: rofl
[15:47] <luca> frankban: hatch that is expected behaviour
[15:47] <hatch> haha yay
[15:47] <frankban> cool
[15:47] <frankban> hatch: then QA is good
[15:48] <hatch> sweet shippin!
[15:48] <hatch> frankban actually, can you comment on the PR THEN i'll ship :)
[15:48] <hatch> there it is!
[15:49] <frankban> hatch: done
[15:51] <hatch> hmm this local inspector business is probably gona be some work
[15:51] <hatch> poo
[15:53] <jcastro> https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1317939
[15:53] <_mup_> Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>
[15:54] <jcastro> can I get some eyeballs here so we can get this fixed in utopic so we can get it backported to trusty?
[15:57] <rbasak> jcastro: I'm your guy. I've been working on this for a while.
[15:58] <rbasak> jcastro: there have been process issues getting in the way, and I've been working on resolving them permanently.
[15:58] <rbasak> jcastro: right now the blocker is that juju-core ftbfs on utopic on powerpc, and I need this to land in utopic to fix juju-quickstart in utopic, and with that I'll be able to SRU to Trusty.
[16:14] <jcastro> rick_h_, <patrick-uds> QUESTION: do you plan to make it possible to deploy a bundle with containing local charms in juju-gui?
[16:14] <jcastro> rick_h_, I will ask you during the wrap up
[16:28] <hatch> luca do the local charm inspectors also go 100% height in the left column? (thinking so, just want to confirm)
[16:28] <luca> hatch: they do
[16:29] <jcsackett> juju-gui: anyone QAing on safari?
[16:29] <hatch> luca thanks
[16:30] <hatch> jcsackett giver'
[16:31] <jcsackett> hatch: huh?
[16:32] <hatch> jus' giver' ?
[16:33] <jcsackett> i have no idea what you're saying.
[16:33] <jcsackett> dialects written in text tend to fail hard. :p
[16:33] <hatch> go hard?
[16:33] <hatch> you can do it?
[16:33] <jcsackett> ok. thanks.
[16:33] <jcsackett> :)
[16:33] <hatch> it's all yours
[16:33] <hatch> please sir, may  you do the safari qa
[16:34]  * jcsackett laughs
[16:34] <hatch> :D
[16:34] <jcsackett> i've never heard "giver'" before...is that "go for it", i'm guessing?
[16:34] <hatch> yeah - we say it all the time when doing something stupid
[16:34] <hatch> "ok dude giver'"
[16:35] <rick_h_> hatch: yea, that's pure canadian nonsense :P
[16:35] <hatch> haha
[16:36] <hatch> I looked up the urban dictionary definition....yeah there is some messed up stuff in there
[16:39] <jcsackett> juju-gui: if someone else has safari, can they please open the gui in coming soon and verify that scrollbars on the sidebar work? i'm almost certain this is my machine sucking, but we should double check.
[16:39] <hatch> looking
[16:40] <hatch> jcsackett working good here
[16:44] <jcsackett> hatch: awesome. well, downside, i can't QA on safari b/c my macbook is *oooold*. plusside, at least the GUI isn't completely hosed on safari. :p
[16:45] <hatch> haha, s'ok we have other osx'rs kadams54 bac frankban rick_h_  :D
[16:45] <jcsackett> hatch: if you've deployed an older version of a service, the upgrade section in the inspector should show the newer version, right? i'm not grossly misunderstanding 'upgrade' in this context, am i?
[16:46] <hatch> rick_h_ I propose we make a spreadsheet of our supported browsers/platforms and sandbox/real env and then people can put their name beside it when it qa's ok
[16:46] <hatch> jcsackett no, atm it now shows every version of the charm (And some which don't exist)
[16:47] <hatch> no, you're not misunderstanding it, it's just broken
[16:47] <hatch> :)
[16:47] <jcsackett> hatch: well, no, it seems to show every older version of the charm.
[16:47] <jcsackett> hatch: ok, as long as know that's broken.
[16:47] <hatch> yeah there are existing cards
[16:48] <jcsackett> hatch: is the upgrade path one then not something we're QAing? b/c there seems to be an inspector left issue in it as well if you actually click upgrade.
[16:48] <hatch> hmm.....
[16:48] <jcsackett> though triggering it is hard, since most of the time clicking "upgrade" doesn't seem to do anything.
[16:48] <hatch> I'm pretty sure that should still work. But it does list charms which don't exist
[16:49] <hatch> so the error may be caused by that
[16:50] <hatch> jcsackett it wouldn't hurt to create new bugs though then rick_h_  can go through and mark as duplicates if need be
[16:50] <rick_h_> oh sure :P
[16:50] <hatch> haha, well 2 bugs is better than 0 :)
[16:50] <rick_h_> hatch: all good, happy to help garden
[16:51] <jcsackett> destroying services leaving machines around is a juju-core issue, right?
[16:51] <rick_h_> hatch: I think the spreadsheet thing is something of formalizing the QA process we should do. I'm going to create a task for that. 
[16:51] <hatch> cool
[16:51] <rick_h_> jcsackett: yes, and there's a branch up for review that changes that
[16:51] <jcsackett> rick_h_: cool.
[16:51] <rick_h_> hatch: but I think that's a bit much for the moment 
[16:52] <hatch> s'ok!
[16:52] <rick_h_> ok, UOS session is done and out woot
[16:54] <rick_h_> jujugui UOS session if interested https://plus.google.com/116120911388966791792/posts/aLNHXFMW5DC
[16:55] <kadams54> UOS?
[16:55] <jcsackett> ubuntu online summit, i think.
[16:56] <hatch> rick_h_ thanks, watching
[16:56] <rick_h_> what jcsackett said
[16:56] <rick_h_> I'm trying to train myself to not use UDS 
[16:57] <hatch> we need to do a lot better marketing of these things, I only noticed it yesterday haha
[16:59] <jcsackett> hatch: i'm making a card in urgent for the upgrade bug i've found; if we decide we don't care for release feel free to alter bug and delete card.
[17:00] <jcsackett> ok, i need food.
[17:00] <rick_h_> jcsackett: ok, make sure you've got reproduction steps please
[17:00] <rick_h_> and I also need to find food now. Phew, busy morning
[17:00] <jcsackett> rick_h_: yup.
[17:01]  * rick_h_ runs away for a few min
[17:01] <jcsackett> rick_h_: i try to never file a bug without reproduction steps if i can avoid it.
[17:01]  * jcsackett runs away in the opposite direction
[17:02]  * rogpeppe1 is done for the day
[17:02] <rogpeppe1> g'night all
[17:03] <rick_h_> night rogpeppe1
[17:03] <rogpeppe1> rick_h_: see ya
[17:03] <rick_h_> jujugui wife is comandeering the mifi for part of tomorrow for dr home visits...I might be up no-net creek without a paddle. Cannot coffee shop as I have to be here during install
[17:04] <rick_h_> gah! imagine a world without internet access! The horror!
[17:04] <hatch> lol
[17:04] <rick_h_> I'll get someone to be a meeting backup for the cross team call in case I have no net tomorrow
[17:04] <rick_h_> anyway, really off to lunch
[17:05] <hatch> enjoy
[17:14] <bac> rick_h_: where's your real internet?
[17:15] <hatch> bac it's being upgraded to add more ips
[17:15] <hatch> business line or something
[17:16] <bac> oh, yeah, that
[17:16] <bac> i tune out people with their first-world internet woes
[17:19] <hatch> lol
[17:25] <kadams54> bac: sent you a PM… going to break for lunch but wanted to chat about some things I was seeing.
[17:26] <bac> kadams54: sorry i was at lunch and didn't see that on my return
[17:26] <kadams54> np
[17:26] <bac> kadams54: do you want to do a hangout?
[17:26] <kadams54> Sure
[17:27] <bac> kadams54: going into daily standup
[17:28] <kadams54> bac: I'm there…
[17:28] <rick_h_> bac: :P definitely first world
[17:29] <bac> kadams54: got kicked.  trying again
[19:01] <bac> jujugui: i forked the homebrew project into https://github.com/CanonicalJS/homebrew instead of jujugui.  how do i delete the fork?  (i'm sure there is a button i'm just not seeing.)
[19:02] <rick_h_> bac: sec, I might be able to move it. 
[19:02] <hatch> bac go into the settings for the repo and click delete
[19:02] <hatch> your fork of the repo that is
[19:02] <rick_h_> bac: where do you want it to be under? /juju/homebrew?
[19:03] <bac> rick_h_: jujugui/homebrew, no?
[19:03] <rick_h_> do we have a jujugui user/org? 
[19:03] <bac> rick_h_: yes
[19:03] <bac> rick_h_: is this not a thing: https://github.com/jujugui
[19:03] <rick_h_> bac: ah, that's the bot user. I'd just move it under /juju I think. We don't have any repos there. 
[19:03] <bac> rick_h_: ok, that works
[19:04] <rick_h_> bac: it's just a dummy user for CI interactions
[19:04] <rick_h_> bac: moved
[19:04] <bac> that's not unconfusing
[19:04] <rick_h_> https://github.com/juju/homebrew
[19:04] <bac> thanks
[19:04] <rick_h_> np
[19:06] <bac> rick_h_: my branch is juju-quickstart-formula
[19:06] <bac> rick_h_: so this would work:
[19:06] <bac> #git push git@github.com:juju/homebrew.git juju-quickstart-formula
[19:07] <rick_h_> bac: is your branch a fork of that juju/homebrew.git repo?
[19:07] <jcsackett> juju-gui: I have been knocked offline by a storm and my poor phone seems to not be up to the task of hot spotting today. 
[19:07] <jcsackett> I go in search of internet elsewhere. 
[19:07] <rick_h_> jcsackett: thanks for the heads up
[19:08] <bac> rick_h_: i think brew created a branch of the original.  i'm following the directions at https://github.com/Homebrew/homebrew/wiki/Formula-Cookbook after the 'Commit' heading
[19:08] <rick_h_> bac: looking
[19:09] <hatch> jcsackett darn I JUST needed to have a chat with you too :)
[19:09] <hatch> are you ok for ircing?
[19:09] <rick_h_> bac: looks ok then
[19:10] <bac> rick_h_: i get access denied.  should i be able to push there?
[19:11] <rick_h_> bac: hmm, I'd expect you to as you can to the gui, /me checks
[19:11] <bac> or my ssh keys are not set up
[19:11] <jcsackett> hatch: yeah, i can IRC from my phone, and i'm not in the car yet. what's up?
[19:12] <hatch> local charm drops use /local in the url and then convert to localType
[19:12] <hatch> but there is an issue with localType being converted to /local
[19:12] <hatch> so I CAN fix that
[19:12] <rick_h_> bac: updated
[19:12] <hatch> but is there a reason why you picked localType and not local?
[19:12] <hatch> I'd really prefer to have a single name instead of a odd rename just for the url
[19:12] <rick_h_> bac: they did some gardening now that core is on github. They don't follow our 'let everyone ahve admin' process
[19:13] <bac> rick_h_: i had not ssh-add my novel github key
[19:13] <bac> now it worked
[19:13] <rick_h_> bac: awesome
[19:13] <jcsackett> hatch: I think I was opposed to "local" as a variable name, since that sounds like a bool to me. 
[19:14] <jcsackett> But localType is a crap URL fragment. 
[19:14] <hatch> ok so are you ok with the rename just for the url?
[19:14] <jcsackett> If you want to s/localType/local I'm good. 
[19:15] <hatch> ok lemme think about it :)
[19:15] <hatch> just wanted to see if there was some other reason
[19:16] <jcsackett> No good ones, no. :p
[19:16] <hatch> haha ok lemme think about it
[19:16] <pitti> hello
[19:17] <rick_h_> howdy pitti 
[19:17] <pitti> so I was watching jcastro's UOS talk today and wanted to try juju-local again (a month or so ago it failed for me due to bug)
[19:18] <rick_h_> pitti: very cool
[19:18] <pitti> so I'm trying "juju quickstart" as in that tutorial; I get http://paste.ubuntu.com/7630057/ and now it's just hanging, and no running wget or similar
[19:18] <jcastro> rick_h_, we're mid session so marco and I can't help right now, but if you could help point him in the right direction that would be <3
[19:18] <pitti> any idea how I can check what's going on?
[19:18] <rick_h_> jcastro: k
[19:18] <rick_h_> pitti: what version of ubuntu are you on?
[19:19] <pitti> no container was created, and strace on the jujud bootstrap is just futex-waiting
[19:19] <pitti> rick_h_: utopic du jour
[19:20] <rick_h_> pitti: oh, bleeding edge. We're aware of some juju/quickstart bugs that we're working on getting landed. https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1317939
[19:20] <_mup_> Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>
[19:20] <rick_h_> pitti: and if you look in the comment there's a bug in getting juju updated in utopic holding that up right now
[19:20] <pitti> rick_h_: right, exactly that bug
[19:20] <rick_h_> pitti: so I'm not sure it will work properly
[19:21] <rick_h_> pitti: we're hoping juju gets updated soon and we can get our quickstart package updated and get it going
[19:21] <rick_h_> pitti: you can try the quickstart beta ppa
[19:21] <rick_h_> https://launchpad.net/~juju-gui/+archive/quickstart-beta
[19:21] <pitti> rick_h_: ack, thanks! so I didn't just screw up :)
[19:21] <rick_h_> that can get you the pending release ahead of time
[19:21] <rick_h_> pitti: no, I don't think so
[19:21] <pitti> I mean, not that there's a whole lot to screw up on a single command :)
[19:21] <rick_h_> pitti: I think you're smacking into the stuff we're all trying to get fixed up
[19:21] <rick_h_> lucky luck you :)
[19:22]  * pitti installs the PPA
[19:22] <rick_h_> pitti: note that I'm not sure it'll help you as the juju bug is still there, but I don't recall if that worked around the bug but our release is blocked
[19:23] <pitti> rick_h_: for testing I'd be ok to create trusty containers; I hope that's what the LXC bug is about? (container release, not host release)
[19:24] <rick_h_> pitti: I know the original issue was trusty containers, but the relaese is blocked on utopic builds. series series everywhere. 
[19:24] <rick_h_> but the beta package should get you around the original precise container issue
[19:24] <bac> rick_h_: the brew pull request has been submitted.  that project has 33 pull requests pending, dating back one week.  so i'm going to declare victory on my card, create a tracking card, and be done.
[19:24] <pitti> still hanging :/ and nothing in .juju/local/log/
[19:24] <rick_h_> bac: sounds good
[19:25] <rick_h_> pitti: :(
[19:25] <pitti> rick_h_: I suppose I'll re-try my luck with juju bootstrap etc.
[19:25] <pitti> I'm mostly interested in this for working on the CI airline wrt. autopkgtest, so trusty containers are totally fine for me
[19:26] <rick_h_> pitti: let me know if that works for you. My understanding is that it's a juju/utopic issue. The bug linked in https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1317939 leads through a few other bugs in juju. 
[19:26] <_mup_> Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>
[19:27] <rick_h_> pitti: so quickstart shouldn't be causing any issues
[19:27] <rick_h_> pitti: but definitely adding a card to our board to look at qa'ing what we do have under utopic, none of us have upgraded and checked it out yet
[19:27] <pitti> rick_h_: ah; I usually upgrade on day 1, dogfooding :)
[19:28] <rick_h_> pitti: <3 just sorry for the complications you hit. 
[19:28] <pitti> rick_h_: but I didn't see any log file etc. in .juju to see what's going on; hence my thought to call bootstrap directly, that might be a little more verbose?
[19:28] <pitti> rick_h_: no worries :)
[19:28] <rick_h_> pitti: --debug
[19:28] <rick_h_> pitti: I think that turns on verbose bootstraping
[19:28] <pitti> rick_h_: how would I manually bootstrap a "local" environment?
[19:29] <rick_h_> pitti: did you create one using quickstart? 
[19:29] <rick_h_> pitti: then just 'juju switch local && juju bootstrap'
[19:29] <pitti> ah, right, that already creates the yaml
[19:33] <pitti> hm, endless series of "juju.state open.go:101 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused" in .juju/local/cloud-init-output.log, and no lxc process or otherwise busy process
[19:33] <pitti> so I guess I'll just subscribe to these bugs and wait until they get fixed :)
[19:33] <pitti> thanks rick_h_ 
[19:33] <rick_h_> pitti: yea, that's the juju mongo bug
[19:33] <rick_h_> pitti: sorry, I think they're up for the next release next week
[19:33] <pitti> sounds nice
[19:33] <pitti> or I'll try it in a trusty VM
[19:34] <rick_h_> pitti: +1
[19:37] <pitti> rick_h_: oh, I just saw that juju-local/juju-core 1.18.4 claim to fix much of this, but are stuck in -proposed
[19:37] <rick_h_> pitti: right
[19:38] <rick_h_> pitti: there's some other blockers 
[19:38] <pitti> powerpc build failure apparently
[19:38] <rick_h_> pitti: they're working through it but not out yet
[19:38] <pitti> *nod*, thanks
[19:38]  * rick_h_ isn't 100% on top of it but watching it to unblock our juju-quickstart release
[19:44] <pitti> rick_h_: much much better with the proposed version :)
[19:44] <rick_h_> pitti: woot
[19:44] <rick_h_> jujugui approval for july 21 set, will have details and such tomorrow but feel free to start planning 
[19:45] <pitti> juju quickstart still defaults to building stuff for precise, but *shrug*, details :)
[19:46] <pitti> and it now fails with juju-quickstart: error: machine 1 is in an error state: error: open /var/lib/lxc/martin-local-machine-1/config: no such file or directory
[19:46] <rick_h_> pitti: well it uses your env for the default env
[19:46] <rick_h_> bah that came out wrong
[19:46] <pitti> so we have some hardcoded /var/lib/lxc/ somewhere (I have them in /scratch/lxc), but that's now much easier to tackle
[19:46] <rick_h_> the default series is defined in your environments.yaml
[19:46] <rick_h_> pitti: orly that one is interesting
[19:46] <pitti> rick_h_: right, I wiped .juju and restarted quickstart, that wrote a new yaml
[19:47] <rick_h_> pitti: ah, and that yaml uses lts as default series 
[19:49] <rick_h_> ok, I'm out for the day all. I'll do my best to be available online tomorrow as much as I can. 
[19:51] <pitti> filed as bug 1329049
[19:51] <_mup_> Bug #1329049: quickstart fails, hardcodes /var/lib/lxc/ somewhere <amd64> <apport-bug> <utopic> <juju-quickstart (Ubuntu):New> <https://launchpad.net/bugs/1329049>
[19:51] <pitti> rick_h_: good night!
[19:58] <hatch> rick_h_ so I'm going to split this bug into two cards, one for the styling and one for the technical bugs
[19:58] <hatch> I've fixed the technical bugs but the styling still needs work
[19:59] <hatch> huw can then do that one
[20:11] <bac> rick_h_: i'm having troubles with the builds for the PPA.  it is clinging to the 1.3.4.b1 name, not recognizing 1.3.4 is more current.  may have to bump to 1.3.5 if i cannot get it to update.  feels like i'm missing something.
[20:12] <rick_h_> bac: oh hmm, I know pypi should treat the b1, guess that might not work in debian packaging world
[20:12] <bac> yeah, pypi definitely did, requiring the --pre install flag
[20:12] <rick_h_> bac: honestly, if 1.3.5 works call it. I think I might have led your wrong on that sorry
[20:12] <bac> np
[20:34] <hatch> jujugui I need a review/qa for https://github.com/juju/juju-gui/pull/380 before Huw starts so he can take on the second part of this card.
[20:34] <kadams54> hatch: I can take a look
[20:34] <hatch> ahh crap I need to remove a comment
[20:34] <hatch> sec
[20:35] <hatch> kadams54 ok it's ready now
[20:35] <hatch> thanks
[20:35] <kadams54> yup
[20:39] <hatch> jujugui does anyone have a real env up?
[20:48] <hatch> rick_h_ I think that we can push the other ticket from jcsackett
[20:48] <hatch> the upgrade one
[20:57] <hatch> oh CI, go home, you're drunk
[20:58] <jcsackett> hatch: +1, upgrade is already hella broken.
[20:58] <hatch> jcsackett cool, moving it out of urgent
[20:58] <kadams54> hatch: what exactly should be fixed in this PR? I'm still seeing the empty sidebar after deploying the local charm.
[20:58] <hatch> you sure you have cleared your cache?
[20:58] <hatch> any errors in the console?
[20:59] <kadams54> OK, caching issue
[20:59] <kadams54> Now the only problem is the squashed inspector, which I take it is what Huw will be fixing.
[21:00] <hatch> well it's just not 100% height
[21:00] <hatch> it's no longer squashed
[21:00] <kadams54> True
[21:00] <hatch> it WAS way squashed :)
[21:00] <kadams54> Alright, looks ready to ship, commented as such in the PR.
[21:01] <hatch> cool - I'm going to wait for CI to pass 
[21:01] <kadams54> Assuming the build gets straightened out
[21:01] <hatch> it passes fine here
[21:01] <hatch> so hoping it's just being it stupid self
[21:20] <kadams54> EOD for me
[21:20] <kadams54> See everyone later
[21:20] <hatch> lata
[21:27] <hatch> rick_h_ anything you want me to start on before release?
[21:29] <rick_h_> hatch: can you QA/check out jcsackett's branch?
[21:29] <rick_h_> hatch: and any idea on kyle/huw's branch in review? I'm guessing he didn't get that updated due to the qa/etc work today
[21:29] <hatch> oh look at that
[21:30] <hatch> for sure
[21:30] <hatch> I THINK that one has landed
[21:30] <hatch> ....
[21:30] <hatch> he has nothing in the PR queue
[21:30] <rick_h_> hatch: oh hmm ok coolio then
[21:36] <jcastro> hey fellas
[21:36] <jcastro> wrt. "we should export bundle.yaml"
[21:37] <rick_h_> jcastro: disagree?
[21:37] <jcastro> yeah
[21:37] <jcastro> but it's only step 1
[21:37] <jcastro> I wonder if there's a bug for
[21:37] <jcastro> "envExport" 
[21:37] <jcastro> like, ideally
[21:37] <rick_h_> yes, there's a bug to allow the user to select a name on export
[21:37] <jcastro> I would click the button to export, and it would ask me "name this bundle"
[21:37] <jcastro> and then it would use that
[21:37] <jcastro> AND bundle.yaml
[21:37] <rick_h_> but this is just a drive by for the filename part
[21:37] <jcastro> rick_h_, excellent, <3
[21:38] <hatch> jcastro I saw you signed up for keybase
[21:38] <jcastro> yessir
[21:38] <hatch> https://keybase.io/hatch
[21:38] <jcastro> I need to figure out how to sign my new key with my old one
[21:39] <hatch> I'm trying to find a use for this
[21:39] <hatch> lol
[21:39] <rick_h_> lol
[21:39] <hatch> I uploaded the generated private key so I can do in browser decrypting
[21:39] <jcastro> gpg pokemon
[21:39] <jcastro> hah no you didn't
[21:39] <jcastro> you fell for that?
[21:39] <hatch> without doing that, what's the point in the service?
[21:39] <hatch> if you must have your computer then why do this at all
[21:40] <jcastro> the CLI is much nicer than gpg
[21:40] <jcastro> it's like, easy to use
[21:41] <hatch> well ok theres that
[21:41] <hatch> but yeah, if I ever come up with a real use for it then maybe I'll gen another key and not push it up
[21:41] <hatch> I don't use the key I pushed up for anything
[21:42] <hatch> maybe I just don't encrypt enough stuff lol
[21:43] <hatch> ok now I need another task... hmm
[21:43] <jcastro> yeah, pokemon
[21:44] <hatch> lol what
[21:47] <jcastro> collecting signatures, it's like pokemon
[21:49] <hatch> ohhh
[21:49] <hatch> pokekey
[21:49] <jcsackett> hatch: don't think i was online when i pinged you about this: looking at reload in service-inspector.js i see this https://pastebin.canonical.com/111543/
[21:50] <jcsackett> looks like a bit of flags.il leftover?
[21:50] <hatch> 2 secs need 2fa
[21:50] <jcsackett> kk.
[21:52] <hatch> jcsackett yep looks like that should have been switched over
[21:52] <hatch> although, I am wondering why I get it auto-reloaded
[21:56] <jcsackett> hatch: my power blew out, so I'm EoDing. Let's look at it tomorrow. 
[21:56] <hatch> yeah no problem - it's pretty low on the priorty list :)
[21:57] <hatch> enjoy lack of power
[21:58] <jcsackett> Thanks. :p
[23:00] <huwshimi> Morning
[23:01] <hatch> hey huwshimi 
[23:01] <hatch> I gots works fors yous
[23:01] <huwshimi> hatch: Hey
[23:01] <huwshimi> hatch: I saw that card
[23:01] <hatch> cool, so it's the last one blocking release 
[23:01] <hatch> I wasn't sure if you're familiar with how those inspectors are rendered so I figured I'd stick around
[23:01] <huwshimi> ah :)
[23:01] <huwshimi> hatch: I just need a local charm right?
[23:02] <hatch> yeah you can download the zip from my ghost charm one
[23:02] <hatch> https://github.com/hatched/ghost-charm
[23:02] <hatch> the big Download Zip button on the right
[23:03] <huwshimi> hatch: Ah yes, got it working
[23:03] <huwshimi> hatch: Anything else I need to take a look at?
[23:03] <hatch> https://github.com/juju/juju-gui/blob/master/app%2Fviews%2Finspectors%2Flocal-new-upgrade.js
[23:03] <hatch> https://github.com/juju/juju-gui/blob/master/app%2Fviews%2Finspectors%2Frequest-series.js
[23:04] <hatch> those are the two inspectors which need updating
[23:04] <huwshimi> Ah ok
[23:04] <hatch> I don't think so, maybe just do a once over, see if you can break it in any other way
[23:04] <huwshimi> ok :)
[23:08] <huwshimi> hatch: Aiming for release tomorrow?
[23:08] <hatch> unless we find some huge blocker :)
[23:08] <hatch> but so far so good
[23:11] <huwshimi> yay!
[23:13] <huwshimi> hatch: This is the problem with doing so much between releases :)
[23:14] <hatch> yeah yeah
[23:15] <huwshimi> hehe
[23:21] <huwshimi> Just changing locations, back in a minute.
[23:47] <hatch> huwshimi I'm going to take off for a couple hours - but I'll be back later if you run into any issues with the js portion of the local charm inspectors
[23:47] <huwshimi> hatch: Yep, np