[00:32] <arosales> anyone know of a quick way to show all the recomended charm store charms @ jujucharms.com?
[00:33] <rick_h_> arosales: search for 'charms' and open up the top list
[00:33] <rick_h_> it'll take a while to load
[00:33] <rick_h_> but the top section should be all recommended and the bottom is the rest
[00:33] <arosales> rick_h_: ack thanks
[00:33] <arosales> rick_h_: is that new with the "bundle" search capability?
[00:33] <rick_h_> arosales: yep
[00:34] <arosales> very cool
[00:34] <rick_h_> two keywords charm, charms, or bundle, bundles
[00:34] <rick_h_> but it's so slow we're not screaming from the root tops
[00:34] <rick_h_> more for you guys to show/demo/look at vs a real user feature :/
[00:35] <arosales> understood, I get a lot of requests from folks to where can I look at the current list of recommeded charms.
[00:35] <arosales> I want to send them to the gui over manage
[00:35] <rick_h_> arosales: yep, understand
[00:35] <arosales> rick_h_: thanks
[00:35] <arosales> keep rocking it gui team
[11:19] <rick_h_> frankban: looks to be going better this time. Thanks for the lik to upgrade npm
[11:19] <rick_h_> and morning
[11:20] <frankban> rick_h_: morning, cool
[11:21] <frankban> rick_h_: npm management is a bit disappointing
[11:21] <rick_h_> yea, not a huge fan myself
[11:21] <rick_h_> better than none I guess. 
[11:21] <frankban> rick_h_: I suspect this breaks our charm as well (e.g. juju-gui-source=develop)
[11:22] <frankban> rick_h_: so, an idea could be to "npm set ca "" in the make file
[11:22] <rick_h_> hmm, where do we get nodjs from in the charm? 
[11:22] <rick_h_> I've just updated the nodejs from the ppa
[11:22] <rick_h_> if it's using the ppa it should be fine on next update/deploy
[11:23] <frankban> rick_h_: trying
[11:25]  * rick_h_ goes to get ready for the day and the boy off to day care now that landing is unblocked
[11:27] <frankban> rick_h_: thanks for updating CI
[12:21] <rick_h_> frankban: the charm test go ok?
[12:24] <frankban> rick_h_: no, we take deps from ppa:juju-gui-charmers/stable, we need to update the ppa. created a critical card
[12:25] <frankban> rick_h_: the charm installs both nodejs and npm: the latter seems to be included in the former now, so a charm update might also be required
[12:26] <frankban> rick_h_: https://launchpad.net/~chris-lea/+archive/node.js/+packages effectively only includes the nodejs package
[12:26] <frankban> rick_h_: if we need to remove npm from the charms deps, then we might want to release a new charm ASAP
[12:26] <frankban> rick_h_: if the above makes sense to you, I'll dig into that ASAP
[12:27] <rick_h_> gotcha, sounds like a plan
[12:28] <rick_h_> yea, npm is both packages now. surprised that hasn't caused us issues before now as apt-get install fails due to that these day
[12:28] <frankban> rick_h_: perhaps the charm installs npm from precise?
[12:29] <rick_h_> frankban: maybe. The hacking docs have been the ppa for a long long time. It'll be good to get it in sync I guess. 
[12:29] <frankban> rick_h_: no, we currently have npm in our ppa
[12:29] <rick_h_> right
[12:29] <rick_h_> gothca
[12:29] <rick_h_> so we've hit this in dev but the charm has been fine using the old stuff
[12:30] <frankban> of course they considered Friday as a good day for a backward incompatible change
[12:30] <rick_h_> hah! can't have a quiet friday
[12:33] <BradCrittenden> frankban: just reading backwards.  so you're seeing the charm ftests failing?
[12:34] <frankban> bac: no, the charm "build from source" fails
[12:34] <bac> frankban: in the charm trunk, i'm seeing the tests fail on lxc and ec2.
[12:37] <frankban> bac: logs?
[12:37] <frankban> bac: it could be related
[12:38] <bac> frankban: http://paste.ubuntu.com/7010106/
[12:38] <bac> frankban: the second error is a problem in tearDown that is masking the real error in that test
[12:39] <bac> if the deploy doesn't work then tearDown fails because self.serviceName is unset.  i'll fix that and re-run to see what the real problem is
[12:42] <bac> frankban: is it true that you cannot run the charm ftests on lxc if your host is not precise?  i was getting errors yesterday that seemed to indicate that when run on my trusty VM.
[12:42] <rick_h_> bac: you'll have to deploy the charm with make deploy and look at the unit log to see why it's in error state
[12:42] <rick_h_> it could be related
[12:43] <rick_h_> bac: but have to double check the unit log to see why it's failing
[12:43] <bac> rick_h_: ok
[12:44] <frankban> bac: since the error is in test_branch_source I strongly suspect you are encountering the same error
[12:48] <frankban> bac: IIRC you cannot run ftests on a local env for two reasons: 1) the tests co-locate the GUI on the bootstrap node (for speed reasons) and this is not possible in local envs, where machine 0 is localhost, and 2) bootstrapping a local env requires sudo
[12:50] <rick_h_> thanks for sending the email frankban 
[12:50] <bac> frankban: yes, i was encountering 1).  couldn't colocate since they were of different series
[12:51] <rick_h_> bac: well lxc can't colocate regardless of series
[12:52] <frankban> bac: as I said, I suspect you would not be able to colocate even if you were on precise. That's because machine 0 in local envs is not a container
[12:52] <bac> frankban: ah, right.  i'll update the HACKING doc to remind folks (future me) of that
[12:52] <frankban> bac: great thank you
[13:24] <bac> marcoceppi: when you have time could you complete the charmworldlib review at  https://codereview.appspot.com/69430043 ?
[13:25] <marcoceppi> bac: thanks, off today so will likely get to it monday -ish
[13:39]  * bac relocates to coworking spot
[13:53] <hatch> frankban I saw your email, does the charm build with the new version of node?
[13:54] <hatch> I've been running the latest node locally without issue....
[13:54] <frankban> hatch: I am trying
[13:54] <hatch> cool
[13:54] <hatch> I thought you may have already so I was just curious :)
[13:54] <frankban> hatch: could you please take a look at https://github.com/juju/juju-gui/pull/149
[13:54] <hatch> on it
[14:00] <frankban> hatch: nodejs update solves the SELF_SIGNED_CERT_IN_CHAIN issue, but there is another error. make log: http://pastebin.ubuntu.com/7010492/   npm log: http://pastebin.ubuntu.com/7010496/
[14:01] <hatch> looking
[14:02] <hatch> frankban do you have g++ installed?
[14:02] <rick_h_> node-gyp requires that the user's home directory is specified in either of the environmental variables HOME or USERPROFILE
[14:02] <rick_h_> didn't we have to add g++ months ago to get things working?
[14:02] <rick_h_> or this is another case where we added the dep for dev but not for prod/charm?
[14:02] <rick_h_> and now we're hitting all kinds of upgrade fun?
[14:03] <hatch> rick_h_ I THINK we only added it locally
[14:03] <frankban> hatch, rick_h_ yeah g++ is in the charm
[14:03] <hatch> ohh
[14:03] <hatch> hmm
[14:03] <hatch> that's what typically causes the contextify issue
[14:03] <rick_h_> frankban: can we try to add a HOME= to the make target and see if it'll build then?
[14:03] <frankban> rick_h_: that's what I was trying to do
[14:04] <hatch> Error: node-gyp requires that the user's home directory is specified in either of the environmental variables HOME or USERPROFILE
[14:04] <rick_h_> ok
[14:04] <frankban> rick_h_: so the HOME will be root's home in the charm context
[14:05] <rick_h_> frankban: yea, :/ and kind of stupid it can't work in tmp or something. 
[14:06] <hatch> ENOENT typically means that the directory doesn't exist or it can't access it
[14:06] <rick_h_> hatch: right, there's no HOME dir and so it can't build in it, or whatever it wants to do there
[14:06] <hatch> blarg
[14:07] <rick_h_> https://github.com/TooTallNate/node-gyp/issues/270
[14:09] <rick_h_> https://github.com/TooTallNate/node-gyp/blob/0cc243e4593bfca8fb5cbbc7413d89b8ba3b1a03/lib/node-gyp.js#L49
[14:10] <rick_h_> so yea, we need to give it a place to extract to. We might be able to fake it out if we had to, but building in /root will have to do as a start
[14:12] <rick_h_> btw, this is why I love OSS. "WTF..." *go load source*
[14:13] <hatch> OSS also has "RTFS MAN"
[14:13] <hatch> :P
[14:15] <hatch> oh man this diff is hard to read, git split it up in a very funky way
[14:15] <rick_h_> hatch: try the whitespace trick?
[14:16] <hatch> https://github.com/juju/juju-gui/pull/149/files#diff-8d19084702f50f400641361a9cb78591L1069
[14:16] <hatch> it picked stuff from within another closure and considered it part of another fn
[14:16] <hatch> which is 'technically' correct
[14:16] <hatch> it's just hard to read
[14:17] <rick_h_> yea, the side by side is a little easier
[14:17] <rick_h_> but not much
[14:19] <frankban> I'll call this "Friday's hot fixes vs charm development" hell :-/
[14:19] <hatch> so hot http://i.kinja-img.com/gawker-media/image/upload/hrlzerlexsbdxj8u0r5h.jpg
[14:20] <hatch> frankban lol
[14:20] <hatch> why do you think we haven't updated node in 6 months :D
[14:20] <frankban> we did not update node, it's node that updated us
[14:21] <hatch> lol
[14:23] <frankban> we were happy with our old good node, they decided to betray our trust, and to make us haters
[14:24] <hatch> there is too much drama in the node world right now
[14:24] <rick_h_> heh, no kidding. You see the npmjs stuff? :P
[14:24] <hatch> ugh what a shitshow
[14:24] <rick_h_> wheeee
[14:24] <rick_h_> community building at its best
[14:24] <hatch> I feel like I'm back in highschool student body elections 
[14:28] <hatch> all I can say is that I'm super glad I didn't "donate" to npm 
[14:28] <rick_h_> yea, i almost did and very glad. I'm be fuming
[14:29] <hatch> I'm still trying to figure out how a product a guy made while working at another company was able to break off into another company
[14:29] <hatch> unless he did it in his own time...
[14:29] <hatch> but I was sure it was done during the normal work
[14:29] <rick_h_> heh, guess who's investing and getting a bit of the company :)
[14:29]  * rick_h_ says in a cynical voice
[14:29] <hatch> lol
[14:30] <hatch> I'm wondering what their revenue plans are
[14:30] <hatch> they are pretty unstable as-is using couchdb
[14:30] <hatch> so not sure if people would want to pay them for local instances
[14:30] <hatch> s/local/private
[14:31] <hatch> I'm just blaming couchdb because that always seems to be their reasoning when something goes down
[14:33] <bac> jujugui: i need a prelimary review of this charmworldlib branch that we're going to include several places as a forked version until it can be landed upstream.  any takers?  https://codereview.appspot.com/69430043
[14:35] <frankban> bac: I'll try to take a look later if nobody else already did, now in the middle of a critical task
[14:35] <bac> frankban: no rush
[14:36] <rick_h_> bac: looking
[14:40] <hatch> jcastro will the app developer week videos be recorded?
[14:44] <jcastro> I am assuming so
[14:44] <jcastro> they're on G+
[14:54] <hatch> jcastro ok cool, I really want to watch but I don't think I can convince rick_h_  to give me that much TO :D
[14:54] <rick_h_> :P
[15:05] <hatch> rick_h_ I've NEVER used middle click in the course of my daily activities :) 
[15:05] <hatch> always ctrl+c/ctrl+shift+c
[15:05] <hatch> the latter being VERY irritating when coming from iterm2
[15:05] <rick_h_> hatch: ugh, neanderthal :P
[15:06] <hatch> haha, I just wish someone would make a good linux terminal like iterm2
[15:06] <rick_h_> oh you've got to be kidding me
[15:06] <rick_h_> urxvt is 10x the terminal iterm2
[15:06] <hatch> do I have to use ctrl+shift+c/p to interact with the terminal?
[15:06] <rick_h_> no, you use middle click and all is well
[15:07] <hatch> there is no middle click on a touch pad :)
[15:07] <rick_h_> which is why I'm so irritated
[15:07] <frankban> hatch: I use ^C ^V and remapped ^C to ^K
[15:07] <rick_h_> no idea what you use keyboard wise to copy/paste in a linux terminal
[15:08] <hatch> interacting with the terminal in Ubuntu always feels like the terminal is a second class citizen 
[15:08] <rick_h_> heh, I feel that way in osc
[15:08] <rick_h_> osx
[15:08] <rick_h_> it doesn't remember the size it was, home/etc is stupiud "fn arrow" crap
[15:08] <rick_h_> urls aren't highlighted and ready to go
[15:09] <hatch> yeah that's osx for ya
[15:09] <hatch> are you using iterm2?
[15:09] <hatch> it's highly customizable and you don't need to do any cryptic commands to change font colours :)
[15:10] <hatch> really though....it should remember all your settings
[15:10] <hatch> mine does
[15:10] <rick_h_> yes, I'm using iterm2
[15:10] <rick_h_> and any terminal that isn't config file configurable sucks...
[15:10] <rick_h_> no, you've got to go into the UI and set x, and y, and then z. Then go over to tab 5 and enter blah blah
[15:11] <rick_h_> instead of git clone github:config_files.git && make install
[15:11] <jcastro> frankban, hey I just noticed, is there no way to make a manual provider with quickstart?
[15:11] <frankban> jcastro: no, maas and manual are not yet supported
[15:12] <frankban> jcastro: of course quickstart does not refuse to start unknown envs if they already exist
[15:12] <hatch> rick_h_ I am pretty sure you can import/export iterm2 profiles
[15:12] <jcastro> ah ok
[15:13] <rick_h_> hatch: yea, I got some colors doing that. 
[15:13] <rick_h_> hatch: not sure how much config it'll support 
[15:14] <hatch> my biggest issue with things like vim/terminal etc is the discoverability of features is 0
[15:14] <hatch> oh you want to show 256 colours? sorry we only show you 16
[15:14] <hatch> :)
[15:15] <rick_h_> hatch: it's why I love my git with my config
[15:15] <rick_h_> solve it once and never worry about it again
[15:16] <hatch> until new features come down and you realize you didn't know about them until a year later :P
[15:16] <rick_h_> :)
[15:31]  * hatch longs for a code-coverage tool for our tests
[15:31]  * hatch sits up late at night sobbing for it's coming
[15:32] <rick_h_> hatch: good sprint idea to hack together 
[15:33] <hatch> tbh the real reason I want it is so that I don't have to keep going through the tests and my refactored code to make sure i hit every branch :)
[15:33] <hatch> it's very time consuming
[15:33] <rick_h_> hah
[15:34] <hatch> http://www.autoblog.com/2014/02/28/lexus-rc-350-f-sport-geneva-photos/
[15:34] <hatch> I think I need a second job
[15:35] <rick_h_> not a fan of that front end
[15:35] <hatch> yeah it's a love it or hate it design
[15:35] <hatch> I'm in the former category
[15:35] <rick_h_> "hey, you guys forgot to finish the bumper"
[15:36] <rick_h_> it's like what would happen if under armor sponsored a car design
[15:36] <rick_h_> "new breathable mesh"
[15:36] <hatch> hahaha
[15:36] <hatch> typically that much air intake on the front of a car is an aerodynamic nightmare 
[15:37] <hatch> I'm curious as to how they solved that
[15:37] <hatch> if they did...
[15:37] <frankban> rick_h_: could you take a quick look at https://codereview.appspot.com/67990044 ?
[15:37] <rick_h_> frankban: loading
[15:37] <frankban> cool thanks
[15:37] <rick_h_> frankban: need a qa? it looks good here. 
[15:38] <frankban> rick_h_: good point. I think a QA might help. make deploy && juju set juju-gui juju-gui-source=develop && check veerything is ok
[15:39] <frankban> everything even
[15:39] <rick_h_> frankban: rgr, will do a ec2 test just to make sure we hit as close to live as possible.
[15:39] <frankban> rick_h_: sounds good thanks
[15:41] <rick_h_> frankban: seen https://pastebin.canonical.com/105721/ ?
[15:42] <frankban> rick_h_: it's a core error. are you using trunk?
[15:42] <rick_h_> frankban: testing something out. Looks like I might have had an old env laying around :/
[15:42] <frankban> rick_h_: if not, do you have a stale jenv file?
[15:43] <frankban> :-/
[15:43] <rick_h_> yea, think I had some jenv around. My bad. Running juju on too many machines and don't realize I leave things in a bad state
[15:44] <hatch> good to see that someone finally fixed that imagemagic issue that we had when upgrading before :)
[15:50] <rick_h_> jujugui call in 10
[15:57] <hatch> jujugui call in 2
[16:05] <jcastro> rick_h_, I have questions for you after your call
[16:05] <jcastro> or if you guys want me in there at the end to make fun of me collectively I can do that
[16:05] <rick_h_> jcastro: after call is cool, be a bit 
[16:06] <jcastro> no worries!
[16:08] <rick_h_> http://mitechie.planningpoker.com/participants/new?token=hm67co 
[16:44] <bac> everyone votes 5 on leaving
[16:45] <rick_h_> jcastro: got time when you want to chat
[16:45] <hatch> bac haha
[16:47] <hatch> I was going to work a bit on my ghost charm this weekend 
[16:47] <hatch> and create a bundle which deploys everything to machine 0
[16:47] <rick_h_> hatch: woot
[16:47] <hatch> but there is a bug which will block that :(
[16:47] <hatch> the gui binds to port 80
[16:47] <hatch> where ghost needs to be
[16:48] <hatch> hazmat filed it a while ago actually https://bugs.launchpad.net/juju-gui/+bug/1256426
[16:48] <_mup_> Bug #1256426: charm, allow binding to just 443 so can colocate with webapp on port 80 <juju-gui:Triaged> <https://launchpad.net/bugs/1256426>
[16:48] <hatch> it would be awesome if we could squish the fix into the schedule somewhere
[16:48] <rick_h_> yea, it'd be good to get that in as a config param
[16:49] <rick_h_> hatch: put a card in the backlog maint pool
[16:49] <rick_h_> and we'll try to get it up for looking at as part of a 2wk cycle
[16:49] <hatch> ok cool can do, could the card be 'supply new http and https ports for the gui' ?
[16:49] <jcastro> rick_h_, https://plus.google.com/hangouts/_/72cpi1ph534ssfjd37rq6d5png?hl=en
[16:49] <hatch> so that the gui could be on any ports (in case the webapp needs https as well)
[16:50] <frankban> hatch: currently the default is 443 and 80 redirects to 443. with secure=false you only have 80
[16:51] <frankban> hatch: so I guess those are two separate tasks 1) an option to only bind to the real port without redirecting 80 (defaulting to false) and 2) and option to set the real port (defaulting to 443)
[16:52] <hatch> ok great thanks I'll update the bug and make appropriate cards 
[16:52] <hatch> it would be super awesome to have a Ghost bundle all on a single machine
[16:52] <frankban> hatch: the only missing bit is what happens when you set secure=false
[16:52] <hatch> juju quickstart ghost-simple
[16:52] <hatch> :)
[16:54] <frankban> rick_h_: is charm deployment going well?
[16:54] <rick_h_> frankban: yes
[16:54] <hatch> frankban right - I'd be happy to say certain config options are invalid when others are set
[16:55] <rick_h_> frankban: looking and testing it out but otp
[16:55] <hatch> if secure=false then you MUST have provided a insecure port
[16:55] <hatch> for example
[16:55] <frankban> sounds reasonable
[16:55] <frankban> rick_h_: cool thanks
[16:59] <rick_h_> frankban: looks good here thanks!
[17:00] <frankban> rick_h_: great
[17:01] <frankban> jujugui: starting the process for a charm release
[17:01] <hatch> :+1:
[17:01]  * hatch wishes his irc client did emoticons
[17:02] <Makyo> Just make it do a train whistle on :+1:
[17:02] <rick_h_> lol
[17:03] <frankban> :-)
[17:03] <rick_h_> perfect
[17:03] <rick_h_> jujugui I'm not getting canonical admin emails right now so if you need approvaly for anything please ping me
[17:03] <Makyo> rick_h_, ping :)
[17:03] <rick_h_> Makyo: lol
[17:07] <hatch> anyone else having issues sending emails?
[17:10] <rick_h_> jcastro: I lied, that is me
[17:11] <jcastro> rick_h_, ok, let Joey know
[17:11] <rick_h_> jcastro: yep, replied
[17:22] <hatch> UGH 
[17:23] <rick_h_> hatch: loves life...
[17:23] <hatch> I am irrationally agitated about the RL-1 not being available in English 
[17:23] <rick_h_> RL-1?
[17:24] <hatch> http://www.revenuquebec.ca/en/sepf/formulaires/rl/rl-1/default.aspx
[18:06]  * Makyo ducks out to laundromat, will be on once there under diff. nick.
[18:11] <rick_h_> yay! new yubikeys arrived. Time to yubikey all the machines!
[18:14] <hatch> yay
[18:14] <rick_h_> can stop swapping them across machines now
[18:33] <frankban> jujugui: cs:precise/juju-gui-85 released and ingested. EOD, have a great weekend!
[18:33] <rick_h_> frankban: thanks so much for that!
[18:33] <rick_h_> have a good weekend
[18:34] <frankban> ty
[19:18] <rick_h_> jujugui if you've got any holiday time in the next two weeks please make sure to submit it so I can setup the number of cards correctly please
[19:18] <hatch> hmmm
[19:29] <hatch> oh so DRAB
[19:29] <hatch> :)
[19:29] <hatch> DrabMakyo I got a funny story for you
[19:29] <hatch> ok it's not funny at all
[19:31] <rick_h_> ruh roh
[19:31] <rick_h_> I must prefer funny stories...especially when they're funny
[19:33] <DrabMakyo> Hah!  Oh yeah?
[19:33] <rick_h_> this one time, at band camp, hatch wrote CS
[19:33] <hatch> there is this reality tv show where they follow customs agents and all the dumb/funny things that happen
[19:33] <DrabMakyo> SHH Don't get him started.
[19:34] <hatch> like people trying to get into the country with warrants and stuff like that
[19:34] <hatch> anyways
[19:34] <hatch> this one guy got pulled aside for whatever reason and they pulled out a fox suit and was like 'wtf?'
[19:34] <hatch> and he said "I'm a furry..."
[19:34] <hatch> I smiled
[19:34] <DrabMakyo> Pff.
[19:34] <DrabMakyo> Nice.
[19:34] <hatch> because I knew what we was talking about lol
[19:34] <rick_h_> umm, ok
[19:35] <rick_h_> hah, come to penguicon, you'll get a lesson or three
[19:35] <DrabMakyo> It's super important, okay? Haha
[19:36] <hatch> I had never heard of it until, what, 3 weeks ago? and now I've seen it on TV
[19:36] <hatch> crazy times
[19:36] <DrabMakyo> It's weird enough to be a media darling, yeah.
[19:36] <rick_h_> lol, you've never heard of it?
[19:36] <hatch> nope never
[19:36] <rick_h_> I'd think in that cold up there you'd all have nice warm furry costumes
[19:36] <DrabMakyo> HAhaha
[19:37] <hatch> rofl
[19:37] <DrabMakyo> hatch is sheltered.
[19:37] <hatch> hey! I'm sure you guys have never heard of a snowmobile poker rally! 
[19:37] <DrabMakyo> You got me there :)
[19:38] <hatch> haha
[19:41] <hatch> jujugui lf a review on https://github.com/juju/juju-gui/pull/150
[19:41]  * hatch is stick of looking at that darn branch
[19:41] <rick_h_> hatch: looking
[19:42] <hatch> thanks
[19:42] <rick_h_> jujugui I've gotten the cards pulled out for the 2 week cycle. Lots of maint hopefully we can burn that down. 
[19:42] <rick_h_> let me know if anything looks off, but basically there's the plan for the next 2 weeks
[19:43] <hatch> rick_h_ heh, it looks like a lot of work for two weeks
[19:43] <hatch> I know it's "accurate" it just looks like a lot :)
[19:43] <rick_h_> 5 devs * 10 days * 2 points per day = 100 points
[19:44] <rick_h_> that's about 79 points on the board
[19:44] <hatch> rick_h_ did you make changes to the CI?
[19:44] <rick_h_> hatch: my bad, I forgot that jujugui was our bot
[19:44] <rick_h_> and removed him from the juju team...oops
[19:45] <rick_h_> added back, sorry
[19:45] <hatch> np, I just noticed a 'Merged build started' and 'Merged build triggered' and got concerned :)
[19:46] <rick_h_> yea
[19:46] <rick_h_> same here
[19:46] <hatch> can he be renamed to jujuguibot?
[19:46] <rick_h_> hatch: I suppose
[19:47] <hatch> whichever :)
[19:47] <rick_h_> 11 files?!
[19:48] <hatch> yeah see why code coverage would have been nice? lol
[19:56] <hatch> responding while the comments come in is pretty cool
[20:07] <hatch> rick_h_ I responded while you were making comments so you will want to go through them again :)
[20:07] <rick_h_> lol, now to go read all the replies that are build up
[20:09] <DrabMakyo> Haha, ouch: http://twitter.com/appcode/status/437896886649757696/photo/1
[20:09] <hatch> hahaha
[20:09] <hatch> well played 
[20:09] <hatch> well played
[20:10] <hatch> very retweet worthy 
[20:12] <hatch> jcastro do you have someone fixing that weird busted sticky header thing on discourse.ubuntu.com? Would you like someone to look into fixing it?
[20:12] <rick_h_> hatch: replies to your replies done
[20:13] <hatch> rick_h_ thanks, I'll get to making the changes
[20:13] <rick_h_> I'll get a QA setup going here
[20:23] <DrabMakyo> rick_h_: now that I see what you mean by the JSON we get from cs, I think it might actually be easiest to just build the URLs from the GUI side.  At that point, we know we're getting charms from teh store because we requested the bundle from the store.
[20:24] <rick_h_> DrabMakyo: right but the json on a bundle details includes the bundle info so we don't have to make 100 calls out to the api
[20:24] <rick_h_> DrabMakyo: so I'm not sure how we can move that logic gui side 
[20:27] <DrabMakyo> It looks like it contains most of the info there... https://gist.github.com/makyo/9279138  Maybe I misunderstand, though.  Let me poke around a bit more.
[20:27] <DrabMakyo> Just need to change these lines: https://gist.github.com/makyo/9279138#file-bundle-json-L1214 etc.
[20:28] <hatch> ugh I gota run to the bank real quick
[20:28] <hatch> I'll be on the cell
[20:29] <DrabMakyo> I'll keep prowling, though.  Definitely want to be sure.  If nothing else, at least we have most of that info already in guiland
[20:29] <rick_h_> DrabMakyo: hangout?
[20:29] <rick_h_> maybe I'm just confused
[20:29] <DrabMakyo> rick_h_: Uh, sure, can step outside.
[20:30] <rick_h_> DrabMakyo: ah, nvm
[20:30] <rick_h_> we can catch up monday
[20:30] <rick_h_> my thoguht is that charmworld can update the charm section for each service when it writes out that json
[20:31] <rick_h_> and then everything should 'just work' and it knows the url since it's building that charm_metadata
[20:31] <DrabMakyo> rick_h_: oh, yeah, that'd work perfectly.
[20:31] <rick_h_> having gui aware that there's some magic there seems the wrong place for the magic
[20:31] <DrabMakyo> Ah, yeah, that makes sense.
[20:31] <DrabMakyo> rick_h_: would that be on outputting the json or on ingest/migration?
[20:32] <DrabMakyo> I had mentioned ingest in the doc, but could do either.
[20:32] <rick_h_> well my thought was to do it on ingestion so the data in the db is clean
[20:32] <DrabMakyo> Okay.
[20:32] <DrabMakyo> +1
[20:32] <rick_h_> vs havnig to remember to clean it any time we output it
[20:32] <DrabMakyo> YEp, sounds good.
[20:33] <DrabMakyo> Laundry's done.  Going to run back home.
[20:33] <DrabMakyo> Back in a few.
[20:52] <rick_h_> jujugui I'm out. Have a good weekend. Thanks for the branch hatch 
[21:13] <hatch> back
[21:13] <hatch> ugh Friday bank and road traffic