[05:33] <sebas5384> hey! o
[05:33] <sebas5384> o/
[05:33] <sebas5384> somebody know what happened with the service's settings in the juju-gui ?
[05:41] <rick_h_> sebas5384: what do you mean?
[05:41] <sebas5384> rick_h_: it isn't appearing anymore
[05:43] <rick_h_> sebas5384: umm, no but thakns for mentioning it. We'll get folks right on it
[05:43] <rick_h_> huwshimi: any time left in the day? ^
[05:43] <sebas5384> http://awesomescreenshot.com/0154cnfkad
[05:43] <huwshimi> rick_h_: Yep, let me take a look
[05:44] <sebas5384> thanks rick_h_ !
[05:44] <rick_h_> sebas5384: yep, can replicate on demo.jujucharms.com as well
[05:44] <rick_h_> sebas5384: ty, will file a bug and get the guys on it right away
[05:47] <rick_h_> huwshimi: added a card marked critical with a bug on it. I assigned it to hatch assuming you'll not have time in your day to complete it but plese leave notes/etc either in the bug or the card
[05:48] <huwshimi> rick_h_: Yep, sure thing. I can see there's an error there so I'll try and track that down and see how I go.
[05:48] <rick_h_> huwshimi: review done?
[05:48] <huwshimi> rick_h_: Sure is :)
[05:48] <rick_h_> huwshimi: <3
[05:51] <sebas5384> rick_h_ and huwshimi thanks for the fast response :)
[05:52] <rick_h_> sebas5384: np, not sure how that one slipped by but hopefully it's a small fix do to some new apis we're using and should be fast. We'll try to get a new rev'd charm out by EOD
[05:52] <rick_h_> US EOD that is
[05:52] <sebas5384> I'm going to demonstrate juju gui at a conference tuesday
[05:53] <rick_h_> sebas5384: you'll definitely have it by then
[05:53] <rick_h_> sebas5384: fyi, the icon thing is a bug in chrom v40 we're tracking upstream
[05:53] <rick_h_> sebas5384: so FF is currently the best demo browser unfortunately
[05:53] <rick_h_> sebas5384: until chrome fixes the svg issue and get it into a release
[05:55] <rick_h_> https://bugs.launchpad.net/juju-gui/+bug/1415550 for tracking
[05:55] <mup> Bug #1415550: Charm's SVG icons with wrong size in Chrome <icon> <svg> <juju-gui:Confirmed> <https://launchpad.net/bugs/1415550>
[05:56] <sebas5384> yeah definitively rick_h_ i'm going to use it with firefox for now
[05:57] <rick_h_> sebas5384: looking at the upstream bug though looks like v41 will include a fix yay!
[05:58] <sebas5384> rick_h_: uhuu!
[05:58] <sebas5384> :)
[05:59] <huwshimi> rick_h_: So it looks like hatch landed a branch which fixed this a couple of days ago: https://github.com/juju/juju-gui/commit/9dabbda4597c53545fc9ed912165a583d3fd1337
[06:00] <huwshimi> rick_h_: I've rolled back to the commit before that and confirmed that the bug was there before that commit.
[06:00] <huwshimi> rick_h_: devel should be fine now.
[06:02] <rick_h_> huwshimi: ok, awesome. We should get a release rolling then. I'll make sure to bug hatch about it
[06:02] <rick_h_> huwshimi: can you email -peeps with your findings and I'll reply asking for the release today please?
[06:02] <huwshimi> rick_h_: Sure thing.
[06:03] <rick_h_> ty kindly
[06:09] <huwshimi> rick_h_: Sent!
[06:09] <rick_h_> huwshimi: awesome
[15:27] <hatch> frankban: wouldyou be able to point me to the correct place to inspect the path in guiserver? I was thinking the on_message method
[15:27] <frankban> hatch: looking at the code
[15:28] <hatch> tornado is very confusing
[15:30] <frankban> I've found it less confusing than other async frameworks
[15:31] <hatch> quite possible - it feels to me like it's shoehorning async into a language that isnt
[15:31] <hatch> (I wrote an async framework for php back in the day) 
[15:31] <hatch> :)
[15:31] <hatch> but php didn't have yeild so I actually had an event loop lol
[15:32] <frankban> hatch: yield is just a way to avoid the callbacks hell
[15:34] <frankban> hatch: so, I'd presume you'll have to extend url routing in server/apps.py
[15:34] <frankban> hatch: right now only /ws$ is routed to the websocket handler
[15:35] <hatch> and what's the path supposed to be now?
[15:35] <hatch> won't it still be /ws/uuid/
[15:36] <frankban> hatch: to avoid confusion, I'd make them reflect the juju API server ones. so we need to keep handling /ws$ and add support for /ws/environment/:env_uuid:/api
[15:37] <frankban> hatch: so same as juju but in the ws/ namespace
[15:37] <hatch> oh so they actually added the "environment" keyword in there
[15:37] <hatch> I thought that was just a placeholder :)
[15:37] <frankban> hatch: heh, no, I think that's the real endpoint path
[15:38] <hatch> alright, is there a way I can test the api using curl or the like to see if that is indeed the endpoint?
[15:40] <frankban> hatch: I am pretty sure that's the real endpoint. however, for these kind of tests I usually use ipython + https://pypi.python.org/pypi/websocket-client/ (it's really quick with the latter to establish a websocket connection)
[15:41] <hatch> ahh cool
[15:41] <hatch> ok well first is gui release then I'll continue on your reivew comments and this
[15:41] <frankban> hatch: for instance, I use this script sometimes to watch env changes: http://pastebin.ubuntu.com/10093532/
[15:41] <hatch> oh yeah...just tiny :P
[15:42] <frankban> heh but easy to change to make other calls
[17:09] <hatch> makyo_: didn't you do a guicharm release in 2015?
[17:09] <hatch> https://jujucharms.com/juju-gui/trusty/17 see the revisions list
[17:10] <hatch> or was that updated but never released?
[17:59] <hatch> makyo_: whenever you return I'm wondering if something borked up becuase there is no git tag to match 1.3.0
[17:59] <hatch> wait there is on trunk...hmm
[18:00] <makyo_> https://github.com/juju/juju-gui/releases/tag/1.3.0 ?
[18:00] <hatch> might help if I used the --tags
[18:00] <hatch> *facepalm*
[18:01] <makyo_> Whew
[18:01] <makyo_> Had me worried
[18:01] <hatch> so that's one problem down - now the charm release :)
[18:01] <hatch> Makyo: so did you push a new charm release and it maybe not make it onto jujucharms?
[18:02] <hatch> I was pretty sure you did one rather recently
[18:02] <hatch> in fact http://bazaar.launchpad.net/~juju-gui-charmers/charms/trusty/juju-gui/trunk/files
[18:02] <hatch> you did
[18:02] <Makyo> I did, yeah.
[18:03] <Makyo> https://jujucharms.com/trusty/juju-gui in the releases dir is juju-gui-1.3.0.xz
[18:03] <Makyo> So maybe the changelog is borked?
[18:05] <hatch> hmm yeah that's odd
[18:06] <hatch> ok well I'll just go on the assumption that it's the UI that's a little busted because the code all looks good
[18:34] <hatch> Makyo: was sphinx supposed to be in the sysdeps?
[18:35] <hatch> oh it is....ok then...hmm
[19:12] <hatch> code release done - commits can resume to the gui
[19:13] <hatch> still working on the charm side