[09:16] <frankban> morning hatch and Makyo: welcome to the "European" timezone ;-). did you have a nice trip?
[09:17] <hatch> :) It's soooo amazing!
[09:17] <Makyo> Hahaha
[09:17] <Makyo> It was okay.  Minus sliding off the highway on Saturday, and the fire alarm last night.
[09:17] <frankban> :-)
[09:17] <hatch> everyone here says router wrong :P
[09:17] <frankban> lol
[09:18] <hatch> frankban you should drive up for supper
[09:18] <hatch> take one of those high speed trains I hear so much about :D
[09:23] <frankban> hatch: heh, I am not in my best shape to do that. but if you want to experience one of those, we can have dinner together in Tuscany, I promise good food and a warm 10/12C temperature
[09:23] <hatch> haha, I'd love too but I think I'd have to skip work on Friday
[10:39] <jab> http://docs.openstack.org/havana/install-guide/install/apt/content/ch_overview.html
[12:25] <bac> good morning frankban
[12:26] <frankban> hi bac
[12:33]  * rick_h_ crosses fingers that the power and gas companies keep up. Poor furnace is running non-stop
[12:33] <rick_h_> -14F / -25.5C this morning wheeee
[12:36] <rick_h_> hah, "feels like -36F, -37C" they're almost even at this point.
[12:49] <bac> rick_h_: a few more degrees and C/F meet!
[12:50] <bac> well, wind chill at least
[12:51] <bac> rick_h_: i should probably not point out the perceived temp here is 120F warmer than yours.  seems not right.
[12:53] <rick_h_> jujugui afk, wife's car won't start and I can't get into mine atm. Working on it for a few.
[12:54]  * benji redirects the microwave satalites to warm up rick_h_'s driveway.
[12:59] <rick_h_> phew! keyfob on the touareg wouldn't work and had to call dealer to find out how to get in via key
[12:59] <rick_h_> man that diesel wasn't happy to start but it did
[12:59] <rick_h_> so will be driving family into work/day care in a bit. then back to regular scheduled hacking
[12:59] <rick_h_> the subaru doesn't want to start
[13:20] <gary_poster> welcome back frankban. :-) Should I review the improve-field-choices branch?
[13:22]  * gary_poster assuming yes
[13:22] <frankban> thank you gary_poster :-) yes please thanks!
[13:22] <gary_poster> cool :-)
[14:01] <rick_h_> bah bah bah, I can't believe hatch lives in this stuff
[14:03] <bac> :)
[14:04] <gary_poster> frankban: qa done, but call now
[14:04] <frankban> gary_poster: thanks, looking
[14:04] <gary_poster> happy for you to get someone else
[14:07] <frankban> gary_poster: ok, so the default series if not specified is "precise". did not know that, thanks for that good point. I have to change the approach, and I will work on your QA notes.
[14:47] <hatch_> jujugui is comingsoon not updating?
[14:48] <bac> hatch: staging.jujucharms.com is currently not ingesting new charms.  would that affect what you see?
[14:48] <rick_h_> hatch: it was setup to at some point, did the cron job get turned on bac? Or maybe a conflict/issue?
[14:48] <bac> hatch: nm
[14:48] <bac> hatch, rick_h_: i'll look into it
[14:49] <hatch> bac thanks, we just noticed when trying to demo something landed last week
[14:51] <bac> rick_h_: git is not updating that branch.
[15:04] <bac> jujugui: comingsoon should be updated now.  i did it manually as the cronjob isn't working due to git/bzr differences.
[15:04] <hatch> bac thanks
[15:04] <hatch> guess that should probably be a high card?
[15:04] <bac> hatch: can you verify?
[15:04] <hatch> checking
[15:04] <bac> hatch: working on it
[15:04] <rick_h_> bac: :( now we can't verify it will work
[15:04] <rick_h_> until the next commit/landing
[15:05] <bac> rick_h_: well go commit something!  :)
[15:05] <hatch> not the latest commit
[15:05] <Makyo> http://comingsoon.jujucharms.com/juju-ui/version.js
[15:05] <Makyo> 7690c76 vs 3366a0995f155b845de49ccda0f58c7cf01e6d89
[15:11] <Makyo> 7690c76 doesn't appear to be real :P
[15:11]  * bac looking
[15:11] <rick_h_> Makyo: yea, that's interesting
[15:12] <rick_h_> Makyo: but there's a commit in a branch on comingsoon to tweak the config
[15:12] <Makyo> Oh, okay, cool
[15:12] <rick_h_> Makyo: I think it's that commit hash and the rest of us don't have it, it's only on that local checkout
[15:12] <hatch> maybe it was blown away in a force push
[15:12] <Makyo> Ohhh, right
[15:12] <bac> rick_h_, Makyo: here is 'git log' http://paste.ubuntu.com/6709529/
[15:13] <bac> yes, to what rick_h_ said about local checkout
[15:13] <rick_h_> ok, that looks good
[15:13] <hatch> ohh you're not pulling and updating
[15:13] <hatch> maybe that needs to be changed
[15:13] <rick_h_> hatch: well we need a config changed
[15:13] <hatch> oh right
[15:13] <rick_h_> you can't pull with un-committed changes
[15:14] <rick_h_> hatch: so we had to create a special branch and then do merges from the remote develop into it, and not the local develop
[15:14] <hatch> shelve it and re apply?
[15:14] <rick_h_> but why if this works?
[15:14]  * rick_h_ has done that in the past
[15:14] <hatch> right but this case we dont have the actual version hash
[15:14] <hatch> what if we copied the 'real' hash
[15:14] <rick_h_> hatch: we will
[15:15] <hatch> and set that in the version.js
[15:15] <benji> rick_h_: this code from the juju-sync alias doesn't appear to work: git pull juju develop
[15:15] <rick_h_> hatch: it's just that this is the last commit
[15:15] <rick_h_> hatch: after this change, the last commit will be the develop hash
[15:15] <benji> I get this error: fatal: 'juju' does not appear to be a git repository
[15:15] <benji> fatal: Could not read from remote repository.
[15:15] <rick_h_> benji: then the remote isn't setup?
[15:15] <hatch> that sounds like it could be
[15:15] <Makyo> benji: git remote -v; is juju set up as a remote?
[15:15] <hatch> or the remote is called something else
[15:15] <hatch> that ^
[15:16] <rick_h_> hatch: anyway, this hash issue is a one time deal while we added that extra commit to change the config settings for comingsoon
[15:16] <rick_h_> hatch: if it doens't update on the next landing we'll look into it I guess.
[15:16] <hatch> ahhh gotcha
[15:16] <benji> Makyo and rick_h_: ok, I got the remote set up and the "git pull juju develop" "worked":
[15:16] <benji> remote: Counting objects: 28, done.
[15:16] <rick_h_> benji: git remote add juju git@github.com:juju/juju-gui.git
[15:16] <benji> remote: Compressing objects: 100% (27/27), done.
[15:17] <benji> remote: Total 28 (delta 5), reused 24 (delta 1)
[15:17] <benji> Unpacking objects: 100% (28/28), done.
[15:17] <benji> From github.com:juju/juju-gui
[15:17] <benji>  * branch            develop    -> FETCH_HEAD
[15:17] <benji> Updating 5e4951a..3366a09
[15:17] <benji> error: Your local changes to the following files would be overwritten by merge:
[15:17] <benji>         HACKING.rst
[15:17] <benji> Please, commit your changes or stash them before you can merge.
[15:17] <benji> Aborting
[15:17] <benji> (excuse the flood)
[15:17] <rick_h_> benji: you have to have a clean working tree
[15:17] <rick_h_> benji: stash (shelve) or commit your changes
[15:17] <rick_h_> benji: git won't let you mess around with doing merges/etc with unclean trees
[15:18] <rick_h_> git stash && git pull juju develop && git stash pop
[15:18] <rick_h_> should get you back to where you are with updated develop
[15:18] <rick_h_> but why are you working on develop anyway?
[15:18] <benji> ok, I think I understand git a little better now, switching to a different branch doesn't touch currently modified files
[15:18]  * rick_h_ is confused
[15:18] <benji> hence the "stash" bit
[15:19] <benji> rick_h_: I am trying to update my github fork of develop because when trying to create a pull request I have lots of diffs that aren't real because my develop is behind the true develop
[15:19] <rick_h_> benji: never work on develop. always feature branch
[15:19] <rick_h_> develop is a read-only branch
[15:20] <benji> rick_h_: I'm not; I'm not communicating well
[15:20] <rick_h_> per the workflow int he hacking docs
[15:20] <rick_h_> benji: k, sorry.
[15:20] <rick_h_> benji: hangout?
[15:20] <benji> rick_h_: I think I've figured it out.  If not, I'll take you up on the offer later.
[15:20] <rick_h_> benji: rgr
[15:21] <rick_h_> hatch: so is your demo feature now up on comingsoon?
[15:21] <hatch> I'll check
[15:22] <hatch> rick_h_ yep but the styles are off
[15:22] <hatch> looking
[15:22] <rick_h_> hatch: bah, do we still have make issues around the css?
[15:22] <gary_poster> yes
[15:22] <gary_poster> make clean
[15:22] <rick_h_> bac: still in to do a clean/update?
[15:22] <rick_h_> please
[15:22] <hatch> ahh ok
[15:23] <bac> rick_h_: ok
[15:23] <hatch> ok well cool thanks for getting that back up
[15:23] <rick_h_> hatch: thanks for noticing :)
[15:24] <benji> rick_h_: ok, I'm back :)  I have (I think) updated my copy of develop but this comparison still has too much stuff in it: https://github.com/juju/juju-gui/compare/add-floobits-vim-instructions...develop
[15:25] <bac> hatch: try now
[15:26] <hatch> tying
[15:27] <Makyo> Yeah, it's working.
[15:27] <Makyo> hatch: is digging for change.
[15:27] <hatch> lol
[15:28] <hatch> the charmbrowser opening animation is super jumpy now
[15:28] <hatch> wonder what's up with that
[15:29] <hatch> benji you pushed a new branch to the juju juju-gui branch instead of your own fork
[15:31] <benji> hatch: that makes sense, let me see if I can address that
[15:31] <rick_h_> benji: looking
[15:33] <rick_h_> benji: yea, always push to the origin
[15:33] <benji> rick_h_: if only those words meant anything to me
[15:33] <rick_h_> benji: if you use the 'git juju-sync' you should never use juju itself
[15:33] <rick_h_> benji: :)
[15:35] <rick_h_> benji: https://github.com/juju/juju-gui/blob/develop/HACKING.rst#typical-github-workflow
[15:35] <benji> rick_h_: that's what I am following
[15:35] <benji> (incorrectly, apparently)
[15:35] <rick_h_> benji: git push origin :{featureBranchName}
[15:36] <rick_h_> hmm, why the : there, /me goes to remove it
[15:36] <benji> I was wondering
[15:36] <benji> rick_h_: that's what I did.  If I do it again I get: Everything up-to-date
[15:36] <hatch> :)
[15:37] <rick_h_> benji: then your origin is off and not your fork on github but the original juju one.
[15:37] <rick_h_> benji: so will need to tweak things
[15:44] <benji> rick_h_: thanks for the help, I got it working
[15:44] <rick_h_> benji: rgr
[15:45] <rick_h_> benji: please let me know if there's anything in the hacking doc I can update that threw you off
[15:46] <hatch> rick_h_ change it to use bzr :P
[15:46] <benji> rick_h_: I think the problem was that I threw away and re-checked-out the other day and I bet I checked out the "real" repo instead of my fork
[15:46] <rick_h_> benji: ok yea, the 'real' one is read only and touched only by the lander tool
[15:47] <hatch> oh thats good to know
[15:47] <hatch> I thought that we were able to push into it by accident
[15:47] <rick_h_> hatch: you can...but the intention is that it's read-only and you never touch it :)
[15:47] <hatch> ohh I see haha
[15:47] <hatch> can it be restricted to user?
[15:47] <rick_h_> not without preventing you access to other things
[15:47] <hatch> I know git allows you to set permissions but I'm not sure aobut github
[15:47] <rick_h_> github doesn't have fine grained ACLs
[15:48] <benji> jujugui: quick docs review, especially interesting to Vim users: https://github.com/juju/juju-gui/pull/48
[15:48] <rick_h_> benji: looking
[15:51] <gary_poster> jujugui call in 9
[15:51] <gary_poster> frankban: trying to do end of review now
[15:53] <frankban> gary_poster: oh, re-proposing now with some fixes
[15:54] <gary_poster> frankban: oh ok cool, no comments so far so will just switch over when you have finished
[15:56] <frankban> gary_poster: changed the default-series behavior. the only missing bit is the choices line wraps: it seems not supported by the urwid.Columns widget. so maybe I can do some ugly thing like putting a maximum of three choices per line :-/
[15:56] <gary_poster> frankban: ack, thanks, and :-/
[15:56] <gary_poster> :-)
[15:58] <gary_poster> jujugui call in 2
[15:59] <gary_poster> hangouts are having issues it seems
[15:59] <rick_h_> got in here
[16:00] <gary_poster> rick_h_: I can sopmetimes get video of myself, but then "It's taking too long to connect you to this video call. Try again in a few minutes."
[16:00] <rick_h_> gary_poster: benji got in, but not hearing anything
[16:00] <gary_poster> Other times it is just a 500 error
[16:01] <rick_h_> oops, he ran out
[16:01] <gary_poster> huh
[16:02] <bac> jujugu: it shows i'm joining with gary and benji but then it puts me in solitare
[16:02] <bac> s/solitare/solitary/
[16:03] <Makyo> Hm, at least it's not just me.
[16:03]  * bac tries phone
[16:03] <Makyo> People in canonical are having problems, too.
[16:09] <bac> gary_poster: can you paste that link here?  (no chat on phone)
[16:29] <gary_poster> frankban: code LGTM, with no suggestions
[16:30] <frankban> gary_poster: thanks! do you have time (now or later) for a quick call?
[16:31] <gary_poster> frankban: can do now, sure
[16:31] <gary_poster> frankban: you making or shall I?
[16:31] <frankban> gary_poster: making
[16:31] <gary_poster> k
[16:31] <benji> rick_h_: I merged wrong, I used the button instead of saying :shipit:.  Is there something I need to do to correct the mistake?
[16:32] <rick_h_> benji: too late
[16:32] <rick_h_> benji: just let it lie
[16:32] <frankban> gary_poster: https://plus.google.com/hangouts/_/72cpjudfrn0nutn1sjf7pg71cc?hl=en
[16:32] <benji> ok.  I wish there were a way to remove that attractive nusance
[16:32] <rick_h_> benji: +1, but nothing to do but learn to ignore it
[16:33] <rick_h_> benji: could custom css using tools to remove hte button if you're concnered about hitting it again
[16:33] <benji> rick_h_: I was thinking the same thing
[16:36] <gary_poster> frankban: having difficulty joining.  retrying repeatedly while trying to google issue
[16:36] <frankban> gary_poster: hangout seems very broken
[16:51] <rick_h_> benji: I removed the extra branch on the main juju repository. To do it, I clone'd it into a temp dir and did a `git push origin :add-floobits-vim-instructions` to remove it.
[16:52] <benji> rick_h_: thanks much
[16:54] <rick_h_> gary_poster: signed up under username 'mitechie'
[16:54] <rick_h_> gary_poster: re: floobits
[16:55] <gary_poster> rick_h_: awesome, you are all set up
[17:00] <benji> doh!  gary_poster, you noticed my typo after the branch landed.  I'll spin up a new branch. :)
[17:02] <Makyo> gary_poster: user makyo
[17:04] <benji> gary_poster: my Floobits user name is "benji"
[17:04] <hatch> email sent with details
[17:37] <benji> rick_h_: is http://ci.jujugui.org unwell?
[17:39] <Makyo> Too cold to ci.
[17:40]  * Makyo calls it.  hatch can be the last one in the office.
[17:58] <rick_h_> benji: looking
[17:59] <rick_h_> benji: seems fine here http://ci.jujugui.org:8080/
[17:59] <rick_h_> benji: see https://github.com/juju/juju-gui/blob/develop/docs/continuous-integration.rst recently updated with all the info and links
[17:59] <benji> rick_h_: oh, I forgot the non-standard port number
[18:00] <rick_h_> benji: and all the emails should contain valid links directly to your pull request test run and such
[18:02] <rick_h_> jujugui afk, verified the wife's car battery is done for due to cold (could jump it at lunch but not holding a charge) so off to get a new one before the stores are all out.
[18:27] <rick_h_> and yay last one for her size
[18:29]  * hatch is confused
[18:29] <hatch> :)
[18:30] <hatch> oh linter and d3 code
[18:30] <hatch> it's like a game to try and figure out what it will accept
[18:30] <rick_h_> hatch: hah, battery on the wife's subie died in this -40C wind chilll
[18:30] <rick_h_> hatch: hah, it tells you where it expects it to be
[18:30] <rick_h_> just pick one of the numbers it lists
[18:30] <hatch> right, but when I'm writing it I mean
[18:31] <hatch> and yeah batteries don't like it when it's that cold :)
[18:31] <rick_h_> oh don't bother, it's like the refactor step
[18:31] <hatch> especially without a battery blanket and block header
[18:31] <hatch> heater*
[18:31] <hatch> lol
[18:31] <rick_h_> heh, yea nothing is liking this. We don't have battery blankets and engine heaters because it's not NORMAL here
[18:32] <rick_h_> the diesel starting up this morning was just painful, poor girl normally likes to purr at me. Was rough today
[18:32] <hatch> haha yup, you can take the battery inside then install it when you need to go out :D
[18:32] <hatch> lol wow the diesel probably was knocking
[18:33] <bac> rick_h_, benji: can either of you look at https://codereview.appspot.com/48540043
[18:33] <bac>  please?
[18:33] <rick_h_> bac: sure thing
[18:41] <bac> rick_h_: a companion fix to the charmworld charm is only a few lines but needs review if you have time https://code.launchpad.net/~bac/charms/precise/charmworld/fix-logging/+merge/200714
[18:42] <rick_h_> bac: rgr
[18:43] <rick_h_> bac: qa will take a few. I've got to setup my charmworld lxc again as it was blown away during my trusty upgrade
[18:44] <bac> rick_h_: np.  it'll take about 15 minutes to run
[18:46]  * rick_h_ needs to create an lxc container template with build-essential and such installed
[19:01] <rick_h_> bac: the charm branch is ok. Should it be a little bit under the cron job? /me isn't sure how they'll interact
[19:01] <bac> rick_h_: cronjob is kaput
[19:01] <rick_h_> bac: ah, nvm then
[19:01] <bac> rick_h_: all run here
[19:01]  * rick_h_ missed that
[19:02] <bac> rick_h_: it now queues and ingests in one pass
[19:02] <rick_h_> bac: k, so this isn't cron'd or the cron just runs this?
[19:03] <bac> rick_h_: it is run by supervisord with --run-forever and the sleep at the end of the cycle
[19:03] <bac> be default the interval is set to 15 minutes (or will be when the charm branch lands)
[19:03] <bac> s/be/by/
[19:03] <rick_h_> bac: cool
[19:04] <bac> rick_h_: seems a lot simpler.  we did give up the ability to split queue and ingest across machines.
[19:04] <rick_h_> bac: yea, that was an original requirement, but I think we've passed that
[19:04] <rick_h_> we've got to worry about ES and mongo long before splitting the other stuff
[19:21] <rick_h_> bac: qa running now, sorry for the delay. /me needs to remember to create lxc containers on older releases and not trusty
[19:22] <bac> rick_h_: np
[19:22] <gary_poster> benji Floobits vim card can be moved, yeah?  Are you working on removing the fullscreen flag from charm?
[19:22] <benji> gary_poster: yes to both; I'll usher the cards to their new homes
[19:22] <gary_poster> thank you
[19:23] <benji> gary_poster: refresh your board, I already moved them
[19:23] <gary_poster> ah cool thanks benji, sorry for noise
[19:24] <benji> np
[19:34] <rick_h_> bac: qa ok, so only comment is the s/charmworld/charm
[19:37] <bac> rick_h_: i changed the qualname to 'charm' to match what the code was already using
[19:38] <rick_h_> bac: ah ok. usually it's the name of hte app in pyramid practice but if that's what the code's using it's not the most evil thing
[19:39] <bac> rick_h_: since the logger name is on every line i guess whoever did it originally thought 'charmworld.worker' took up too much space
[19:39] <rick_h_> bac: rgr
[19:52] <bac> rick_h_: could you mark it LGTM?
[19:53] <rick_h_> bac: sorry, thought I did. /me goes back to it
[19:53] <bac> thanks
[19:54] <bac> rick_h_: you got close but it wasn't green and i was unsure what 'bzr rv-submit' would do
[19:54] <rick_h_> bac: right, I said qa ok, but not a firm LGTM
[19:54] <rick_h_> corrected
[19:55] <rick_h_> cool new github feature today: traffic https://github.com/juju/juju-gui/graphs/traffic
[19:57] <gary_poster> that is cool
[19:58] <rick_h_> https://github.com/blog/1672-introducing-github-traffic-analytics for announcement
[20:28] <bac> hey benji, we've got one persistenly queued basket on production and staging.  http://manage.jujucharms.com/heartbeat
[20:29] <benji> bac: maybe now is the time to figure out why that happens (or maybe not) :)
[20:29] <bac> benji: but...but...i thought you figured it out a few weeks ago. was that just a special case?
[20:30] <benji> bac: not quite: I thought the problem I was debugging was cuased by a stuck basket, but it wasn't, it was incidental
[20:31] <bac> oic
[22:01] <huwshimi> Morning


[18:32] <arraybolt3> @tsimonq2: Is there any info I don't already have for discussing how to proceed with the lubuntu-update-notifier fix with those who need to be involved? You were saying that you thought we should contact the Technical Board, I'm not sure what the best way to do that is (email?).
[19:22] <arraybolt3> @tsimonq2: Could also use your help here: https://salsa.debian.org/lxqt-team/liblxqt/-/merge_requests/5
[19:22] -ubot93:#lubuntu-devel- Merge 5 in lxqt-team/liblxqt "Releasing debian version 1.2.0-5." [Opened]
[19:23] <arraybolt3> (Not to merge, but to back up the symbols file - ChangZhuo apparently isn't convinced by my logic there)