/srv/irclogs.ubuntu.com/2015/02/06/#juju-dev.txt

=== kadams54 is now known as kadams54-away
mattywmorning folks, I get the following error in the tip of juju/errors - is it just me or can someone else see it?05:43
mattyw^^ not gccgo05:43
anastasiamacmattyw: what error?05:44
mattywanastasiamac, ah - dammit - sorry forgot to past the paste :/05:44
mattywanastasiamac, http://paste.ubuntu.com/10085832/05:44
mattywanastasiamac, sorry - it's still early (1:44pm)05:44
anastasiamacmattyw: m running with juju/errors that juju/juju depended on yesterday05:48
anastasiamacmattyw: and get05:48
anastasiamacmattyw: ok      github.com/juju/errors  0.008s05:48
mattywanastasiamac, what version of go?05:49
mattywanastasiamac, (starting to clutch at straws now :) )05:49
anastasiamacmattyw: go version go1.2.1 linux/amd6405:50
mattywanastasiamac, ok - I might try running an earlier version and see what happens, it's not blocking me,  just an observation05:51
mattywI'll keep an eye on it though05:51
anastasiamac:D05:51
mattywdavecheney, done https://github.com/juju/errors/pull/1609:41
axwdimitern: nice logo :)10:08
dimiternaxw, :) it took 15m10:08
dimiternaxw, yeah I think goose deserves a logo now heh10:08
axwkatco: FYI, https://github.com/go-goose/goose10:10
axwdimitern: katco has some Cinder support in the works10:10
axwdimitern: and what she's doing is auto-generating bindings off WADL provided by OpenStack. may be useful to use more generally10:11
dimiternaxw, oh, ok - I'll sync up with her next week then10:13
dimiternmy current plan is to just migrate existing trunk to GH and change imports to use gopkg.in10:13
dimiternaxw, katco ^^10:18
axwdimitern: no worries, that's what I expected10:18
dimiternaxw, ok, cheers10:19
dimiternwe'll use gated merges as well with the bot like for juju/juju10:19
axwdimitern: not using Travis?10:20
dimiternaxw, nope, I really don't want to, if it can be avoided10:24
axwokey dokey10:24
dimiternaxw, our merge bot does a more consistent job I think10:24
dimitern(a bit of handwavyiness here ofc.. :)10:25
axwdimitern: I'm happy with that, was just wondering if this would be handled the same as go-amz10:25
dimiternaxw, I got bashed a bit for taking this decision frankly (travis over our bot) and want to do it "properly" this time :)10:30
axwdimitern: I see :)10:30
frankbandimitern: morning, I was looking at this regression we have on the GUI: bug 141843312:00
mupBug #1418433: unit information pane lost port information <juju-gui:Triaged> <https://launchpad.net/bugs/1418433>12:00
frankbandimitern: it seems that newer versions of juju-core no longer populate the unit ports in the mega-watcher. unitDoc.Ports is also marked as no-longer used, but it's still used by the mega-watcher12:01
frankbandimitern: note that this breaks API backward compatibility12:03
dimiternfrankban, hey, I was afk for a while, reading back12:16
dimiternfrankban, unitDoc.Ports is no longer there (or at least no longer used)12:17
dimiternfrankban, but i'll have a look to recall what should've be used instead12:18
frankbandimitern: it's no longer populated, and assumed to be no longer used, but instead it's still used by the megawatcher for units12:18
frankbandimitern: and therefore it's always empty12:18
frankbandimitern: I guess we should use unit.OpenedPorts(), but that would still be a backward incompatible API change12:19
frankbandimitern: because the ports are now ranges (FromPort/ToPort) while before they were just numbers (Number)12:19
dimiternfrankban, fair point12:20
dimiternfrankban, we should fix this to be wire-format-compatible12:21
dimiternfrankban, but by doing this we'll lose some precision - if from=to port, that's fine, if not - what?12:22
frankbandimitern: we could make the mega-watcher use an ad-hoc function that return a slightly different slice of port ranges, in which we have both the From/To and the Number, in the case From==To12:22
dimiternfrankban, and the gui should definitely use unit.OpenedPorts to get them12:22
dimiternfrankban, I mean .. it should expect port ranges at least12:23
frankbandimitern: the GUI uses the mega-watcher to get them, so we need to modify the mega-watcher to call OpenedPorts, and then maybe modify the result as I described12:23
dimiternfrankban, ah, that's a good idea - adding PortRanges to the MW changes struct for units12:23
frankbandimitern: yes, we need a fix to the GUI too, but introducing a Number in the struct returned by the mega-watcher would make it easy for the GUI to be backward compatible, i.e. if there is a number, use that, otherwise handle the range12:24
dimiternfrankban, so the Ports *can* be wrong, but PortRanges slice won't be12:24
dimiternfrankban, thanks for the heads up, I'll tackle this with priority12:24
frankbandimitern: I can help if you want12:25
dimiternfrankban, I need to have a chat with william first, but I'll get back to you12:26
frankbandimitern: ok thanks12:26
frankbandimitern: anyway, something like this prototype would work, with a subsequent change to the GUI: https://github.com/frankban/juju/compare/restore-megawatcher-unit-ports?expand=112:36
perrito666hi, anyone in for a trivial text only rev https://github.com/juju/testing/pull/50 ?12:41
dimiternfrankban, ok, so I'm filing a bug about it first, then I have a clear plan how to fix it in a backwards compatible way12:41
dimiternperrito666, reviewed12:42
dimiternfrankban, unfortunately what you're suggesting is not sufficient, as it introduces another change into the struct format12:43
perrito666dimitern: tx done12:43
frankbandimitern: I know it's still backward incompatible, but it can be good enough for the GUI, which is your main API consumer12:44
dimiternfrankban, I'd rather have a new PortRanges slice field and revert Ports to how it was, while having a piece of code that converts from=to ranges to ports and drops the rest12:44
frankbandimitern: sounds good, at that point no change is required GUI side12:45
dimiternfrankban, exactly; ok, cheers12:45
frankbandimitern: thanks for looking at that, could you ping when you have a fix?12:46
perrito666dimitern: same thing for utils?12:50
dimiternperrito666, what thing?12:54
perrito666dimitern: If I where a smarter person, I would not have forgotten to paste the link12:55
perrito666https://github.com/juju/utils/pull/11312:55
dimiternperrito666, :)12:55
dimiternperrito666, lgtm12:56
perrito666ta12:56
perrito666lool, did yo see what shows in github when you say :shipit:  ?12:58
dimiternperrito666, I saw but couldn't quite get it13:19
dimiternis it a mob-frog of some sort?13:20
perrito666looks like a squirrel with a hat13:20
perrito666oh is it a frog?13:20
dimiternha, could be :)13:20
dimiternok, gtg - CPT sprint is officially over13:20
perrito666dimitern: cheers13:20
dimiternta ;)13:21
jw4perrito666, dimitern: Ship It Squirrel - added to github - https://github.com/github/hubot-scripts/commit/247310f83e8f0a33230c4a2ceb5e68ca86006e1813:24
perrito666ok, las licencing fix, I promisse http://reviews.vapour.ws/r/889/14:42
hazmatanyone around with mongodb knowledge jujuer on #juju has an interesting bootstrap error http://paste.ubuntu.com/10092884/ please come over there15:45
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== makyo_ is now known as Makyo
perrito666rogpeppe: I didnt parse half of your mail19:07
rogpeppeperrito666: sorry, my fault, i've had beer :)19:08
perrito666I do agree though that we could/should move to gopkg.in yet that does not change the fact that our internal repo should branch when this happens (as I did)19:08
perrito666rogpeppe: I envy you, I had wather only19:08
rogpeppeperrito666: is wather low alcohol?19:08
rogpeppeperrito666: ( :-) )19:09
perrito666dont try wather, is terrible, produces oxidation :p19:09
rogpeppeperrito666: what do you mean by "our internal repo"?19:09
perrito666well, see, when we tag juju for release, lets say 1.2119:10
perrito666we deppend on a set of versions of ilbraries19:10
perrito666that we support ourselves19:10
perrito666like juju/utils or juju/testing19:11
rogpeppeperrito666: ok19:11
perrito666so, as development advances for new versions, these all grow in code but we keep maintaining 1.2119:11
rogpeppeperrito666: ok19:11
perrito666so at some point we will neet to backport a dependency fix to 1.21, say a licence issue19:11
perrito666and there you have two options, you add that fix on top of the dependency and make 1.21 deppend on that, with a subset of unknown/unwanted changes in the dependency19:12
rogpeppeperrito666: is that a problem?19:12
perrito666or, branch the dependency at the point that is used in 1.21 and apply changes there19:12
rogpeppeperrito666: (option 2, that is)19:12
perrito666rogpeppe: exactly that19:12
rogpeppeperrito666: the only time i can think it would be a problem is if the dep hasn't changed in a backwardly compatible way19:13
perrito666that was the case19:14
rogpeppeperrito666: right19:14
rogpeppeperrito666: that's why i'm suggesting the use of gopkg.in19:14
perrito666but if it wherent and the distance is too big, you are adding a lot of unwilling changes to a minor release which is a bit icky19:14
rogpeppeperrito666: i don't think it should be19:15
rogpeppeperrito666: backwardly compatible should be backwardly compatible19:15
rogpeppeperrito666: and maintaining forks is a significant use of time and resources19:15
perrito666well, they are called maintenance branches for something, you just add whatever fix you backport to those or close them :p19:16
* perrito666 ponders having beer to stop mosquitoes from bitting him19:16
* rogpeppe accepts another beer19:17
rogpeppeIPA is dead: citra19:19
rogpeppemmm19:19
* perrito666 settles for mosquito repellent19:20
=== kadams54 is now known as kadams54-away
rogpeppeperrito666: the more branches the more effort and the more likelihood of getting things wrong between branches, in my experience anyway.19:26
perrito666rogpeppe: ¯\_(ツ)_/¯19:27
rogpeppeperrito666: that looks rude to me19:27
* perrito666 suspects that the fonts dont translate the message too well :(19:27
perrito666rogpeppe: its a very strange not really ascii face for "yup, what to do about it"19:29
perrito666I now realize I only know the expression in spanish :p which means it might not go past local boundaries19:30
rogpeppeperrito666: ah, it's a face! i thought it looked like legs... :)19:30
perrito666rogpeppe: the face seems to be a pretty odd unicode character19:30
perrito666rogpeppe: something that, thinking of it, most people not having a language that needs of it might not have installed19:31
rogpeppeperrito666: my suggestion is that we move to gopkg.in and always update to the latest branch of any package whenever possible19:31
rogpeppeperrito666: no, the character worked19:31
perrito666rogpeppe: even though we might be backporting a load of changes as a collateral?19:32
rogpeppeperrito666: yes19:32
rogpeppeperrito666: because we should guarantee backward compatibility19:32
perrito666its a bit like: hey I fixed the typo on the kernel, lets release a minor... and you might have a news scheduler too19:32
rogpeppeperrito666: for gopkg.in branches19:32
rogpeppeperrito666: we're talking about deps here, not core functionaliryt19:33
rogpeppeity19:33
rogpeppeperrito666: if deps implement extra (backwardly compatible) core functionality, then why not?19:33
rogpeppeperrito666: i don't really understand what your real concern is here? increased binary size?19:34
perrito666rogpeppe: not really, I think my concern is mostly bureaucratic so I should drop it19:36
rogpeppeperrito666: if using the latest version turns out to be a problem in practice, we always have the *option* of forking it19:37
perrito666about bugs and the probability of those being added when adding code there19:37
perrito666rogpeppe: agreed there19:37
perrito666rogpeppe: btw, the icon -> http://s3-ec.buzzfed.com/static/2014-05/enhanced/webdr07/21/15/enhanced-29943-1400699227-1.jpg19:37
rogpeppeperrito666: hopefully, later versions of the same package should remove bugs, not add them...19:37
rogpeppeperrito666: :)19:37
rogpeppeperrito666: the emoticon looked correct in my IRC client19:38
perrito666rogpeppe: then your internal emoticon interpreter does not really work :p19:38
rogpeppeperrito666: yeah, i think i need an upgrade19:38
perrito666I have seen some machines render a square for some of those19:38
perrito666rogpeppe: I meant to ask in brusselles, what was the editor you where using, at first it seemed like a heaviy customized vi, but then I doubted19:43
rogpeppeperrito666: http://en.wikipedia.org/wiki/Acme_%28text_editor%2919:43
rogpeppeperrito666: this is a nice intro: https://www.youtube.com/watch?v=dP1xVpMPn8M19:44
rogpeppeperrito666: there is a small but select group of people that use it :)19:45
perrito666Well Ill take you on the small :p19:45
rogpeppeperrito666: it's actually kind of the opposte of vi19:46
perrito666do you use a linux port or run plan9?19:46
rogpeppeopposite19:46
rogpeppeperrito666: i'm currently using trusty19:46
perrito666rogpeppe: the opposite of vi is emacs :p I have been in countless flamewars about the subject19:46
rogpeppeperrito666: actually the reason vi and emacs inspire flamewars is that they are similar19:47
rogpeppeperrito666: like how the worst religious wars are between related faiths19:47
perrito666I attribute the amount of flame on those to the fact that they attract people who like to flame19:47
* perrito666 goes for the intro on video19:48
wwitzel3when you combine rogpeppe with beer it gives him great power and he will attempt to lure you to the darkside, don't fall for it perrito66619:52
rogpeppelol19:52
perrito666wwitzel3: lool, well for starters that editor seems to require for me to use a mouse19:53
rogpeppeactually, lololololol19:53
perrito666which sits at more than an arms lenght from where I sit19:53
perrito666so no chance :p19:53
rogpeppeperrito666: the mouse is an instrument of the Force19:53
perrito666rogpeppe: the xbox kinect is an instrument of the force, the mouse is too far19:54
rogpeppeperrito666: but seriously, the mouse transmits more information than a keyboard19:54
perrito666rogpeppe: I could do with a touchpad :p19:54
perrito666rogpeppe: well I do have a layout set for keyboard mostly, which makes  the mouse a bit irrelevant, I only use it when using things like inkscape or gimp19:55
rogpeppeperrito666: i use it quite successfully with a thinkpad nipple19:55
rogpeppeperrito666: i know people that use it successfully with a touchpad (and some keys set up for button chording)19:56
perrito666rogpeppe: yup, I like the thinkpads thinguie, but all of my thinkpads kbs are in es_ES which sucks for coding, next trip to an english speaking country ill get a thinkpad wireless kb19:56
rogpeppeperrito666: but the mouse power is probably the essence of acme19:56
rogpeppeperrito666: just change the keyboard layout and don't look at your fingers19:57
perrito666rogpeppe: the shape is different sadly19:57
rogpeppeperrito666: orly?19:57
perrito666spanish kb lacks |\19:57
perrito666it has a large return instead19:57
rogpeppeperrito666: that's a bit rubbish19:58
perrito666I currently use an apple blueetooth kb19:58
perrito666not wonderful but light and en_US19:58
rogpeppeperrito666: well, that's a reasonable option19:58
rogpeppeperrito666: anyway, acme is the embodiment of mouse-is-faster-than-keyboard. http://www.asktog.com/TOI/toi06KeyboardVMouse1.html19:59
perrito666yup, borrowed from a friend that became a full time manager and suddenly lost need for his coding station :p19:59
rogpeppeperrito666: and it really does seem to work (for me anyway :-])19:59
perrito666I wont counter a man that can succesfully climb a palm tree while drunk20:00
rogpeppesuccess is in the eye of the beholder20:01
perrito666rogpeppe: well you did not fall or get arrested, that is success20:02
rogpeppeperrito666: in which case i am succeeding all the time, wa hay!20:04
perrito666I cant believe you do that often and not get arrested of fall20:05
rogpeppeperrito666: i am not falling or getting arrested20:10
* rogpeppe wonders why the video is a query parameter on the youtube video url20:12
perrito666rogpeppe: it is a curious choice20:23
rogpeppeperrito666: it makes a mockery of REST :)20:24
perrito666well, they never said it was restful :p20:24
rogpeppeperrito666: and in the end, who cares?20:25
perrito666rogpeppe: well I do, I like nice urls :)20:25
rogpeppeperrito666: "?" "/" ... what's the difference in the end?20:26
=== 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

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