[09:12] <jackpeterfletch> Hey guys
[12:21] <rick_h_> Makyo: what's this doc branch that you manually landed with the one line "This branch in particular..."?
[12:22] <rick_h_> Makyo: oic, you merged it into a branch of the juju/juju-gui
[12:36] <Makyo> rick_h_: yeah, sorry about that.  That's our networking prototype branch, sorry you're getting notifications :/  We can maybe move to my fork if need be.
[12:41] <rick_h_> Makyo: that's ok, I just missed the diff branch and it went by the lander so was checking it out
[13:33] <benji> frankban: do you have a second to review a small branch? https://codereview.appspot.com/49030043
[13:34] <frankban> benji: sure
[13:34] <benji> thanks
[13:43] <frankban> benji: the code looks good. what happens if you still pass "fullscreen" to the GUI? is it just ignored? does it fallback to the default (sidebar)? I am worried about existing deployments, like jc.com, and I believe we should update the instructions in https://wiki.canonical.com/InformationInfrastructure/WebOps/CDO/JujuGui
[13:44] <benji> frankban: both good points, I'll investigate the first and write down a TODO for the second
[13:45] <rick_h_> frankban: the config parameter is still part of the config-debug/prod.js. The code in the gui ignores it though and it should be removed
[13:46] <rick_h_> frankban: benji the deployment notes need update and the current deployment needs to have webops request the value get changed first I believe
[13:46] <benji> rick_h_: thanks for the info
[13:48] <frankban> benji: great thanks.
[13:49] <frankban> rick_h_: does it mean that also 'sidebar' and 'minimized' are ignored?
[13:49]  * rick_h_ goes to pull up the code real quick
[13:50] <rick_h_> frankban: so the code in the gui ignores the setting entirely
[13:50] <rick_h_> frankban: but the config is still defined in the config-app/prod files. So yes, all values for that setting are ignored
[13:51] <frankban> benji: ^^^ so if this is the desired behavior maybe we should just remove the option entirely from the charm too
[13:52] <benji> frankban: yeah, I suppose so; the card just specified "fullscreen" but it sounds like (and I will verify) that the configuration paramiter itself should go away.
[13:52] <frankban> benji, rick_h_: cool thank you
[14:30] <benji> man, it's still cold out there; I demand warmer weather
[15:12] <luca_> rick_h_: just heard you have a 4k monitor. You have now been labelled as a man of extremes.
[15:12] <rick_h_> luca_: no sense playing with things half way :)
[15:12] <luca_> rick_h_: rofl
[15:12] <rick_h_> I like my command lines pretty and clear :)
[15:12] <luca_> rick_h_: haha
[15:13] <luca_> rick_h_: how awesome is it?
[15:13] <rick_h_> luca_: quite awesome
[15:14] <rick_h_> luca_: took a little config though http://uploads.mitechie.com/current_status.png
[15:14] <luca_> rick_h_: do you have a powerful enough computer to properly utilise it? by properly utilise it I mean play bf4 or something similar on full spec....
[15:15] <rick_h_> luca_: I've not tried steam on it. I've got an nviidia 660ti which will run it over display port 1.2 at 60hz
[15:15] <luca_> rick_h_: jeez, impressive stuff
[15:15] <rick_h_> luca_: I'd expect to be able to run a game, not at 100+fps
[15:15] <rick_h_> but usable
[15:15] <luca_> rick_h_: yeah
[15:15] <rick_h_> I tried some youtube 4k video samples
[15:15] <rick_h_> pretty stuff
[15:16] <luca_> rick_h_: what size is it?
[15:16] <bac> huh rietveld won't give you the Green Seal of Approval if you self review.  boo.
[15:16] <rick_h_> 24"
[15:16] <luca_> rick_h_: nice
[15:16] <rick_h_> bac: yea
[15:16] <gary_poster> 6 feet x 8 feet
[15:16] <gary_poster> It's a Fahrenheit 451 tv wall
[15:16] <luca_> gary_poster: lol
[15:16] <rick_h_> hah
[15:17] <luca_> gary_poster: you reminded me! Can I get comment permissions on the doc you sent earlier?
[15:17] <rick_h_> If it was 27" it'd be cool I think, but I don't want much more than that
[15:17] <bac> rick_h_: which did you get?
[15:17] <rick_h_> http://www1.la.dell.com/bz/en/corp/peripherals/dell-up2414q/pd.aspx?refid=dell-up2414q&s=corp
[15:17] <gary_poster> luca_: done, for you and ale
[15:18] <luca_> gary_poster: thanks, I'll give it a read through. Is there anything that I should specifically look at?
[15:19] <bac> gary_poster: 2.b.ii. stops in mid
[15:19] <gary_poster> luca_: <shrug> not really.  This is an attempt to guess at a lot of things that have not been spelled out.
[15:19] <gary_poster> luca_: and for the the three new projects, we have specs for you for two and the third won't be explicitly exposed at first
[15:19] <gary_poster> specs from you, I mean
[15:20] <gary_poster> bac, thank you, fixed
[15:21] <luca_> gary_poster: yeah, I see
[15:50] <gary_poster> jujugui call in 10
[15:53] <rick_h_> jujugui does anyone have a "this is awesome" pattern for doing logging in python cli scripts?
[15:53] <hazmat> rick_h_, depends on what your looking for
[15:53] <hazmat> rick_h_, dictConfig makes things pretty simple
[15:54] <rick_h_> hazmat: yea, just feels like repeating the wheel to add a argparse -v and deal with logging config to allow going into verbose and such. 
[15:54] <hazmat> rick_h_, simple to type it up as yaml.load("""\) that's if you want something pretty 
[15:55] <rick_h_> looks like quickstart just using logging.basicConfig with a couple of tweaks
[15:55] <hazmat> rick_h_, fair enough i typically just on verbose set level=logging.DEBUG on basicConfig
[15:55] <rick_h_> hazmat: yea, guess it's not that much to setup the logging and change the level. 
[15:55] <rick_h_> hazmat: thanks
[15:55] <hazmat> and if using dictConfig, just post config grab root logger and set level for verbose
[15:55] <hazmat> cheers
[15:58] <gary_poster> jujugui call in 2
[16:22] <bac> gary_poster: release to production done and heartbeat shows happiness.
[16:23] <gary_poster> bac, yay!  thanks
[16:23] <bac> gary_poster: going to lunch now but will need new task when i return.  let me know if you have something to suggest.
[16:23] <gary_poster> ack
[16:25] <rick_h_> gary_poster: back home on real interwebs
[16:25] <gary_poster> ack
[16:26] <gary_poster> rick_h_: come on by: https://plus.google.com/hangouts/_/calendar/Z2FyeS5wb3N0ZXJAY2Fub25pY2FsLmNvbQ.j0rk5d371ph8331ijtf48t2uj0
[16:38] <benji> frankban: does this charm ftest failure look familiar? http://paste.ubuntu.com/6715682/
[16:40] <gary_poster> hey frankbanready in https://plus.google.com/hangouts/_/calendar/Z2FyeS5wb3N0ZXJAY2Fub25pY2FsLmNvbQ.j0rk5d371ph8331ijtf48t2uj0 whenever. no rush
[16:40] <frankban> benji: that could mean a newer version of firefox does not work well with the selenium version we are using
[16:40] <gary_poster> frankban, I mean
[16:40] <frankban> gary_poster: joining
[16:41] <benji> frankban: I'll run the tests on a clean checkout and see if it reoccurs there
[16:45] <gary_poster> frankban: https://plus.google.com/hangouts/_/72cpi0lc0etbof2h2ahv9kcd18 if that helps
[18:05] <rick_h_> heh, backup is 655MB :/ though ran and uploaded in 8min. Love cloud storage though. That'll be less then $2/mo with one backup a day
[18:13] <bac> rick_h_:  you got any pre-imp-ish thoughts on bug 1263112 ?
[18:13] <_mup_> Bug #1263112: charmworld proof and ingest does not properly support inheriting bundles <charmworld:Triaged> <https://launchpad.net/bugs/1263112>
[18:13] <bac> rick_h_: it would take me all day to upload that backup file.  :(
[18:14] <rick_h_> bac: I think I can remember enough to walk you through it if you want
[18:16] <bac> rick_h_: i'm ok winging it but thought i'd ask before starting.  problem statement is clear.
[18:16] <rick_h_> bac: right, the general thing is that charmworld ingest seems to support it
[18:16] <rick_h_> bac: and we shared some logic with the deployer that supports it
[18:17] <rick_h_> bac: but when the proof bits were written we had no examples and I didn't understand it so kind of skipped the feature
[18:17] <rick_h_> bac: so any changes should just be in the proof bits in charmworld or the proof library in order to allow ingest to accept the inheritance based bundles
[18:18] <rick_h_> bac: and I found one from hazmat that's attached to the bug as a narly example. If that one ingests then everything should be good
[18:18] <rick_h_> bac: I believe that demo file works with the deployer, so we need to make sure it'll ingest
[18:18] <bac> rick_h_: great extra info.  thanks.
[18:51] <hatch> Makyo ping
[18:52] <Makyo> Yo
[18:53] <jcastro> hey rick_h_
[18:53] <jcastro> https://jujucharms.com/fullscreen/search/precise/mongodb-20/?text=mongodb
[18:53] <jcastro> if I change the description to be proper markdown
[18:53] <rick_h_> jcastro: party, looking
[18:53] <jcastro> will the bullets render properly?
[18:54] <rick_h_> jcastro: depends. We do some custom css to make non-markdown bullets ok
[18:54] <rick_h_> jcastro: so not sure, worth a try
[18:54] <jcastro> ok
[18:54] <jcastro> I can do whichever when I review the bullets
[18:54] <jcastro> I'll try real markdown
[18:54] <jcastro> will a blank line in the metadata.yaml fly?
[18:55] <rick_h_> if proof says it's valid yaml should be fine
[18:55]  * rick_h_ isn't a yaml expert
[19:02] <jcastro> well it all passes proof
[19:02] <jcastro> so it must work fine. *g*
[19:03] <rick_h_> :)
[19:17] <benji> jcastro and rick_h_: YAML is a superset of JSON, so if it's cool in JSON you know it's cool in YAML
[19:17] <jcastro> ok so in a description I would escape \"
[19:45] <gary_poster> light table open-sourced: http://www.chris-granger.com/2014/01/07/light-table-is-open-source/ for py, js, css, clojure so far.  Nifty editor exploring new possibilities but also open source as opposed to ST.
[19:50] <rick_h_> jujugui quick review please of test cleanup https://github.com/juju/juju-gui/pull/57/files qa is the fact that the tests still pass :)
[19:51] <gary_poster> on it
[19:52] <gary_poster> rick_h_: done :-)
[19:52] <rick_h_> thanks gary_poster 
[19:52] <gary_poster> thank you!
[22:10] <huwshimi> Morning
[22:46] <hatch> hey huwshimi 
[22:46] <hatch> hows it going?
[22:52] <huwshimi> hatch: Good thanks. Yourself? Enjoying London?
[22:54] <hatch> it's alright, it seems like people are afraid of the dark or something lol
[22:54] <hatch> nothing near as much happening as on last sprint
[22:56] <hatch> like out in the streets I mean
[22:56] <huwshimi> hah
[22:57] <hatch> might head into soho or something to see maybe if there is something going on there