[00:18] <gary_poster> hey huwshimi, another thing to put after icons but before SASS is to style the settings page, if you could.  The ghost styles are perfect, and the same code is producing the html for post-deployed settings, so I suspect there's something fairly simple to do to get it working there.  It might be a re-fix for you--ISTR you might have already done this. If so, sorry about us missing that :-(
[00:18]  * gary_poster runs away into the night
[00:20] <huwshimi> gary_poster: I'll take a look, I haven't touched this at all.
[01:42] <hatch> huwshimi: just to elaborate on the settings stuff a bit - there is also a IE10 bug ticket about the settings layout issue
[01:43] <hatch> so if you are going to tackle that might as well keep that in mind
[01:57] <huwshimi> hatch: OK thank
[01:57] <huwshimi> s
[12:33] <teknico> gary_poster: one on one now, right?
[12:33] <gary_poster> teknico, yes, almost
[12:43] <bac> rick_h: have you ever seen the charmworld test suite get wedged where things ran very slowly and known good tests started failing with elasticsearch errors like (paraphrasing) ShardNotAvailableError?  i rebooted, blew away the fake HOME directory and all tests pass now.
[12:44]  * frankban lunches
[12:54] <gary_poster> benji, will be late.  I have extra time at end so we will have time :-)
[12:55] <benji> gary_poster: that
[12:55] <benji> 's fine
[12:55] <gary_poster> lol
[12:55] <gary_poster> ok thanks
[12:55] <benji> the enter key and ' key are closer together this morning
[13:20] <rick_h> bac: yes, I've seen that. I didn't have ES running
[13:20] <rick_h> ends up I had to update the ppa and install it
[13:21] <rick_h> I *thuoght* I had ES, but figured maybe I'd missed an upgrade or something after doing what you did.
[13:22] <bac> rick_h: thx
[13:29] <sinzui> abentley, bac: do either of your have time to review https://code.launchpad.net/~sinzui/charms/precise/juju-gui/nagios/+merge/177588
[13:30] <bac> sinzui: i will in a bit
[13:32] <sinzui> Excellent news. A train has derailed and if I smell ammonia I am too turn off the air conditioners
[13:34] <jcsackett> sinzui: eeee.
[13:35] <hatch> yesterday wasps, today ammonia....might be time to move if  the danger level keeps increasing at this rate
[13:35] <hatch> :)
[13:37] <teknico> on a positive (?) note, the ammonia might kill the wasps
[13:37] <hatch> and flys
[13:50] <jcsackett> ...what keeps setting me as away...
[13:50] <jcsackett> hatch: danger follows sinzui whereever he goes.
[13:51] <hatch> lol
[13:51] <sinzui> We've kept the shootings to a minimum since I had children
[13:52]  * jcsackett laughs
[13:54] <sinzui> Little does jcsackett know that I was held under suspicion of attempted murder
[13:54] <jcsackett> eh, i've always suspected.
[13:55] <jcsackett> you're a suspicious character, sinzui. :-)
[13:55] <jcsackett> no one with that many tie-tacks could be an innocent.
[13:56] <sinzui> Little do people realise that I am a geek in disguise. Paving the way for all geeks to look good and get dates
[13:56] <hatch> all geeks can get dates it just takes us longer....like 10 years
[13:56] <hatch> lol
[13:57] <sinzui> See, I beat that by 5 years
[13:57] <sinzui> or maybe 9
[13:57] <hatch> haha
[13:58] <sinzui> or 1 
[13:58] <jcastro> rick_h: click-results thing fix today? 
[13:58] <sinzui> I cannot think which what this works
[13:58] <rick_h> jcastro: coming, waiting on one other branch to get through. Last I heard an update was planned to get out this afternoon under an updated release
[13:59]  * jcastro nods
[13:59] <jcastro> thanks man
[13:59] <rick_h> bac: is comingsoon all fixed up? 
[13:59] <jcastro> that's really my only "kicks me in the face" bug. 
[13:59] <rick_h> jcastro: yea :/
[13:59] <jcastro> rick_h: after this I promise to not bother you for at least another 24 hours. heh.
[13:59] <bac> rick_h: it was yesterday
[13:59] <rick_h> jcastro: :P yea you can see it fixed on comingsoon
[13:59] <rick_h> bac: cool, I missed what was up with that. 
[14:00] <jcastro> rick_h: oh indeed.
[14:00] <bac> rick_h: upgrade to d3 caused 'make build-prod' to fail.  cleaned out the old and it was happy again
[14:00] <rick_h> bac: ah, good stuff. 
[14:00] <jcastro> rick_h: generally speaking if I see something fixed on comingsoon it hits prod __X__ days after? What's X usually?
[14:01] <rick_h> jcastro: hmm, only recently had this going and so far it's 4-6 days?
[14:01] <jcastro> ok
[14:01] <rick_h> jcastro: so working that out I think. 
[14:11] <hatch> jujugui looking for two reviews and a qa https://codereview.appspot.com/12205043/
[14:42] <hatch> gary_poster: what do we do with the Needs Reboot and Security Upgrades Available? Should there be a link to landscape?
[14:42] <hatch> hey luca how was your time off?
[14:43] <gary_poster> hatch, yes.  luca could we have inspector icons for that, btw?
[14:43] <gary_poster> hatch open in new window
[14:43] <gary_poster> hatchj oh no
[14:43] <gary_poster> don't open in new window :-P
[14:43] <luca> hatch: gary_poster hey guys, It was good thanks :)
[14:43] <hatch> gary_poster: no? Won't they have to log in separately anyways?
[14:45] <gary_poster> y, though they can stay logged in on gui and landscape.  last time we said it would be in same window.  don't remember why, but was just sticking with past decision.  obv I still kinda agree with you :-)
[14:45] <gary_poster> hatch, luca, if you want to make a different decision together +1 :-)
[14:46] <luca> gary_poster: hatch they link to landscape but I was going to email you a request to make them open in a new window
[14:46] <gary_poster> yay :-)
[14:46] <hatch> excellent
[14:46] <gary_poster> I wish I remember the argument to have it in the same window
[14:46] <gary_poster> just so we would know
[14:46] <hatch> so a single button 'go to landscape' or some icon of some sort
[14:47] <gary_poster> but...yeah.  prefer new window
[14:47] <hatch> gary_poster: I 'think' it had something to do with the session storage
[14:47] <hatch> being window specific
[14:47] <gary_poster> hatch, ah right
[14:47] <gary_poster> so if you go from LS back to GUI
[14:47] <gary_poster> then you have to log in again
[14:47] <gary_poster> let's try this instead :-P
[14:48] <hatch> yep new winder is is
[14:49] <gary_poster> cool
[14:50] <jcastro> rick_h: I was pointing out mysql as one that works
[14:50] <rick_h> jcastro: ah, read it as another example of fail. 
[14:50] <rick_h> jcastro: cool, so yea, simple file extension issue
[14:57] <gary_poster> hatch, please ask me about css name changes on noon call.  rick_h has to do with deployment, you might care too.
[14:58] <gary_poster> hatch sorry I mean on weekly call (@ my noon ;-) )
[15:01] <rick_h> has to do with deployment? ok
[15:19] <luca> gary_poster: I think I remember a conversation on changing Hooks to Source but is there any document for it
[15:20] <rick_h> luca: I thought gary_poster did that at the sprints
[15:20] <rick_h> luca: yea, the tab is already called Source and the description/info at the top of that tab updated
[15:20] <gary_poster> luca there was a bug about it filed by Nick Veitch.  I decided that it was nicer to rename the tab to "Source" rather than remove all files that were no a hook
[15:20] <gary_poster> so addressed the bug in that way
[15:21] <luca> gary_poster: that's right, I remember seeing the bug. We can discuss it next week :)
[15:21] <gary_poster> luca, cool, thanks, look forward to it.
[15:23] <benji> gary_poster: I swear.... The juju-gui-charmers charm trunk appears broken.
[15:23] <benji>         agent-state: error
[15:23] <benji>         agent-state-info: 'hook failed: "start"'
[15:23] <benji> I'll diagnose but this will likely cause a delay in landing my branch.
[15:23] <gary_poster> benji :-( :-(
[15:23] <gary_poster> benji please give me more details when you have them.  pyjuju or juju core?
[15:24] <benji> gary_poster: juju-core; I'll keep you apprised.
[15:24] <gary_poster> thanks
[15:27] <hatch> gary_poster: created a card in the second row of inspector for the viewlet docs
[15:27] <gary_poster> benji, seesm like the change would be in juju core if so.  we haven't changed lately
[15:27] <gary_poster> thanks hatch
[15:27] <gary_poster> benji, I mean, in a way that should affect that
[15:38] <hatch> our webserver is based on tornado right?
[15:39] <rick_h> hatch: rgr
[15:39] <hatch> thx
[15:44] <benji> gary_poster: we did this to ourselves: http://paste.ubuntu.com/5936817/
[15:48] <gary_poster> benji...yes but if so... :-( been that way a looong time and nobody told us
[15:48] <benji> that's because they can't start the gui to click on the feedback tab
[15:48] <gary_poster> benji and it was definitely working relatively recently
[15:49] <gary_poster> 2013-07-18
[15:49] <benji> we just made this change yesterday I think; I reviewed the branch that removed the charm world URL config setting (I didn't think it would have this side-effect of course)
[15:49] <gary_poster> benji did you deploy with any special options
[15:50] <benji> juju bootstrap --upload-tools && juju deploy --repository ~/juju-charms local:juju-gui -u
[15:50] <gary_poster> benji this change would not cause that key error: http://bazaar.launchpad.net/~juju-gui-charmers/charms/precise/juju-gui/trunk/revision/69
[15:51] <hatch> rick_h: have a second for another hbs q?
[15:51] <gary_poster> of course the fact that this happened yesterday makes me sad.  I though we had done that a long time ago--was sure of it in fact, because we had used this for jujucharms.com
[15:51] <rick_h> hatch: sure
[15:51] <benji> gary_poster: I think this was a change in the gui, not the charm; this is just an initial reaction at this point though, I'm trying to confirm
[15:52] <hatch> rick_h: thx ok here is what I'm trying to do https://gist.github.com/hatched/7bbbc76b881fa20d7b92 which obviously is not supported
[15:52] <gary_poster> benji, but we haven't made a release since 0.8.1
[15:52] <benji> that's a good point; I wonder why this is happening
[15:52] <hatch> rick_h: basically i need it to parse an array to see what buttons are to be shown, and if it's in that array then show it
[15:54] <bac> sinzui: branch for review when you have a moment.  https://code.launchpad.net/~bac/charmworld/bundle-search/+merge/178107
[15:54] <rick_h> hatch: so you have to build it in the View layer before you pass it to the template. See  _buildQAData in the subapp browser charm.js view
[15:54] <gary_poster> benji fwiw I'm trying to dupe with pyJuju now
[15:54] <bac> abentley: would like for you to look at it too.  ^^
[15:54] <rick_h> hatch: it sucks, but it's the best way to do it and that way you can test it as well. 
[15:54] <benji> k
[15:54] <hatch> rick_h: ahh - yeah that's exactly what I was trying to avoid :)
[15:55] <hatch> thanks for sanity checking
[15:55] <rick_h> hatch: yea, try as you might. I've had to break down and do it in several places. 
[15:55] <Makyo> jujugui call in 5 kanbaaaaaan
[15:55] <gary_poster> hatch I am in guichat if you want to talk early about css thing
[15:55] <gary_poster> Makyo, thanks :-)
[15:57] <sinzui> bac: I wont be able to get to it today
[15:57] <bac> sinzui: ok
[15:58] <gary_poster> jujugui weekly call in 2
[15:58] <gary_poster> orangesquad weekly call in 2
[16:11] <hatch> luca: in the unit lists in the new inspector the resolve/retry/replace section....
[16:11] <hatch> not all sections need all buttons
[16:11] <hatch> should they be left or center justified?
[16:11] <hatch> aligned*
[16:11] <luca> hatch: centered please :)
[16:11] <hatch> sounds good....and for the landscape statuses
[16:12] <hatch> what do you want the 'go to landscape' button to say?
[16:12] <hatch> or look like....
[16:56] <bac> gary_poster: after lunch i'd like just a few minutes to nail down exactly what you want for IoM bundle deploy demo.
[16:57] <gary_poster> ack thanks bac
[17:09]  * benji lunches.
[17:15] <gary_poster> hatch, rick_h wanna talk now, in 15 min, or 1 hr? :-)
[17:17] <hatch> I'm good whenever
[17:18] <rick_h> gary_poster: just cooking up lunch, 1hr?
[17:18] <rick_h> or you guys can watch me eat on google-cam :)
[17:19] <hatch> what are you having?
[17:19] <rick_h> skillet meal 
[17:20] <hatch> yeah I have no idea what that is
[17:20] <rick_h> lol, frozen meal in a bag you stick on the stove for 10min and then eat
[17:20] <hatch> ohh haha
[17:21] <hatch> I'll probably have a sandwitch
[17:21] <hatch> although a grilled sandwitch also sounds good
[17:21] <gary_poster> hatch, rick_h cool thanks :-) talk to you in 1 hr
[17:24] <rick_h> hatch: had grilled cheese/ham earlier in the week :P
[17:24] <Makyo> "This version of SublimeText 2 has expired"?   Boo >:/
[17:25] <rick_h> :P vim never expires
[17:25] <Makyo> rick_h, +1000
[17:47] <hatch> Makyo: expired?
[17:47] <hatch> using a demo?
[17:47] <Makyo> hatch https://twitter.com/bzr_pull_makyo/status/362988795529940992/photo/1
[17:48] <Makyo> hatch, their demos don't expire, per their website.  I think it's just "please please use the most recent"
[17:48] <hatch> ohhh right
[17:50] <hatch> vim needs a paid version
[17:50] <rick_h> they do, it's called vim. Just pay to their selected charity
[17:51] <hatch> I mean so that they can develop the product to make it more user friendly :)
[17:51] <rick_h> there are two sets of tools in the world. consumer grade and pro grade. Consumers can't easily use pro grade. (camera, sound equipment, ... editors) :P
[17:52] <hatch> things aren't "discoverable"
[17:52] <Makyo> gVim is prosumer
[17:52] <hatch> and editing the config is....well.....heh
[17:52] <Makyo> Sigh.
[17:54] <hatch> I thought I found somewhere that had a config manager
[17:54] <hatch> for vim
[17:56] <Makyo> There's a few.
[17:58] <Makyo> There's https://github.com/spf13/spf13-vim which sits on top of a manager thing, I think.
[17:58] <Makyo> That had too many features for me, though.
[17:58] <Makyo> I couldn't see the code for all of the extra STUFF in there.
[18:00] <hatch> haha
[18:01] <Makyo> I just use stock vim, my vimrc, and ctrlp.
[18:01] <rick_h> jujugui review time please. ﻿﻿https://codereview.appspot.com/12272043
[18:01] <rick_h> and hatch sorry, I forgot I said I'd do your review. Looking for it now
[18:01] <hatch> yeah...that's right!
[18:02] <rick_h> hatch: linky?
[18:02] <hatch> https://codereview.appspot.com/12205043/
[18:02] <hatch> Makyo: the time to setup the vimrc I think is what ultimately drove me away from it
[18:02] <rick_h> hatch: booo, that's back to back "error old chunk mismatch" 
[18:02] <hatch> seriously??
[18:02] <hatch> ugh
[18:02] <rick_h> hatch: next sprint, we'll take care of you
[18:03] <hatch> I'll repropose
[18:03] <rick_h> hatch: I'm on 3rd generation of my vimrc setup
[18:03] <Makyo> hatch, I've not had a single one of your reviews work, tbh, been going off MPs.
[18:03] <rick_h> hatch: k, thanks
[18:03] <Makyo> hatch, but yeah, vimrc is something you can build off others; I think both rick_h and I have good ones you could maybe crib from.
[18:03] <rick_h> yea, but don't ever copy anything you don't understand wtf it is. That lead from gen 1 to gen 2
[18:04] <hatch> haha
[18:04] <rick_h> "my vim's not working, wtf...it must be one of these 200+ lines of crap I copied from some dude"
[18:04]  * rick_h deletes all
[18:06] <hatch> rick_h: Makyo missmatch fixed
[18:07] <rick_h> hatch: thanks, looking now
[18:07] <hatch> tons of results about the chunk missmatch error, must be a reitveld error
[18:07] <hatch> rietveld
[18:07] <hatch> whatever
[18:09] <hatch> I was actually considering webstorm ide
[18:09] <hatch> has some really cool api docs parsing stuff
[18:09] <hatch> rick_h: btw I'm reviewing your branch, will also qa
[18:10] <rick_h> hatch: ty
[18:10] <hatch> lol nice test file diff
[18:10] <rick_h> yea, warning in the description
[18:10] <rick_h> had hoped reitveld would just show the indentation change, but nope :(
[18:11] <hatch> I bet the bzr diff shows it as all new
[18:11] <rick_h> yea
[18:11] <rick_h> bzr hates indentation changes
[18:13] <jcsackett> rick_h: looking at your MP now.
[18:13] <rick_h> jcsackett: ty
[18:16] <jcsackett> rick_h: making sure i understand, the important bits of the test changes are the setup/teardowns for the display tree suite?
[18:17] <rick_h> jcsackett: correct, the browser dom create method is shared among all suites in the new closure. The setup/teardown is adjusted to take care of things that showView auto did before. 
[18:18] <hatch> Chrome has an update....50 tabs open....not updating :P
[18:18] <rick_h> hatch: no tests?
[18:18] <hatch> rick_h: where we are going....we don't neeeeed tests
[18:19] <hatch> but really though there is a card to write the ghost tests
[18:19] <hatch> it's still a little to much in flux imho
[18:19] <rick_h> hatch: up for a chat on the branch then. I'm missing some changes and really ugh about a no-test branch that goes into modifying form elements/config data
[18:21] <hatch> sure
[18:21] <hatch> your branch also failed qa....dun dun dunnnnn
[18:21] <rick_h> gary_poster: we up to chat ?
[18:21] <rick_h> hatch: doh! I qa'd. Curious what was found. Did you hit a back button again? /me always forgets to test that part
[18:22] <hatch> just getting repro
[18:23] <hatch> rick_h: ok updated the review
[18:23] <rick_h> hatch: rgr, thanks
[18:24] <hatch> guichat about my branch?
[18:24] <rick_h> sure thing
[18:26] <gary_poster> hatch, rick_h 
[18:26] <gary_poster> yeah, guichat
[18:26] <rick_h> gary_poster: rgr
[18:27]  * Makyo has to go take the dogs to dogcamp.  Back in a little bit.
[18:42] <gary_poster> Makyo, bac either of you ready/able to talk?
[18:43] <bac> gary_poster: i am
[18:43] <gary_poster> bac cool.  guichat is busy let me make a hangout
[18:52] <gary_poster> Makyo, you're the only one left.  :-) I saw you are out; np.  ping on your return.
[18:52] <gary_poster> benji, what's the status?
[18:53] <rick_h> gary_poster: guichat empty
[18:53] <benji> gary_poster: I've been successful in deploying the juju-gui-charmers trunk against pyJuju, but goJuju gives me the same error; I'm going to chalk it up to my goJuju being broken somehow and am moving forward QAing against pyJuju.
[18:54] <gary_poster> rick_h, :-) thanks
[18:54] <gary_poster> benji, super weird since that looks like such a bltant python error.  but glad you can move forward
[19:10] <Makyo> gary_poster, back.
[19:11] <hatch> benji: kind of like your termbeamer but for sublime, vim and emacs https://floobits.com/
[19:11] <benji> I saw that the other day.  It looks really cool.
[19:12] <hatch> also found http://codeshare.io
[19:13] <rick_h> benji: mentioned termbeamer 3 times at PyOhio
[19:13] <rick_h> I should have done an open space demo'ing it. 
[19:13] <rick_h> benji: one question came up I wasn't sure about, can you use it with your own jabber server? (mozilla folk wanted to know)
[19:13] <benji> did it appear and offer to help you get back to the land of the living?
[19:14] <benji> yep, it only needs xmpp, it doesn't do anything google-specific (AFAIK)
[19:14] <rick_h> benji: cool, told them I thought so but only used it with my google account
[19:15] <benji> and there's a new option to use a purpose-built server; one runs on termbeamer.com or they can run their own
[19:15] <rick_h> yea, had mentioned you were working on that. You need a blog post we can reshare around the inter-webs :)
[19:16] <hatch> http://finalterm.org/
[19:19] <benji> finalterm looks cool, especially the context-sensitive menus; I haven't given it a try yet though
[19:19] <hatch> so many things to try out, who has the time
[19:19] <hatch> this is why I have so many tabs open
[19:20] <hatch> because I also have 100s of bookmarks so things just get lost haha
[19:20] <hatch> one of these days I'll put them into evernote or something
[19:21] <Makyo> There are probably better solutions for bookmarking.  Just a guess, though ^^
[19:21] <Makyo> Er, hatch ^^^
[19:22] <rick_h> *cough* bmark.us *cough*
[19:22] <Makyo> Was gonna say :)
[19:22] <abentley> sinzui: chat?
[19:23] <hatch> haha
[19:23] <sinzui> abentley, in 2 minutes?
[19:23] <abentley> sinzui: okay
[19:23] <hatch> I have a lot of stuff in evernote
[19:24] <hatch> but I know the featureset rick_h has in bmark is pretty darn close :)
[19:24] <hatch> even if it is in python :P
[19:24] <rick_h> hey, I updated YUI for you :P
[19:24] <hatch> haha I saw that
[19:24] <rick_h> it's nearly 50% JS 
[19:24] <hatch> is there a bmark.ca?
[19:24] <hatch> :P
[19:24] <rick_h> no, but you can deploy your own
[19:25] <hatch> should modernize the styles of it, put it on bmark.io or something and then charge /yr :P
[19:27] <hatch> use bootstrap 3 even!!!
[19:27] <hatch> lol
[19:27] <rick_h> nevar! die bootstrap
[19:27] <rick_h> I should update to pure though. Using older responsive YUI grids
[19:28] <hatch> can't....stop....sneezing
[19:29] <hatch> man I wish I could open up the rietveld comments in my code
[19:29] <hatch> unlikely they have an api though
[19:29] <rick_h> very simple api https://code.google.com/p/rietveld/wiki/APIs
[19:30] <rick_h> would have to fetch the issue metadata, with messages, and then parse those out I think. 
[19:30] <hatch> ehh too much work
[20:01] <gary_poster> benji, please keep me up to date on charm progress.  I should be stopping now but I need to make sure we have a release in progress
[20:02] <benji> gary_poster: I am doing what I hope is the last test now... we'll see.
[20:02] <gary_poster> cool
[20:02] <gary_poster> thanks
[20:07] <jcastro> gary_poster: I have no problem making the README file a documentation thing, I just need to know which ones are valid?
[20:07] <jcastro> README, README.md and ... ?
[20:09] <bac> abentley, benji: i have changed my plans to work tomorrow so i'll be around to help with the demo
[20:09] <abentley> bac: Cool.
[20:09] <bac> abentley: changes per review have been made.  diff is updating now
[20:10] <jcastro> hey sinzui 
[20:10] <abentley> sinzui: I haven't figured out how to make juju-deployer export an environment.
[20:10] <sinzui> hi jcastro
[20:11] <jcastro> sinzui: is there a way we can generate a list of charms in the store that have READMEs that either are .rst or .markdown?
[20:11] <jcastro> I can go through and fix em all up
[20:11]  * sinzui thinks
[20:12] <sinzui> jcastro, I can run a query on staging to do that. I can do that tomorrow.
[20:12] <jcastro> rock and roll
[20:12] <jcastro> sinzui: hey so, actually
[20:12] <jcastro> remember how we wanted to do a charm audit anyway?
[20:12] <sinzui> jcastro, I think you mean all charms owned by charmers
[20:12] <jcastro> maybe start seeding the queue with stuff like that?
[20:13]  * sinzui copies scrollback to keep the task
[20:13] <jcastro> yeah so now that we're not smoked from OSCON maybe we should chat like tomorrow about how to seed the queue with audit tasks, etc?
[20:14] <sinzui> abentley, :(
[20:15]  * sinzui tries to remember what he did
[20:16] <hatch> bcsaller: kickin around?
[20:16] <bcsaller> hatch: yeah
[20:17] <hatch> return view.createServiceInspector(service, {databinding: {interval: 0}});
[20:17] <hatch> what does the interval effect?
[20:17] <bcsaller> we delay the updateDOM unless interval is 0 so its needed to test sync style
[20:18] <bcsaller> otherwise updateDOM will fire only after some period w/o calling, 150ms I think
[20:18] <sinzui> abentley, jitsu export > staging.jc.com.deployer
[20:18] <sinzui> abentley, https://pastebin.canonical.com/95362/
[20:18] <hatch> ahh ok thanks
[20:19] <abentley> sinzui: thanks.
[20:19] <sinzui> abentley, so I think there might be version issues between what I did lat May and today's deployer
[20:26] <bac> abentley: what does a deployer file branch look like?  does it just have a single .yaml or .cfg file in it?  special naming?
[20:34] <gary_poster> thanks jcastro.
[20:35] <abentley> bac: Yes, it's a single file named "bundles.yaml".
[20:35] <bac> thanks abentley
[20:39] <abentley> sinzui: Yes, there has been skew.  In current configs, there is an outer dict of bundles, and services is a dict, not a list.
[20:39] <sinzui> yeah, services is what looked wrong
[20:42] <abentley> sinzui: Also, relations looks wrong.
[20:45] <abentley> bac: Have you run "make lint"?  Some of the indentation looks like it would be rejected.
[20:49] <abentley> bac: r=me aside from that.
[20:51] <hatch> rick_h: do you happen to still be around?
[20:51] <rick_h> hatch: kinda, booking a flight for the wife but EOD. I know your branch needs a look. I'll try to peek here in the next 20ish
[20:52] <hatch> thanks, it's proposing now
[20:52] <hatch> issues are fixed and I added ghost-inspector tests and the outline of what is to be followed once this lands
[20:52] <BradCrittenden> thanks abentley for the re-review.  it is lintfree.
[20:52] <hatch> I also moved the ghost inspector test card onto the board under me
[20:52] <hatch> so I'll be on it right after this lands
[20:52] <benji> gary_poster: QA looks good; I'm doing a gui upgrade (from 0.8.0 or 0.8.1) now to QA my change specificially, but I think we'll be in the clear
[20:53] <gary_poster> great thanks benji!
[20:55] <hatch> rick_h: updated
[20:55] <hatch> gary_poster: this will be 0.8.2 right?
[20:56] <gary_poster> hatch, I guess so, yeah
[20:56] <hatch> save 0.9 for the inspector :)
[20:56] <hatch> OR should 0.10 be the inspector
[20:56] <gary_poster> :-)
[20:56] <hatch> oooOOo
[20:56] <gary_poster> lol
[20:56] <hatch> it's so much work that we jumped 2 spots
[20:57] <gary_poster> heh
[20:57] <gary_poster> I'm trying out lp:~gary/juju-gui/hackreleasefiles now
[20:59] <benji> gary_poster: QA looks good (no style or sprite issues)
[21:00] <benji> I'll do the merge in the morning (deployments near EOD being a bad idea)
[21:01] <hatch> are Friday morning deployments better than Thursday night?
[21:01] <hatch> debate! :P
[21:02] <benji> Yes.  Debate over.
[21:02] <benji> Tuesday morning deployments being the holy grail.  After all, who wants to create problems on a Monday.
[21:04] <hatch> true true
[21:06] <bac> sinzui: do you have a deployer file for deploying jujucharms?  i hear you do.
[21:06] <sinzui> bac. I do.
[21:07] <bac> sinzui: would it be compelling for an IoM demo?  if so, can you share it with me?
[21:07] <sinzui> bac, the file is from IS and I think it is the old format though
[21:07] <bac> sinzui: ok.  wiki.yaml from the deployer configs looks serviceable
[21:10] <gary_poster> benji, ok thank you.  
[21:17] <gary_poster> it appears building a branch now requires that g++ be available
[21:18] <gary_poster> so the charm is broekn for that use case atm afaict
[21:22] <rick_h> hatch: I've got to head to swim class in a minute. I don't have time to go back over the branch, sorry. Please rope someone else in to help get it in for huw
[21:22] <gary_poster> hey hatch, seen this node error before
[21:22] <gary_poster> http://pastebin.ubuntu.com/5937801/
[21:22] <rick_h> as temping as code review on the lake beach might seem
[21:22] <hatch> rick_h: haha ok
[21:22] <hatch> gary_poster:  looking
[21:23] <hatch> gary_poster: what version of node are you running?
[21:23] <gary_poster> hatch this is on the charm.  0.8.23
[21:23] <hatch> ok one sec lemme check out node-sass
[21:23] <gary_poster> hatch fwiw that came from bin/generateTemplates
[21:24] <hatch> engines: { node: '>=0.10.0' },
[21:24] <gary_poster> hatch, ah :-(
[21:24] <gary_poster> hatch I have that on raring but in charm...
[21:25] <gary_poster> looking at PPA...
[21:25] <gary_poster> yup https://launchpad.net/~juju-gui-charmers/+archive/stable
[21:25] <gary_poster>  	0.8.23-1chl1~precise1 
[21:26] <hatch> we should really try to upgrade node again
[21:26] <hatch> do we have time?
[21:26] <gary_poster> pfft, not before Friday morning :-P
[21:27] <hatch> what's odd is that I run the most recent 'stable' node on my desktop/laptop and can deploy just fine
[21:27] <hatch> s/deploy/buil
[21:27] <hatch> d
[21:27] <hatch> maybe the error we ran into has been resolved
[21:27] <hatch> of course the easiest thing to do would be to comment out node-sass
[21:27] <hatch> :)
[21:28] <gary_poster> hatch, that's what I was thinking. :-/ are we using it for anything?
[21:29] <hatch> looking
[21:29] <hatch> nope
[21:29] <hatch> it was a setup branch for the following sass changes
[21:29] <gary_poster> right
[21:30] <hatch> so in lib/templates.js you can comment out the require('node-sass')
[21:30] <gary_poster> hatch, could you tell me the least invasive way to disable it?  I need to go help with dinner and will investigate afterwards
[21:30] <gary_poster> oh
[21:30] <gary_poster> :-) thanks
[21:30] <hatch> and one more
[21:30] <hatch> remove the node-sass line from the package.json
[21:30] <hatch> then you'll need to remove the shrinkrap file and regenerate it
[21:31] <hatch> which is simply `npm shrinkwrap`
[21:33] <gary_poster> hatch shrinkwrap not available in my local npm :-/
[21:33] <gary_poster> must run will be back iab
[21:40] <hatch> jujugui anyone around able to do areview https://codereview.appspot.com/12205043/
[21:41] <bcsaller> sure
[21:41] <hatch> thanks
[21:41] <hatch> bcsaller: the tests are coming up right after this lands, card is already in active coding :) just FYI
[21:57] <Makyo> Heading down to the hotel, back to work after check-in.
[22:13] <hatch> bcsaller: lol "scary scoping, and it get worse."
[22:24] <huwshimi> Morning
[22:26] <hatch> morning huwshimi
[22:26] <gary_poster> morning
[22:29] <gary_poster> huwshimi, hatch, bcsaller, call in 1 in guichat
[23:15] <hatch> huwshimi: I'll probably be hangin around cleaning up some stuff and reading blogs so ping me if ya run into any issues
[23:15] <huwshimi> hatch: Thanks.
[23:21] <hatch> oh huwshimi also if you're working on the inspector be sure to pull in trunk as I did a bunch of css stuff today
[23:40] <hatch> must.....close....chrome....tabs
[23:57]  * gary_poster restarts hoping that chrome will be ok again...
[23:57] <gary_poster> back soon