UbuntuIRC / 2014 /12 /04 /#juju-gui.txt
niansa
Initial commit
4aa5fce
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
[00:41] <rick_h_> hatch: right, there are a few known broken ones :/
[00:41] <hatch> ok and we are just 'ok' with that?
[00:41] <rick_h_> hatch: which is why getting the updated command to quickstart is required. and getting the details panel updated asap so that it works as well
[00:42] <hatch> alright - I just wanted to know how far down the rabbit hole I needed to go :)
[00:42] <rick_h_> hatch: so there are two things we know break. 1) the details panel doesn't come up because the id isn't valid
[00:42] <rick_h_> hatch: so that's your next branch
[00:42] <rick_h_> hatch: and 2) the quickstart command isn't valid, but we have a way around that
[00:42] <rick_h_> hatch: is there another I'm missing atm?
[00:43] <hatch> 1) correct, but to fix this we need to switch to the v4 id's and the resulting data morphing
[00:44] <hatch> *phew* thought I accidentally installed Ubuntu into the wrong partition on my macmini
[00:44] <rick_h_> hatch: hmm, I guess we need to look at that one. I assumed we'd go to the details next. You're right that it might cause issues as that id is passed and used in tabs/etc
[00:44] <hatch> but grub just overwrote refind
[00:45] <hatch> oh it definitely causes issues :)
[00:45] <hatch> but nothing that's not fixable
[00:45] <rick_h_> hatch: so the ways through that are to either store the old id around in a new property and do some find/replace business
[00:45] <hatch> it'll just slow the search down because we'll pull all the data down at once
[00:45] <rick_h_> hatch: or to stick the new id in a new attribute
[00:45] <hatch> so use the 'old' method but with the new api
[00:45] <rick_h_> so that you can roll things to it one by one
[00:45] <rick_h_> huh?
[00:45] <hatch> lol wana hop into standup for a bit?
[00:45] <rick_h_> right, but that's ok because it's a single entity at that point
[00:46] <rick_h_> yea, let me get my headphones meet you there
[00:46] <hatch> ok be there in a sec
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
[00:57] <rick_h_> hangouts ftw
[00:57] <rick_h_> :)
[01:00] <hatch> ahah Ubuntu now dual booting on mac mini
[01:01] <rick_h_> woot
[01:01] <hatch> had me freaked out - grub overwrote the osx bootloader and refind
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== jcw4 is now known as jw4
[15:03] <rick_h_> hatch: http://www.infoworld.com/article/2855057/application-development/why-iojs-decided-to-fork-nodejs.html
[15:03] <hatch> lol *drammmmaaaaa*
[15:05] <rick_h_> well crazy drama if uber and other companies are jumping on board
[15:06] <rick_h_> and you thought just running and keeping npm up was bad :P
[15:06] <hatch> well in all seriousness node runs on an old unsupported version of v8
[15:06] <hatch> so it must be impossible to get anything done on it
[15:06] <rick_h_> yea, but a fork in a community that already feels held together by shoe strings
[15:06] <rick_h_> crazy
[15:07] <hatch> yeah - but js is everywhere and people don't have much of a choice so people will keep using it
[15:07] <hatch> unless Dart gets a foothold
[15:07] <rick_h_> guess so, crazy stuff
[15:07] <hatch> you can now write android chrome apps with Dart
[15:07] <hatch> so it's getting closer I think :)
[15:08] <hatch> at IO this year I think they are going to release that it's going to be in Chrome/Android
[15:08] <hatch> maybe :)
[15:11] <hatch> problem with this fork is that now modules will likely have to support both or people will have to mark 'this works with this version of node'
[15:11] <hatch> because js on the client didn't have enough issues
[15:11] <hatch> now we have multiple serverside targets too
[15:11] <hatch> lol
[15:19] <jrwren> hahaha, jenn was right. javascript is replacing nodejs :)
[15:23] <hatch> say what?
[15:27] <hatch> who's jenn?
[15:28] <hatch> and what js replacing nodejs?
[15:34] <jrwren> hatch: jennschifer?
[15:35] <hatch> yeah and what do you mean replacing nodejs?
[15:35] <hatch> nodejs was always based on v8
[15:35] <jrwren> hatch: oh jeff :p
[15:35] <hatch> I feel like I'm missing something
[15:36] <jrwren> hatch: yes. the best computer satire ever written.
[15:36] <jrwren> hatch: this started it for me: https://medium.com/cool-code-pal/how-node-js-is-going-to-replace-javascript-cf72b588b1b
[15:37] <jrwren> hatch: which is extra hilarious if you read those "Java is better than Javascript" links, becuase they aren't satire.
[15:37] <jrwren> that one was followed by some others, but then: https://medium.com/cool-code-pal/how-javascript-is-going-to-replace-node-js-33cc50bfe64c
[15:40] <hatch> sorry all I could muster was a 'heh' :)
[15:41] <jrwren> hatch: oh man, I nearly died of suffucation from laughing.
[15:41] <hatch> maybe because you don't see the stupidity on a daily basis :)
[15:41] <jrwren> "Until Now. Though." I want to frame that and put it on my wall. It makes me lol every time.
[15:41] <jrwren> The "Java is better than Javascript" did make me sad for our world.
[15:50] <rick_h_> uiteam call in 10 kanban please
[16:22] <hatch> MBP lint time: [35s], Mini lint time[52s] :)
[16:22] <hatch> that's quite a difference
[16:28] <rick_h_> no one said the mini was fast :P
[16:30] <hatch> haha no but I wouldn't have bet that it was THAT much slower
[16:35] <hatch> rick_h_: did you set up volume controls etc on your kinesis in Ubuntu?
[16:44] <lazyPower> rick_h_: sorry I didn't bookmark this before - can you repoint me at the jujucharms.com bug tracker?
[16:44] <lazyPower> i was mid-email composition and remembered you sent a link to me prior for filing bugs
[16:46] <hatch> frankban: where should I file quickstart bugs?
[16:46] <hatch> lazyPower: see eco
[16:46] <frankban> hatch: https://bugs.launchpad.net/juju-quickstart
[16:47] <rick_h_> lazyPower: https://github.com/CanonicalLtd/jujucharms.com/issues
[16:47] <rick_h_> lazyPower: the bugs link in the footer should be updated with a release on monday so the footer has a 'report a bug link' we'll do
[16:47] <lazyPower> gracias
[16:47] <hatch> frankban: thanks
[16:48] <rick_h_> hatch: no, I don't do keyboard volume controls
[16:50] <lazyPower> https://github.com/CanonicalLtd/jujucharms.com/issues/19
[16:51] <hatch> frankban: thanks https://bugs.launchpad.net/juju-quickstart/+bug/1399274
[16:51] <mup> Bug #1399274: quickstart should install juju-local by default <juju-quickstart:New> <https://launchpad.net/bugs/1399274>
[16:52] <hatch> rick_h_: ahh ok - with the OSX host I had some of the F keys remapped to do the audio
[16:53] <lazyPower> rick_h_: if yinz could sneak that update into teh monday update, i'll <3 you long time
[16:54] <hatch> lazyPower: regress to highschool? :P
[16:54] <frankban> hatch: quickstart already installs juju-core and juju-local if juju is not found on the machine
[16:54] <lazyPower> hatch: i watched full metal jacket over the weekend. Clearly it has stained my brain
[16:54] <hatch> frankban: ok I'll update the bug - I installed juju then installed quckstart
[16:54] <hatch> so a conditional must be broken
[16:55] <frankban> hatch: so, juju is there but juju-local is not right?
[16:55] <rick_h_> lazyPower: will try to get it in tomorrow
[16:55] <hatch> frankban: correct
[16:55] <frankban> hatch: ok, thanks for reporting the bug
[16:56] <hatch> frankban: np, I updated the bug
[17:03] <rick_h_> ok, this I have to share, love love love this https://twitter.com/founderscode/status/540462193574047744
[17:07] <hatch> bahaha love it
[17:09] <hatch> well the ubumini does NOT like provisioning new lxc machines
[17:10] <hatch> they take friggen forever
[17:10] <hatch> lol
[17:10] <hatch> will have to investigate
[17:11] <rick_h_> hatch: well it's doing it for the first time right? so will have to get images and the like?
[17:12] <hatch> ohh right right
[17:12] <hatch> I forgot about the images
[17:12] <frankban> not ubumini's fault!
[17:13] <hatch> lol
[17:15] <hatch> rick_h_: no matter what I try I cannot reproduce that firefox bug - might be a maas only bug, we'll probably have to set up a desktop share session to figure out what the issue is...
[17:15] <jrwren> hatch: does mac mini have ssd or is it a 2.5" 5400 rpm ?
[17:16] <rick_h_> hatch: ok
[17:16] <rick_h_> hatch: join #juju on canonical irc
[17:18] <hatch> jrwren: crucible 128 ssd
[17:34] <hatch> rick_h_: if you get a moment I've made a pr for this branch, just working on fixing the tests now
[17:34] <hatch> rick_h_: you'll notice that it's all still one method
[17:34] <hatch> I will split it out however in a follow-up, I just didn't want to conflate this branch even more
[17:47] <rick_h_> hatch: ok, going to get some food for the brain but will look
[18:18] <hatch> stepping out for lunch bbl
[19:32] <hatch> oh man these tests are going to be tough - the 'temporary' changes are causing big headaches heh
[19:32] <rick_h_> how so?
[19:32] <hatch> well the tests pass a entity into the views
[19:33] <hatch> which we no longer check for
[19:33] <rick_h_> (put my evil brain to work for you :) )
[19:33] <hatch> but this change is temporary
[19:33] <hatch> so I could just skip the tests?
[19:33] <rick_h_> :P
[19:33] <rick_h_> nevar! it passes an entity to which tests?
[19:33] <hatch> test_browser_charm_details.js
[19:33] <hatch> for example
[19:33] <rick_h_> and we're not passing it in atm, but that doesn't make the test invalid?
[19:34] <hatch> it makes the tests fail because the tests pass in a mock entity
[19:34] <hatch> which we no longer use
[19:34] <rick_h_> but we broke it from the other end?
[19:34] <rick_h_> at least that's what we talked about yesterday I thought
[19:34] <rick_h_> hatch: hangout time please?
[19:34] <hatch> no the view handles requesting the data from the charmworld
[19:35] <hatch> (which is bad)
[19:35] <hatch> ok joining
[19:38] <rick_h_> <3 hangouts :)
[19:42] <hatch> haha indeed
[19:42] * hatch feels like an idiot now
[19:42] <hatch> haha
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
[20:35] <hatch> after doing that properly only 5 test failures :)
[20:35] <hatch> vs the hundred or so from before :P
[20:36] <rick_h_> hatch: :)
=== kadams54 is now known as kadams54-away
[21:59] <huwshimi> Morning
[22:03] <rick_h_> huwshimi: you able to do our calls earlier today?
[22:04] <huwshimi> rick_h_: Sure, anytime!
[22:04] <rick_h_> Makyo: hatch ? ^
[22:05] <hatch> rick_h_: anytime
[22:07] <hatch> tonight I have to move my irc over to ubumini - going to try weechat....mostly because I can't find an irc client that doesn't look like garbage
[22:09] <rick_h_> hatch: heh, welcome to the cli world
[22:09] <rick_h_> ok, once we hear back from Makyo we'll do the call. I'd like to chat/sync up on gui login stuff as part of it
[22:09] <hatch> there is one which is designed like gnome 3 which looks nie
[22:09] <hatch> nice
[22:09] <hatch> but it's missing features
[22:10] <hatch> I don't even know what Trusty prefers to run
[22:10] <hatch> I thought it was GTK3 stuff
[22:10] <hatch> (so that it'll take advantage of the system theme settings)
[22:11] <hatch> 6 more tests to write!!! ooooooo yeahhh
[22:39] <huwshimi> What's the way to clear local changes to our index.html?
[22:40] <rick_h_> clear local changes?
[22:40] <rick_h_> git co index.html
[22:42] <huwshimi> rick_h_: I mean, cached in the browser, I remember we had to do something like visit a url in the browser and clear out something
[22:43] <hatch> huwshimi: do you have the devtools open?
[22:43] <hatch> and cache set to no?
[22:43] <huwshimi> Maybe we don't have to do that anymore...
[22:44] <huwshimi> hatch: yeah, there was some specific thing a long time ago
[22:44] <huwshimi> It appears to be working now anyway
[22:44] <hatch> if that's not working then you can clear the cache in chromes cache thing
[22:44] <hatch> I think that's what you meant
[23:03] <Makyo> Promises are literally worse than geese.
[23:04] <rick_h_> Makyo: lol
[23:04] <Makyo> They eat all exceptions, including assertionerrors, so tests just...freeze with nothing to show, since the promise never returns.
[23:04] <rick_h_> Makyo: up for the AU calls?
[23:04] <Makyo> rick_h_, yep
[23:04] <rick_h_> Makyo: huwshimi hatch call time please
[23:04] <hatch> joining
[23:18] <Makyo> huwshimi, http://bazaar.launchpad.net/~juju-gui-charmers/charms/trusty/juju-gui/trunk/view/head:/hooks/utils.py#L347
[23:24] <hatch> lol eject me
[23:24] <hatch> I didn't actually know you could kick ppl
[23:30] <huwshimi> hatch: Did it work?
[23:31] <hatch> yep
[23:31] <huwshimi> :)
[23:31] <hatch> and for that - you have to qa my branch :P
[23:31] <hatch> https://github.com/juju/juju-gui/pull/671
[23:31] <hatch> :)
[23:31] <hatch> I still need to write out the QA details
[23:32] <huwshimi> hatch: Yeah, I was just about to say...
[23:32] <huwshimi> "To QA"
[23:34] <hatch> ok qa instructions are available
[23:34] <hatch> :)
[23:35] <hatch> rick_h_: I'm going to work on converting the bundles details page to use the apiv4 data in the next branch
[23:35] <hatch> sound good
[23:35] <hatch> ?