/srv/irclogs.ubuntu.com/2014/06/11/#juju-gui.txt

huwshimihatch: This bug still exists: https://bugs.launchpad.net/juju-gui/+bug/132155800:09
_mup_Bug #1321558: Destroying a service leaves inspector visible <juju-gui:Triaged> <https://launchpad.net/bugs/1321558>00:09
huwshimihatch: Also, your caching branch is lovely!00:12
rick_h_huwshimi: hmm, that was marked as fixed. The card for that was done by Makyo 00:21
huwshimirick_h_: Was the one for hiding the ghost inspector on deploy?00:21
huwshimi*that the00:22
rick_h_huwshimi: no, that bug you linked above on the destroying leave the inspector open00:22
rick_h_huwshimi: moved the card into urgent maint. 00:22
rick_h_Makyo: ^ 00:22
huwshimirick_h_: Oh, I mean, didn't Makyo do the one about hiding the ghost inspector on deploy00:22
rick_h_huwshimi: not sure, I just did a search on the bug number in the kanban board and found the card00:23
huwshimioh I see00:23
rick_h_I'll have to chase down the branch that was submitted and see what is up00:23
rick_h_huwshimi: but please make sure to note that one and the card in an email summary of the QA results please00:24
hatchhuwshimi thanks :)00:24
huwshimirick_h_: Will do, I have some small visual cleanups that I'll do myself today00:24
rick_h_huwshimi: awesome thanks00:24
hatchis comingsoon very slow for you guys?00:28
hatchoh maybe it's just me00:28
rick_h_hatch: no00:28
hatchhuwshimi in your bug, how do you reproduce it?00:28
hatchcan you add steps because I am not able to reproduce on comingsoon00:29
huwshimihatch: I've added them to the bug: https://bugs.launchpad.net/juju-gui/+bug/132155800:37
_mup_Bug #1321558: Destroying a service leaves inspector visible <juju-gui:Triaged> <https://launchpad.net/bugs/1321558>00:37
hatchhuwshimi thanks, the bug only happens with ghost services not deployed ones00:38
hatchshould be an easy fix the url isn't changing so just needs to fire a changestate event00:38
hatchgood catch though00:39
huwshimihatch: Ah yes, you are right. I thought I had reproduced it on a deployed service, but can't seem to now.00:40
hatchyeah, just looked, huwshimi  if you have time today you could probably bang out a fix for it real quick-like :)00:41
hatchthink you might have time?00:41
hatchif not I can probably do it while watching some tv tonight heh00:41
hatchhuwshimi here is the fix (sans tests) https://gist.github.com/b85f7d0ebdbf05ee063200:43
hatch:)00:43
huwshimihatch: It's ok I'll do it00:44
rick_h_hah! just used the chrome dev tools "copy a cURL" feature. sweetness00:44
huwshimihatch: Unless you get to it first :)00:45
hatchrick_h_ haha cool, I've always wanted to use that :)00:45
hatchhuwshimi true, although I have to start cooking supper right away so it won't be for a few hours for sure00:45
rick_h_needed a QA bundle file so went to the gui, went to code, loaded the bundle file and copied the curl command from the network tab to download it :)00:46
hatchkeep me posted if you do tackle it00:46
hatchhaha nice nice00:46
huwshimihatch: Yep, I'll let you know if I start00:46
rick_h_bwuhahaha BradCrittenden you rule. <3 this00:48
rick_h_92056301:00
hatchhuwshimi I'm going to fix that bug now03:27
huwshimihatch: OK :)03:27
hatchjust watched some House of Cards and Orange is the new Black03:27
hatchneed a break03:28
hatchlol03:28
rick_h_lol03:28
hatchhuwshimi bug is fixed if you want to take a look for review/qa if you find some time04:08
huwshimihatch: Ah sure, let me take a look04:09
hatchhuwshimi I'm hopping offline, if alls good feel free to shipit04:09
huwshimihatch: Sure04:09
hatchthanks, have a good night04:09
huwshimihatch: You too04:10
frankbanmorning rogpeppe1: is juju/charm ready to be used?08:55
rogpeppe1frankban: yeah08:56
rogpeppe1frankban: i'm just about to push a branch that changes juju-core to use it08:56
frankbanrogpeppe1: cool08:57
frankbanrogpeppe1: could you please review https://github.com/juju/juju/pull/73 ?09:05
rogpeppe1frankban: looking09:07
frankbanthanks09:07
rogpeppe1frankban: the PR doesn't seem to update dependencies.tsv - is that because it's been done in a previous PR?09:09
frankbanrogpeppe1: yes, http.go was moved to external testing some days ago09:09
rogpeppe1frankban: LGTM then09:10
frankbanrogpeppe1: thanks09:10
frankbanrogpeppe1: I'll start the store migration right after you merge your current branch09:11
rogpeppe1frankban: cool. am currrently running the tests.09:11
rogpeppe1frankban: https://github.com/juju/juju/pull/7409:20
frankbanrogpeppe1: looking09:20
frankbanrogpeppe1: could you please create a juju/store repo and give me permissions?09:21
rogpeppe1frankban: sure09:21
rogpeppe1frankban: i wonder if the repo should be named "charmstore". what do you think?09:22
frankbanrogpeppe1: it will also be a bundle store in the future. So I guess store can be ok, but that's not a strong opinion09:23
rogpeppe1frankban: bundles are bundles of charms, really09:23
rogpeppe1frankban: i'll raise it in #juju-dev09:23
frankbanrogpeppe1: yeah09:23
frankbanrogpeppe1: what about github.com/bmizerany/assert and deps? were they missing?09:27
rogpeppe1frankban: yup09:27
frankbanrogpeppe1: LGTM09:28
=== rogpeppe1 is now known as rogpeppe
rogpeppefrankban: i've created the repo and added juju-hackers as collaborators09:59
rogpeppefrankban: github.com/juju/charmstore10:00
frankbanrogpeppe: cool, thanks. I'll wait for your branch to land and then start mgrating the store10:00
frankbanrogpeppe: you have a conflict10:02
rogpeppefrankban: oh, darn10:02
=== rbasak_ is now known as rbasak
frankbanrogpeppe: how is it going?11:01
rogpeppefrankban: running tests again after merging11:02
rogpeppefrankban: worker/uniter/debug just timed out11:02
frankbanrogpeppe: :-/11:02
frankbanrogpeppe: some of the tests seems to have some weakness11:03
rogpeppefrankban: but just passed when i ran it again11:03
rogpeppefrankban: yeah11:03
rogpeppefrankban: it took 0.2s to run the second time11:03
frankbanrogpeppe: heh11:03
rogpeppefrankban: my computer just decided to reboot randomly11:07
frankban:-/11:08
rogpeppeonce upon a time if the kernel panicked, you'd see some kind of a message11:08
frankbanrogpeppe: so what do you think about this plan: I will 1) migrate store 2) add README etc... 3) change core to use external store in the few places it is imported. You a) wait for 2 (add README etc) b) add to charmstore the server entry points (e.g. cmd/charmd/main.go), including README updates on how to start the charmstore server and c) remove those bits from core11:08
frankbanrogpeppe1: ^^^11:14
rogpeppe1frankban: i haven't seen anything, sorry11:14
frankbanrogpeppe1: so what do you think about this plan: I will 1) migrate store 2) add README etc... 3) change core to use external store in the few places it is imported. You a) wait for 2 (add README etc) b) add to charmstore the server entry points (e.g. cmd/charmd/main.go), including README updates on how to start the charmstore server and c) remove those bits from core11:15
* rogpeppe1 thinks11:17
rogpeppe1frankban: how about, instead, migrating store and cmd/{charmd,charmload,charm-admin} all together. then there's nothing in core that imports store11:19
rogpeppe1frankban: because those commands feel like they're more part of the charm store than juju-core itself11:20
rogpeppe1frankban: i will suggest that in #juju-dev11:20
frankbanrogpeppe1: charm-admin depends on juju/cmd. That said, the result is the same, b) and c) are about doing that move. My proposal is just to proceed with incremental steps, so that mechanical branches are really mechanical11:22
frankbanrogpeppe1: so, focus on the goal of having an external store, and then move the commands where they belong11:22
rogpeppe1frankban: ah, i see11:23
rogpeppe1frankban: yeah, your approach seems fine11:23
frankbanrogpeppe1: cool11:23
frankbanrogpeppe1: uhm: your merge failed: godeps: cannot parse "/mnt/jenkinshome/jobs/github-merge-juju/workspace/tmp.o7sFxEIu8x/RELEASE/src/github.com/juju/juju/dependencies.tsv": cannot find directory for "github.com/bmizerany/assert": not found in GOPATH11:30
rogpeppe1frankban: oh frick11:30
rogpeppe1frankban: thanks11:30
rogpeppe1frankban: i'll remove that dependency for the time being11:31
frankbanrogpeppe1: +111:32
BradCrittendenmorning rick_h_11:34
=== BradCrittenden is now known as bac
frankbanrogpeppe1: created the cards for the plan above11:35
rogpeppe1frankban: lovely, ta11:36
rick_h_bac: morning12:08
bachi rick_h_.  what was your message from last night about?  the discussing in vague terms my awesomeness.12:08
rick_h_bac: QA went well for me yesterday. Had one note where if the terminal window is small, and you go in to 'use' one of the environments, you have to scroll down with the down arrow before you can select buttons12:09
rick_h_bac: oh, just was so cool to deploy a bundle and such from OSX. 12:09
bacyeah, pretty sweet12:09
bacrick_h_: is that term size issue os x specific or would that be the case on linux too?12:11
rick_h_bac: I think it'll be any terminal. I don't notice it because of the bigger display/terminals I use on linux vs OSX the default is so small12:12
rick_h_bac: so I was debating about filing a bug and wanted to see if anyone else ran across it during qa12:13
bacrick_h_: i tested the interactive stuff when i first started the process but have not made it a part of general QA as the interactive piece has been static.  so i'm glad you saw this issue.12:14
rick_h_bac: just tried it out here on linux and yep, it's just a general thing with the UI. I happened to have a terminal of *just* the right height where I could seee the buttons, but there was a small amount of scoll available12:16
rick_h_bac: so definitely nothing block about and not even sure it's something we can do something about12:17
frankbanrick_h_: we can make the buttons always visible (like the status bar): I would consider this a minor/nice to have and not a release blocker.12:19
rick_h_frankban: cool, I'll file a bug then for now.12:21
rick_h_bac: but QA went well for me and was very exciting to try out after writing docs and emails all day :)12:21
bacrick_h_: cool.  i'll wait for kyle to have a go and then do the release if all is good.12:22
rick_h_bac: sounds good12:22
bacfrankban: if you have a moment could you review https://codereview.appspot.com/103310043  -- it has updates to the HACKING doc for new release procedures.  You may want to read the whole section carefully, not just the changes in this branch.  I've landed a few mods there self-reviewed.12:41
frankbanbac: I will12:42
frankbanrogpeppe1: could you please take a look at https://github.com/juju/charmstore/pull/1 ?12:42
rogpeppe1frankban: looking12:42
rogpeppe1frankban: LGTM12:43
frankbanrogpeppe1: thanks12:43
frankbanrogpeppe1: another one? https://github.com/juju/charmstore/pull/213:06
rogpeppe1frankban: looking13:06
rogpeppe1frankban: LGTM13:07
frankbanrogpeppe1: thank you!13:07
jcsackettmorning all.13:16
rick_h_morning jcsackett 13:17
rick_h_jcsackett: can you assis with release today? QA/review Huw's branch and do some QA please. 13:17
rick_h_assist that is13:17
jcsackettrick_h_: was already planning on it--saw your email.13:18
rick_h_jcsackett: ty much13:18
jcsacketti'll start with Huw's branch and then start whacking the GUI. we have specific areas we're worried about?13:18
rick_h_jcsackett: we're just making the inspector left release. So with no flags, just does anything in the GUI have an issue before we release and update jujucharms.com with it13:19
jcsackettno flags, got it.13:20
frankbanrogpeppe1: last one for the store: https://github.com/juju/juju/pull/7613:28
rogpeppe1frankban: cool13:28
rogpeppe1frankban: looking13:28
frankbanthnaks13:28
frankbanbac: review done13:28
bacty13:28
rogpeppe1frankban: LGTM13:29
frankbanrogpeppe1: thank you, merging13:29
=== tvansteenburgh1 is now known as tvansteenburgh
jcsackettrick_h_: huw's branch is good; there's no reason to hold off on shipping it, is there?13:42
rick_h_jcsackett: nope thanks13:43
frankbanbac: replied13:44
hatchgithub added a 'jump to file' button13:59
hatchkadams54 did you see my comment on your PR?14:00
kadams54I did.14:01
* rogpeppe1 lunches14:01
bacfrankban: yeah, that step was attempting to do two things: use pre-booted env and remote bundle.  i'll beef up the description.14:02
kadams54Here's what I think is happening: the machine view panel… er… view has at least one child view, which means the child view's container is connected to a child node.14:02
kadams54So when container.empty() is called, the child node is removed14:02
kadams54And when the destructor is called on the child view, it attempts to empty its container and throws an error because there's no longer an associated DOM node.14:03
bacrick_h_: the date in the first sentence of https://docs.google.com/a/canonical.com/document/d/1PI4XPNxVUP3mXqce-jxtT5KgqdZoTuvJZ71W-mSiCZg/edit  does not match the later date14:03
kadams54getDOMNode returns null14:03
hatchkadams54 right, but there should be no child view rendered into the createMachine view14:07
hatchif there is then something is wrong14:07
hatchcreate machine view should be managing it's own child views (if there are any)14:07
kadams54I think there are quite a few child views… machine headers, service scale up, create machine, etc.14:09
kadams54The one that started erroring when I changed to container.empty() was service-scale-up-view.js14:09
hatchyeah....but create machine and scale up are siblings14:09
hatchnot parent/child14:09
kadams54Maybe, but not in the DOM14:09
hatchwell then the DOM structure is incorrect14:10
hatchyou can't have sibling views that require one to be rendered into the other14:11
kadams54machine-view-panel.js, line 848 - the view passes a node as the container for ServiceScaleUpView14:11
kadams54That node is a child of MV's container14:11
hatchright14:12
hatchso why does another child of machine-view-panel destroy that node?14:12
kadams54Another child doesn't destroy it14:13
kadams54machine-view-panel itself destroys it, when container.empty() is called in machine-view-panel's destructor14:13
backadams54: you still willing/have time to do the quickstart QA this morning?14:13
kadams54bac: Yeah, I started on that last night14:13
bacoh, cool14:13
hatchkadams54 no the empty() is called in 'createMachineView' not 'machineViewPanel'14:14
hatchkadams54 https://github.com/juju/juju-gui/pull/375/files#r1361872814:14
rick_h_bac: ty, updated14:15
kadams54hatch: Ah, that's my problem :-) For some reason I changed line 901 in machine-view-panel.js :-)14:16
hatchlol oh boy14:17
jcsackettrick_h_: one minor bug that i believe is linked to inspector left https://bugs.launchpad.net/juju-gui/+bug/132893214:17
_mup_Bug #1328932: "tutorial" link under "help & feedback" sends you to /sidebar and does nothing <juju-gui:New> <https://launchpad.net/bugs/1328932>14:17
jcsackettnot remotely done looking yet.14:17
rick_h_jcsackett: rgr, ty looking14:17
hatchrick_h_ jcsackett I'll take it14:18
rick_h_hatch: rgr ty14:18
bacfrankban: here is a new section http://paste.ubuntu.com/7628821/  - i've tested that the steps work.14:29
hatchhmm looks like onboarding can never BE rendered any longer, good catch jc14:31
frankbanbac: looks good14:39
hatchrick_h_ low priority but should probably get some new assets from UX https://bugs.launchpad.net/juju-gui/+bug/132893614:39
_mup_Bug #1328936: onboarding now puts the inspector in the incorrect location <juju-gui:New> <https://launchpad.net/bugs/1328936>14:39
rick_h_hatch: oh ouch, yea. Not sure I agree on low priority though14:40
rick_h_luca: ^14:40
lucarick_h_: ah yeah14:41
rick_h_luca: I feel like that should block our release today. 14:41
lucarick_h_: if I remember right, they are just images that Spencer made.14:41
rick_h_hatch: what's the file name? 14:42
lucarick_h_:  is that correct?14:42
rick_h_luca: correct14:42
rick_h_I'm trying to find the one we're using right now14:42
hatchumm, I broke it, lemme get it back working and grab the file name :)14:43
hatchjuju-ui/assets/images/non-sprites/onboarding/3-inspector.png14:43
hatchrick_h_ luca  the issue we will have though is that the charmbrowser will be rendered underneath the new inspector image14:44
hatchso it's more work than simply changing the image14:44
rick_h_hatch: oh, but we can work with this image14:44
rick_h_hatch: we just have to relocate it and cover the sidebar14:44
hatchit'll only cover part of it14:45
hatchwhich may look worse :)14:45
lucarick_h_: Spencer can create a new image of the inspector14:45
rick_h_right, but I mean cover the sidebar (entirely) and then put this image on there14:45
lucarick_h_: he’s busy doing the google mocks but once he’s done he can send one over14:45
rick_h_luca: ok, but we'll have a height issue regardless14:45
rick_h_We have to solve this better than updating the image14:45
hatchthe sidebar is 100% height, so that image will need to be like 3000px tall to accommodate all screens 14:45
lucahatch: I see :)14:46
rick_h_right, thus we use a smaller image that's the 'top part' of a demo inspector, cover all of the sidebar and have that kindn of floating in place14:46
hatchheh, a mask in a mask14:47
rick_h_:)14:47
hatchI foresee problems in out future14:47
hatchour!14:47
rick_h_huw can do it :)14:49
hatchwell we could create a fake service and show the inspector for that service14:50
hatchthat's probably going to be the end goal14:50
lucarick_h_: hatch do you need me to action anything?14:53
hatchrick_h_ I'm not sure we want to try and do this pre-release14:54
hatchI think there will be dragons here which may end up causing us to push release14:55
hatchjujugui call in dos14:59
hatchjujugui call in Un14:59
jcsackettrick_h_, hatch: i've got another one: https://bugs.launchpad.net/juju-gui/+bug/132894114:59
_mup_Bug #1328941: Deploying a local charm shows a compacted inspector <juju-gui:New> <https://launchpad.net/bugs/1328941>14:59
rick_h_jujugui on the phone with ramm at the moment, might be late14:59
hatchok I can run it14:59
hatchjcsackett ok can you make a card in urgent plx14:59
jcsacketthatch: yup, marking the bug as high too. unless we feel "critical" is better.14:59
hatchjcsackett high is fine, we'll do it right away either way15:00
hatchjujugui call now15:01
rick_h_jcsackett: ^ antdillon 15:04
backadams54: thanks for your help doing the QA.  please ping me when you're done.15:17
kadams54bac: will do15:17
hatchthe tow truck drivers are driving around and honking the horn in front of peoples cars to get them to move it before they tow it....that's pretty nice15:20
hatchI mean...the big yellow signs have only been here for 5 days....15:20
hatchbut still nice :)15:20
hatchjujugui lf a review/qa for https://github.com/juju/juju-gui/pull/379 plz and thx15:34
frankbanhatch: looking15:36
hatchthanks15:36
hatchjcsackett looking at your screen shots remind me of what internet was like in the 90s :P15:39
jcsacketthatch: yeah; it's something weird with shutter.15:41
jcsacketti get great screenshots, and then the moment shutter does anything with them, they turn into horribly compressed jpegs without any chance of recovering them.15:41
frankbanhatch: when I visit a charm details page and then close the panel, the onboarding is shown. Is that the expected behavior?15:41
jcsacketti haven't figured out what's going on--it didn't used to have this issue.15:41
hatchfrankban if you dismiss it once then that doesn't happen, correct?15:42
frankbanhatch: yes15:42
hatchfrankban tough to say.... luca ^15:42
hatchfrankban I'm pretty confident that that is how it should stay...15:43
frankbanhatch: ok15:43
hatchyou don't want to necessarily miss out on the onboarding just because you clicked a link to view some charm details15:44
hatchat least thats my reasoning15:44
lucahatch: frankban you mean that when you visit Juju for the first time and you’ve been linked to a charm details and you close the details the onboarding shows?15:44
hatchluca no if you click a link to charm details15:45
hatchbut you've never been to juju before15:45
hatchwe show the details w/o the onboarding15:45
hatchbut when you then close those details, we show the onboarding15:45
frankbanluca, hatch: I think you are describing the same path...15:46
hatchoh.....yeah, I read it wrong15:46
frankbanand you are both right15:46
hatchEnglish is hard...15:46
hatchlol15:46
lucahatch: rofl15:47
lucafrankban: hatch that is expected behaviour15:47
hatchhaha yay15:47
frankbancool15:47
frankbanhatch: then QA is good15:47
hatchsweet shippin!15:48
hatchfrankban actually, can you comment on the PR THEN i'll ship :)15:48
hatchthere it is!15:48
frankbanhatch: done15:49
hatchhmm this local inspector business is probably gona be some work15:51
hatchpoo15:51
jcastrohttps://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/131793915:53
_mup_Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>15:53
jcastrocan I get some eyeballs here so we can get this fixed in utopic so we can get it backported to trusty?15:54
rbasakjcastro: I'm your guy. I've been working on this for a while.15:57
rbasakjcastro: there have been process issues getting in the way, and I've been working on resolving them permanently.15:58
rbasakjcastro: right now the blocker is that juju-core ftbfs on utopic on powerpc, and I need this to land in utopic to fix juju-quickstart in utopic, and with that I'll be able to SRU to Trusty.15:58
jcastrorick_h_, <patrick-uds> QUESTION: do you plan to make it possible to deploy a bundle with containing local charms in juju-gui?16:14
jcastrorick_h_, I will ask you during the wrap up16:14
hatchluca do the local charm inspectors also go 100% height in the left column? (thinking so, just want to confirm)16:28
lucahatch: they do16:28
jcsackettjuju-gui: anyone QAing on safari?16:29
hatchluca thanks16:29
hatchjcsackett giver'16:30
jcsacketthatch: huh?16:31
hatchjus' giver' ?16:32
jcsacketti have no idea what you're saying.16:33
jcsackettdialects written in text tend to fail hard. :p16:33
hatchgo hard?16:33
hatchyou can do it?16:33
jcsackettok. thanks.16:33
jcsackett:)16:33
hatchit's all yours16:33
hatchplease sir, may  you do the safari qa16:33
* jcsackett laughs16:34
hatch:D16:34
jcsacketti've never heard "giver'" before...is that "go for it", i'm guessing?16:34
hatchyeah - we say it all the time when doing something stupid16:34
hatch"ok dude giver'"16:34
rick_h_hatch: yea, that's pure canadian nonsense :P16:35
hatchhaha16:35
hatchI looked up the urban dictionary definition....yeah there is some messed up stuff in there16:36
jcsackettjuju-gui: if someone else has safari, can they please open the gui in coming soon and verify that scrollbars on the sidebar work? i'm almost certain this is my machine sucking, but we should double check.16:39
hatchlooking16:39
hatchjcsackett working good here16:40
jcsacketthatch: awesome. well, downside, i can't QA on safari b/c my macbook is *oooold*. plusside, at least the GUI isn't completely hosed on safari. :p16:44
hatchhaha, s'ok we have other osx'rs kadams54 bac frankban rick_h_  :D16:45
jcsacketthatch: if you've deployed an older version of a service, the upgrade section in the inspector should show the newer version, right? i'm not grossly misunderstanding 'upgrade' in this context, am i?16:45
hatchrick_h_ I propose we make a spreadsheet of our supported browsers/platforms and sandbox/real env and then people can put their name beside it when it qa's ok16:46
hatchjcsackett no, atm it now shows every version of the charm (And some which don't exist)16:46
hatchno, you're not misunderstanding it, it's just broken16:47
hatch:)16:47
jcsacketthatch: well, no, it seems to show every older version of the charm.16:47
jcsacketthatch: ok, as long as know that's broken.16:47
hatchyeah there are existing cards16:47
jcsacketthatch: is the upgrade path one then not something we're QAing? b/c there seems to be an inspector left issue in it as well if you actually click upgrade.16:48
hatchhmm.....16:48
jcsackettthough triggering it is hard, since most of the time clicking "upgrade" doesn't seem to do anything.16:48
hatchI'm pretty sure that should still work. But it does list charms which don't exist16:48
hatchso the error may be caused by that16:49
hatchjcsackett it wouldn't hurt to create new bugs though then rick_h_  can go through and mark as duplicates if need be16:50
rick_h_oh sure :P16:50
hatchhaha, well 2 bugs is better than 0 :)16:50
rick_h_hatch: all good, happy to help garden16:50
jcsackettdestroying services leaving machines around is a juju-core issue, right?16:51
rick_h_hatch: I think the spreadsheet thing is something of formalizing the QA process we should do. I'm going to create a task for that. 16:51
hatchcool16:51
rick_h_jcsackett: yes, and there's a branch up for review that changes that16:51
jcsackettrick_h_: cool.16:51
rick_h_hatch: but I think that's a bit much for the moment 16:51
hatchs'ok!16:52
rick_h_ok, UOS session is done and out woot16:52
rick_h_jujugui UOS session if interested https://plus.google.com/116120911388966791792/posts/aLNHXFMW5DC16:54
kadams54UOS?16:55
jcsackettubuntu online summit, i think.16:55
hatchrick_h_ thanks, watching16:56
rick_h_what jcsackett said16:56
rick_h_I'm trying to train myself to not use UDS 16:56
hatchwe need to do a lot better marketing of these things, I only noticed it yesterday haha16:57
jcsacketthatch: i'm making a card in urgent for the upgrade bug i've found; if we decide we don't care for release feel free to alter bug and delete card.16:59
jcsackettok, i need food.17:00
rick_h_jcsackett: ok, make sure you've got reproduction steps please17:00
rick_h_and I also need to find food now. Phew, busy morning17:00
jcsackettrick_h_: yup.17:00
* rick_h_ runs away for a few min17:01
jcsackettrick_h_: i try to never file a bug without reproduction steps if i can avoid it.17:01
* jcsackett runs away in the opposite direction17:01
* rogpeppe1 is done for the day17:02
rogpeppe1g'night all17:02
rick_h_night rogpeppe117:03
rogpeppe1rick_h_: see ya17:03
rick_h_jujugui wife is comandeering the mifi for part of tomorrow for dr home visits...I might be up no-net creek without a paddle. Cannot coffee shop as I have to be here during install17:03
rick_h_gah! imagine a world without internet access! The horror!17:04
hatchlol17:04
rick_h_I'll get someone to be a meeting backup for the cross team call in case I have no net tomorrow17:04
rick_h_anyway, really off to lunch17:04
hatchenjoy17:05
bacrick_h_: where's your real internet?17:14
hatchbac it's being upgraded to add more ips17:15
hatchbusiness line or something17:15
bacoh, yeah, that17:16
baci tune out people with their first-world internet woes17:16
hatchlol17:19
kadams54bac: sent you a PM… going to break for lunch but wanted to chat about some things I was seeing.17:25
backadams54: sorry i was at lunch and didn't see that on my return17:26
kadams54np17:26
backadams54: do you want to do a hangout?17:26
kadams54Sure17:26
backadams54: going into daily standup17:27
kadams54bac: I'm there…17:28
rick_h_bac: :P definitely first world17:28
backadams54: got kicked.  trying again17:29
bacjujugui: i forked the homebrew project into https://github.com/CanonicalJS/homebrew instead of jujugui.  how do i delete the fork?  (i'm sure there is a button i'm just not seeing.)19:01
rick_h_bac: sec, I might be able to move it. 19:02
hatchbac go into the settings for the repo and click delete19:02
hatchyour fork of the repo that is19:02
rick_h_bac: where do you want it to be under? /juju/homebrew?19:02
bacrick_h_: jujugui/homebrew, no?19:03
rick_h_do we have a jujugui user/org? 19:03
bacrick_h_: yes19:03
bacrick_h_: is this not a thing: https://github.com/jujugui19:03
rick_h_bac: ah, that's the bot user. I'd just move it under /juju I think. We don't have any repos there. 19:03
bacrick_h_: ok, that works19:03
rick_h_bac: it's just a dummy user for CI interactions19:04
rick_h_bac: moved19:04
bacthat's not unconfusing19:04
rick_h_https://github.com/juju/homebrew19:04
bacthanks19:04
rick_h_np19:04
bacrick_h_: my branch is juju-quickstart-formula19:06
bacrick_h_: so this would work:19:06
bac#git push git@github.com:juju/homebrew.git juju-quickstart-formula19:06
rick_h_bac: is your branch a fork of that juju/homebrew.git repo?19:07
jcsackettjuju-gui: I have been knocked offline by a storm and my poor phone seems to not be up to the task of hot spotting today. 19:07
jcsackettI go in search of internet elsewhere. 19:07
rick_h_jcsackett: thanks for the heads up19:07
bacrick_h_: i think brew created a branch of the original.  i'm following the directions at https://github.com/Homebrew/homebrew/wiki/Formula-Cookbook after the 'Commit' heading19:08
rick_h_bac: looking19:08
hatchjcsackett darn I JUST needed to have a chat with you too :)19:09
hatchare you ok for ircing?19:09
rick_h_bac: looks ok then19:09
bacrick_h_: i get access denied.  should i be able to push there?19:10
rick_h_bac: hmm, I'd expect you to as you can to the gui, /me checks19:11
bacor my ssh keys are not set up19:11
jcsacketthatch: yeah, i can IRC from my phone, and i'm not in the car yet. what's up?19:11
hatchlocal charm drops use /local in the url and then convert to localType19:12
hatchbut there is an issue with localType being converted to /local19:12
hatchso I CAN fix that19:12
rick_h_bac: updated19:12
hatchbut is there a reason why you picked localType and not local?19:12
hatchI'd really prefer to have a single name instead of a odd rename just for the url19:12
rick_h_bac: they did some gardening now that core is on github. They don't follow our 'let everyone ahve admin' process19:12
bacrick_h_: i had not ssh-add my novel github key19:13
bacnow it worked19:13
rick_h_bac: awesome19:13
jcsacketthatch: I think I was opposed to "local" as a variable name, since that sounds like a bool to me. 19:13
jcsackettBut localType is a crap URL fragment. 19:14
hatchok so are you ok with the rename just for the url?19:14
jcsackettIf you want to s/localType/local I'm good. 19:14
hatchok lemme think about it :)19:15
hatchjust wanted to see if there was some other reason19:15
jcsackettNo good ones, no. :p19:16
hatchhaha ok lemme think about it19:16
pittihello19:16
rick_h_howdy pitti 19:17
pittiso I was watching jcastro's UOS talk today and wanted to try juju-local again (a month or so ago it failed for me due to bug)19:17
rick_h_pitti: very cool19:18
pittiso I'm trying "juju quickstart" as in that tutorial; I get http://paste.ubuntu.com/7630057/ and now it's just hanging, and no running wget or similar19:18
jcastrorick_h_, we're mid session so marco and I can't help right now, but if you could help point him in the right direction that would be <319:18
pittiany idea how I can check what's going on?19:18
rick_h_jcastro: k19:18
rick_h_pitti: what version of ubuntu are you on?19:18
pittino container was created, and strace on the jujud bootstrap is just futex-waiting19:19
pittirick_h_: utopic du jour19:19
rick_h_pitti: oh, bleeding edge. We're aware of some juju/quickstart bugs that we're working on getting landed. https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/131793919:20
_mup_Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>19:20
rick_h_pitti: and if you look in the comment there's a bug in getting juju updated in utopic holding that up right now19:20
pittirick_h_: right, exactly that bug19:20
rick_h_pitti: so I'm not sure it will work properly19:20
rick_h_pitti: we're hoping juju gets updated soon and we can get our quickstart package updated and get it going19:21
rick_h_pitti: you can try the quickstart beta ppa19:21
rick_h_https://launchpad.net/~juju-gui/+archive/quickstart-beta19:21
pittirick_h_: ack, thanks! so I didn't just screw up :)19:21
rick_h_that can get you the pending release ahead of time19:21
rick_h_pitti: no, I don't think so19:21
pittiI mean, not that there's a whole lot to screw up on a single command :)19:21
rick_h_pitti: I think you're smacking into the stuff we're all trying to get fixed up19:21
rick_h_lucky luck you :)19:21
* pitti installs the PPA19:22
rick_h_pitti: note that I'm not sure it'll help you as the juju bug is still there, but I don't recall if that worked around the bug but our release is blocked19:22
pittirick_h_: for testing I'd be ok to create trusty containers; I hope that's what the LXC bug is about? (container release, not host release)19:23
rick_h_pitti: I know the original issue was trusty containers, but the relaese is blocked on utopic builds. series series everywhere. 19:24
rick_h_but the beta package should get you around the original precise container issue19:24
bacrick_h_: the brew pull request has been submitted.  that project has 33 pull requests pending, dating back one week.  so i'm going to declare victory on my card, create a tracking card, and be done.19:24
pittistill hanging :/ and nothing in .juju/local/log/19:24
rick_h_bac: sounds good19:24
rick_h_pitti: :(19:25
pittirick_h_: I suppose I'll re-try my luck with juju bootstrap etc.19:25
pittiI'm mostly interested in this for working on the CI airline wrt. autopkgtest, so trusty containers are totally fine for me19:25
rick_h_pitti: let me know if that works for you. My understanding is that it's a juju/utopic issue. The bug linked in https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1317939 leads through a few other bugs in juju. 19:26
_mup_Bug #1317939: New upstream release 1.3.2 is available <upgrade-software-version> <juju-quickstart (Ubuntu):Triaged> <https://launchpad.net/bugs/1317939>19:26
rick_h_pitti: so quickstart shouldn't be causing any issues19:27
rick_h_pitti: but definitely adding a card to our board to look at qa'ing what we do have under utopic, none of us have upgraded and checked it out yet19:27
pittirick_h_: ah; I usually upgrade on day 1, dogfooding :)19:27
rick_h_pitti: <3 just sorry for the complications you hit. 19:28
pittirick_h_: but I didn't see any log file etc. in .juju to see what's going on; hence my thought to call bootstrap directly, that might be a little more verbose?19:28
pittirick_h_: no worries :)19:28
rick_h_pitti: --debug19:28
rick_h_pitti: I think that turns on verbose bootstraping19:28
pittirick_h_: how would I manually bootstrap a "local" environment?19:28
rick_h_pitti: did you create one using quickstart? 19:29
rick_h_pitti: then just 'juju switch local && juju bootstrap'19:29
pittiah, right, that already creates the yaml19:29
pittihm, endless series of "juju.state open.go:101 connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused" in .juju/local/cloud-init-output.log, and no lxc process or otherwise busy process19:33
pittiso I guess I'll just subscribe to these bugs and wait until they get fixed :)19:33
pittithanks rick_h_ 19:33
rick_h_pitti: yea, that's the juju mongo bug19:33
rick_h_pitti: sorry, I think they're up for the next release next week19:33
pittisounds nice19:33
pittior I'll try it in a trusty VM19:33
rick_h_pitti: +119:34
pittirick_h_: oh, I just saw that juju-local/juju-core 1.18.4 claim to fix much of this, but are stuck in -proposed19:37
rick_h_pitti: right19:37
rick_h_pitti: there's some other blockers 19:38
pittipowerpc build failure apparently19:38
rick_h_pitti: they're working through it but not out yet19:38
pitti*nod*, thanks19:38
* rick_h_ isn't 100% on top of it but watching it to unblock our juju-quickstart release19:38
pittirick_h_: much much better with the proposed version :)19:44
rick_h_pitti: woot19:44
rick_h_jujugui approval for july 21 set, will have details and such tomorrow but feel free to start planning 19:44
pittijuju quickstart still defaults to building stuff for precise, but *shrug*, details :)19:45
pittiand it now fails with juju-quickstart: error: machine 1 is in an error state: error: open /var/lib/lxc/martin-local-machine-1/config: no such file or directory19:46
rick_h_pitti: well it uses your env for the default env19:46
rick_h_bah that came out wrong19:46
pittiso we have some hardcoded /var/lib/lxc/ somewhere (I have them in /scratch/lxc), but that's now much easier to tackle19:46
rick_h_the default series is defined in your environments.yaml19:46
rick_h_pitti: orly that one is interesting19:46
pittirick_h_: right, I wiped .juju and restarted quickstart, that wrote a new yaml19:46
rick_h_pitti: ah, and that yaml uses lts as default series 19:47
rick_h_ok, I'm out for the day all. I'll do my best to be available online tomorrow as much as I can. 19:49
pittifiled as bug 132904919:51
_mup_Bug #1329049: quickstart fails, hardcodes /var/lib/lxc/ somewhere <amd64> <apport-bug> <utopic> <juju-quickstart (Ubuntu):New> <https://launchpad.net/bugs/1329049>19:51
pittirick_h_: good night!19:51
hatchrick_h_ so I'm going to split this bug into two cards, one for the styling and one for the technical bugs19:58
hatchI've fixed the technical bugs but the styling still needs work19:58
hatchhuw can then do that one19:59
bacrick_h_: i'm having troubles with the builds for the PPA.  it is clinging to the 1.3.4.b1 name, not recognizing 1.3.4 is more current.  may have to bump to 1.3.5 if i cannot get it to update.  feels like i'm missing something.20:11
rick_h_bac: oh hmm, I know pypi should treat the b1, guess that might not work in debian packaging world20:12
bacyeah, pypi definitely did, requiring the --pre install flag20:12
rick_h_bac: honestly, if 1.3.5 works call it. I think I might have led your wrong on that sorry20:12
bacnp20:12
hatchjujugui I need a review/qa for https://github.com/juju/juju-gui/pull/380 before Huw starts so he can take on the second part of this card.20:34
kadams54hatch: I can take a look20:34
hatchahh crap I need to remove a comment20:34
hatchsec20:34
hatchkadams54 ok it's ready now20:35
hatchthanks20:35
kadams54yup20:35
hatchjujugui does anyone have a real env up?20:39
=== jcsackett_ is now known as jcsackett
hatchrick_h_ I think that we can push the other ticket from jcsackett20:48
hatchthe upgrade one20:48
hatchoh CI, go home, you're drunk20:57
jcsacketthatch: +1, upgrade is already hella broken.20:58
hatchjcsackett cool, moving it out of urgent20:58
kadams54hatch: what exactly should be fixed in this PR? I'm still seeing the empty sidebar after deploying the local charm.20:58
hatchyou sure you have cleared your cache?20:58
hatchany errors in the console?20:58
kadams54OK, caching issue20:59
kadams54Now the only problem is the squashed inspector, which I take it is what Huw will be fixing.20:59
hatchwell it's just not 100% height21:00
hatchit's no longer squashed21:00
kadams54True21:00
hatchit WAS way squashed :)21:00
kadams54Alright, looks ready to ship, commented as such in the PR.21:00
hatchcool - I'm going to wait for CI to pass 21:01
kadams54Assuming the build gets straightened out21:01
hatchit passes fine here21:01
hatchso hoping it's just being it stupid self21:01
kadams54EOD for me21:20
kadams54See everyone later21:20
hatchlata21:20
hatchrick_h_ anything you want me to start on before release?21:27
rick_h_hatch: can you QA/check out jcsackett's branch?21:29
rick_h_hatch: and any idea on kyle/huw's branch in review? I'm guessing he didn't get that updated due to the qa/etc work today21:29
hatchoh look at that21:29
hatchfor sure21:30
hatchI THINK that one has landed21:30
hatch....21:30
hatchhe has nothing in the PR queue21:30
rick_h_hatch: oh hmm ok coolio then21:30
jcastrohey fellas21:36
jcastrowrt. "we should export bundle.yaml"21:36
rick_h_jcastro: disagree?21:37
jcastroyeah21:37
jcastrobut it's only step 121:37
jcastroI wonder if there's a bug for21:37
jcastro"envExport" 21:37
jcastrolike, ideally21:37
rick_h_yes, there's a bug to allow the user to select a name on export21:37
jcastroI would click the button to export, and it would ask me "name this bundle"21:37
jcastroand then it would use that21:37
jcastroAND bundle.yaml21:37
rick_h_but this is just a drive by for the filename part21:37
jcastrorick_h_, excellent, <321:37
hatchjcastro I saw you signed up for keybase21:38
jcastroyessir21:38
hatchhttps://keybase.io/hatch21:38
jcastroI need to figure out how to sign my new key with my old one21:38
hatchI'm trying to find a use for this21:39
hatchlol21:39
rick_h_lol21:39
hatchI uploaded the generated private key so I can do in browser decrypting21:39
jcastrogpg pokemon21:39
jcastrohah no you didn't21:39
jcastroyou fell for that?21:39
hatchwithout doing that, what's the point in the service?21:39
hatchif you must have your computer then why do this at all21:39
jcastrothe CLI is much nicer than gpg21:40
jcastroit's like, easy to use21:40
hatchwell ok theres that21:41
hatchbut yeah, if I ever come up with a real use for it then maybe I'll gen another key and not push it up21:41
hatchI don't use the key I pushed up for anything21:41
hatchmaybe I just don't encrypt enough stuff lol21:42
hatchok now I need another task... hmm21:43
jcastroyeah, pokemon21:43
hatchlol what21:44
jcastrocollecting signatures, it's like pokemon21:47
hatchohhh21:49
hatchpokekey21:49
jcsacketthatch: don't think i was online when i pinged you about this: looking at reload in service-inspector.js i see this https://pastebin.canonical.com/111543/21:49
jcsackettlooks like a bit of flags.il leftover?21:50
hatch2 secs need 2fa21:50
jcsackettkk.21:50
hatchjcsackett yep looks like that should have been switched over21:52
hatchalthough, I am wondering why I get it auto-reloaded21:52
jcsacketthatch: my power blew out, so I'm EoDing. Let's look at it tomorrow. 21:56
hatchyeah no problem - it's pretty low on the priorty list :)21:56
hatchenjoy lack of power21:57
jcsackettThanks. :p21:58
huwshimiMorning23:00
hatchhey huwshimi 23:01
hatchI gots works fors yous23:01
huwshimihatch: Hey23:01
huwshimihatch: I saw that card23:01
hatchcool, so it's the last one blocking release 23:01
hatchI wasn't sure if you're familiar with how those inspectors are rendered so I figured I'd stick around23:01
huwshimiah :)23:01
huwshimihatch: I just need a local charm right?23:01
hatchyeah you can download the zip from my ghost charm one23:02
hatchhttps://github.com/hatched/ghost-charm23:02
hatchthe big Download Zip button on the right23:02
huwshimihatch: Ah yes, got it working23:03
huwshimihatch: Anything else I need to take a look at?23:03
hatchhttps://github.com/juju/juju-gui/blob/master/app%2Fviews%2Finspectors%2Flocal-new-upgrade.js23:03
hatchhttps://github.com/juju/juju-gui/blob/master/app%2Fviews%2Finspectors%2Frequest-series.js23:03
hatchthose are the two inspectors which need updating23:04
huwshimiAh ok23:04
hatchI don't think so, maybe just do a once over, see if you can break it in any other way23:04
huwshimiok :)23:04
huwshimihatch: Aiming for release tomorrow?23:08
hatchunless we find some huge blocker :)23:08
hatchbut so far so good23:08
huwshimiyay!23:11
huwshimihatch: This is the problem with doing so much between releases :)23:13
hatchyeah yeah23:14
huwshimihehe23:15
huwshimiJust changing locations, back in a minute.23:21
hatchhuwshimi I'm going to take off for a couple hours - but I'll be back later if you run into any issues with the js portion of the local charm inspectors23:47
huwshimihatch: Yep, np23:47

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!