[00:22] <davecheney> it is strange
[00:23] <davecheney> i've seen more piture of HRH in NZ that I have in Au
[01:25] <mup> Bug #1588636 changed: mgo: Panic: Test left sockets in a dirty state (PC=0x46257C) <panic> <unit-tests> <juju-core:Invalid> <https://launchpad.net/bugs/1588636>
[01:27] <davecheney> spot the bug         if err != nil && err == mgo.ErrNotFound {
[01:27] <davecheney>                 return errors.Trace(err)
[01:27] <davecheney>         }
[01:28] <natefinch> aside form the err != nil being extraneous?
[01:28] <natefinch> errors.Cause?
[01:29] <natefinch> if errors.Cause(err) == mgo.ErrNotFound { return errors.Trace(err) }
[01:29] <davecheney> yeah, it's eaither
[01:30] <davecheney> err != nil && err != mgo.ErrNotFound
[01:30] <davecheney> or err == mgo.ErroNotFound
[01:30] <davecheney> but the latter would mean ignoreing any error other than mgo.ErrNotFound
[01:31] <natefinch> well, yes.. it depends on the rest of the error stack to figure out which one they meant
[01:31] <natefinch> er s/error stack/context of the code
[01:32] <natefinch> I kinda hate errors.Trace.  It just adds so much noise to the code.   If we had the stacktrace on the error, I don't think I'd ever use trace.
[01:33] <davecheney> https://github.com/juju/juju/commit/93d52ed7
[01:33] <davecheney> fix some log messages ... and add an entire state/presence package
[01:33] <davecheney> no biggie
[01:34] <davecheney> natefinch: that's why my errors package captures the full stacktrace at the point of creatin
[01:34] <davecheney> it has some drawbacks
[01:34] <davecheney> but compared to errors.Trace turds everywhere
[01:34] <davecheney> it's paid for itself
[01:36] <natefinch> davecheney: that commit is pretty funny... I presume the presence stuff was intended to be committed separately
[01:36] <natefinch> davecheney: also, whoowee that is some old code
[01:37] <davecheney> yeah, that line is older than some of your kids
[01:37] <natefinch> davecheney: this is true.
[01:47] <natefinch> wallyworld: I spent Friday looking at the logs, but I can't see any differences between the setaddress calls that work and those that fail. I'm printing out the entire list of operations... and the ones that work look identical to the ones that fail.. and the ones that fail, the ops don't change from attempt to attempt, as they should if things were actually changing.
[01:47] <davecheney> natefinch: https://github.com/juju/juju/pull/5537 if you feel so inclined
[01:49] <wallyworld> natefinch: maybe we need to log what is actually in the db
[01:50] <natefinch> wallyworld: yeah, I had that in there and then must have deleted it while debugging why I wasn't getting any log output.  Sigh.
[01:54] <natefinch> davecheney: wow, totally messed up error handling for 4 years...
[01:55] <natefinch> admcleod_: i guess mgo doesn't often return errors other than not found
[01:55] <natefinch> whoops
[01:55] <natefinch> davecheney: that was for you, of course
[01:55] <natefinch> stupid fingers
[01:56] <natefinch> davecheney: I'd ask for a unit test to verify it, but... uh.. yeah.  LGTM
[01:56] <davecheney> natefinch: didn't fail before : didn't fail afterwards :)
[01:57] <natefinch> what I wouldn't give for separate persistence layer
[01:58] <davecheney> you had me at separate layer
[03:06] <davecheney> https://bugs.launchpad.net/juju-core/+bug/1589339
[03:06] <mup> Bug #1589339: environs/manual: test failure if host does not have a valid reverse dns record <juju-core:New> <https://launchpad.net/bugs/1589339>
[03:06] <davecheney> nice
[03:06] <natefinch> lol
[03:08] <davecheney> solution: hack /etc/hosts
[03:09] <davecheney> test isolation, how does it work?
[03:10] <mup> Bug #1589339 opened: environs/manual: test failure if host does not have a valid reverse dns record <juju-core:New> <https://launchpad.net/bugs/1589339>
[03:13] <mup> Bug #1589339 changed: environs/manual: test failure if host does not have a valid reverse dns record <juju-core:New> <https://launchpad.net/bugs/1589339>
[03:22] <mup> Bug #1589339 opened: environs/manual: test failure if host does not have a valid reverse dns record <juju-core:New> <https://launchpad.net/bugs/1589339>
[03:24] <natefinch> davecheney: wow, I just noticed from an offhand comment on golang-nuts that builds are now deterministic... that's amazing
[03:25] <davecheney> natefinch: cool
[03:25] <davecheney> i hope it lasts
[03:25] <davecheney> googlers don't care about byte for byte comparisons
[03:25] <davecheney> and there is no test for it
[03:25] <natefinch> davecheney: gah, there should be a test for it
[03:25] <natefinch> davecheney: it's SOOOO useful
[03:38] <wallyworld> axw: here's part 1. next I can introduce a get-controller-config CLI and make get-model-config only show the model specific bits; we can also pass in config from cloud.yaml as controller config at bootstrap time
[03:38] <wallyworld> http://reviews.vapour.ws/r/4983/
[03:38] <axw> wallyworld: thanks, just saw. just from reading the summary: why in the "controllers" collection rather than the settings collection?
[03:39] <wallyworld> axw: collection needs to be global
[03:39] <wallyworld> so all models can always read the controller config
[03:39] <axw> wallyworld: ok
[03:40] <wallyworld> axw: i started out in settings and it all went to shit with different hosted models
[03:40] <wallyworld> we now use that controllers collection for a few things it seems
[03:42] <wallyworld> axw: once this gets a +1 or whatever, let me know where you're at so we can decide what bit i should do next - the CLI or controller config from clouds.yaml. also, i think we need to handle the case for things like resource-tags where the model values don't overwrite but merge
[03:43] <axw> wallyworld: sure. merging config sounds like something we don't need to do right away
[03:44] <wallyworld> yeah
[03:44] <wallyworld> axw: i should have said in the PR, but a bunch of the green is model config stuff moved from state.go to its own modelconfig.go file
[03:45] <axw> wallyworld: yep, thanks
[03:45] <wallyworld> and i found some old code to delete also
[03:52] <mup> Bug #1589350 opened: apiserver/provisioner: tests do not pass with go 1.7 beta 1 <juju-core:New> <https://launchpad.net/bugs/1589350>
[04:07] <mup> Bug #1589350 changed: apiserver/provisioner: tests do not pass with go 1.7 beta 1 <juju-core:New> <https://launchpad.net/bugs/1589350>
[04:10] <mup> Bug #1589350 opened: apiserver/provisioner: tests do not pass with go 1.7 beta 1 <juju-core:New> <https://launchpad.net/bugs/1589350>
[04:10] <mup> Bug #1589351 opened: provider/azure: test failure during stress test <juju-core:New> <https://launchpad.net/bugs/1589351>
[04:16] <davecheney> https://launchpad.net/bugs/1589353 what a shitshow
[04:16] <mup> Bug #1589353: apiserver/annotations: test failure during setup <juju-core:New> <https://launchpad.net/bugs/1589353>
[04:40] <mup> Bug #1534757 changed: Attempting to run charm before unit provisioned, 1.26 <2.0-count> <juju-release-support> <lxd> <juju-core:Expired> <https://launchpad.net/bugs/1534757>
[04:40] <mup> Bug #1589353 opened: apiserver/annotations: test failure during setup <juju-core:New> <https://launchpad.net/bugs/1589353>
[04:41] <davecheney> axw: wallyworld https://github.com/juju/testing/pull/101
[04:41] <davecheney> here is a simple one
[04:41] <wallyworld> ok
[04:43] <wallyworld> davecheney: ty, nice to see that fixed
[04:43] <davecheney> wallyworld: it's one of those bugs that doesn't stay fixed
[04:44] <davecheney> wallyworld: i've been trying to repro https://bugs.launchpad.net/juju-core/+bug/1588574
[04:44] <mup> Bug #1588574: Session already closed in state/presence <blocker> <ci> <intermittent-failure> <juju-core:In Progress by dave-cheney> <https://launchpad.net/bugs/1588574>
[04:44] <davecheney> but all i've acomplished so far today is raising 4 extra bugs
[04:44] <wallyworld> yeah, the presence stuff sucks
[04:45] <wallyworld> axw: we'll need to get to the inheritance stuff pretty quickly to allow config from clouds.yaml to be handled. i guess we should keep controller only config like api port totally separate from anything that can be inherited
[04:47] <axw> wallyworld: unless it's going to be a huge amount of rework (didn't look like it), I'd feel more confident reviewing them separately.
[04:48] <wallyworld> ok
[04:49] <anastasiamac> davecheney: did u try to remove omitempty as per my suggestion?
[04:50] <davecheney> anastasiamac: no i did not i'm sorry
[04:50] <davecheney> i'm still trying to reproduce the error locally
[04:50] <davecheney> anastasiamac: why will changing the json part of a struct fix the bug ?
[04:50] <anastasiamac> davecheney: it does not cause probs for me except at landing :D
[04:51] <anastasiamac> davecheney: every attemp at landing came up with the error messaage u r chasing "session closed"
[04:51] <anastasiamac> davecheney: possibly unrelated and was just this PR's luck  :-P
[04:52] <davecheney> anastasiamac: yeah, i cannot reprodyce the bug locally either
[04:52] <davecheney> i'm trying to build an environment in ec2 that matches CI
[04:52] <davecheney> but i keep hitting flakey tests
[04:52] <anastasiamac> davecheney: \o/
[04:52] <davecheney> i've raised 4 bugs already today and haven't managed to run all the tests successfully
[04:53] <anastasiamac> davecheney: it's sad but even that makes a productive day :-P
[04:54] <davecheney> if I fix all 4 bugs I raised, then I'm back to square one, so that's something
[04:55] <anastasiamac> :D
[05:06] <davecheney> spoiler alert: i'm probably not goig to fix all four today
[05:13] <anastasiamac> funny and here I was looking forward to watching it all being fixed today :D
[05:14] <wallyworld> axw: bbiab, almost got a revised branch ready, but school pickup
[05:52] <mup> Bug #1589372 opened: state: state test failure during stress test <juju-core:New> <https://launchpad.net/bugs/1589372>
[07:02] <mup> Bug #1589385 opened: leftover eth0.cfg in /etc/network/interfaces.d <4010> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1589385>
[07:11] <davecheney> mongodb is such a pile of crap
[07:19] <davecheney> I _finally_ got the bug to trigger locally
[07:22] <anastasiamac> davecheney: \o/ how?
[07:22] <davecheney> anastasiamac: persistance
[07:22] <davecheney> just need enough load
[07:22] <davecheney> in the right way
[07:23] <anastasiamac> well done! ;-P
[07:32] <davecheney> https://github.com/juju/testing/pull/102
[08:44] <wallyworld> axw: would you yave time to look at http://reviews.vapour.ws/r/4972/ ? it needs to merge into the feature branch
[09:01] <dimitern> voidspace, fwereade: standup?
[09:01] <dimitern> dooferlad: ^^
[09:05] <voidspace> dimitern: sorry, omw
[09:05] <voidspace> got distracted
[09:34] <dimitern> fwereade: how does the advice to return concrete errors (e.g. ErrFooFailed) align with "no global variables" ?
[09:35] <dimitern> (as I suspect global consts are fine)
[10:06] <davecheney> fwereade: https://github.com/juju/juju/pull/5543
[10:06] <davecheney> if you have the time
[10:25] <fwereade> dimitern, ha :) good point, possibly error types are safer? I have been bitten a couple of times by people assigning to stuff that's "obviously" a global "constant" variable
[10:25] <fwereade> dimitern, but types don't quite feel like they pay for themselves?
[10:26] <dimitern> fwereade: yeah, I suspect so
[10:26] <dimitern> fwereade: it's nice to use if errors.Cause(err) == ErrMyFooFailed
[10:28] <dimitern> fwereade: well, I guess if we define type SimpleError string and func (s SimpleError) Error() { return s }, we can define all such concrete errors as const ErrFooFailed SimpleError = "foo failed"
[10:28] <dimitern> and get both the const guarantee and no global vars
[10:29] <fwereade> davecheney, LGTM
[10:30] <fwereade> dimitern, mm, I think I like that
[10:30] <fwereade> dimitern, neat
[10:32] <dimitern> fwereade: it even works: https://play.golang.org/p/jbCEra4_xi
[10:33] <dimitern> (and it should be almost the same using Cause())
[10:37] <dimitern> fwereade: re tests isolation, while treating tests and production code the same: given a ctor NewFooForSeries(series string) (Foo, error); and Foo being an interface with concrete (unexported) implementations per series
[10:39] <dimitern> fwereade: how to properly isolate this for tests (assuming e.g. Foo.GetFoo() returns different results based on what's there on the local machine)? One option is to allow "dummy" as series and construct a no-op Foo, that has extra methods tests can use to set a pre-canned result from GetFoo()..
[10:50] <fwereade> dimitern, I *think* that if they differ interestingly enough to be different types they deserve different ctors for direct testing? then you can have a wrapper around a map[series]ctor with shims as necessary and test that as much as it needs -- but it's much closer to being purely data-driven
[10:52] <fwereade> dimitern, and then if NewXenialFoo returns an exported *XenialFoo it seems sane/good to check the underlying types that come out of a Foo factory
[10:53] <dimitern> fwereade: I was thinking something like this might work: https://play.golang.org/p/bW-TI4l8yI
[10:53] <fwereade> dimitern, or rather checking that some series return a *UpstartFoo and others a *SystemdFoo
[10:54] <dimitern> fwereade: and the dummyRouteSource there is perfectly valid at run-time, but will be mostly used by tests; no special treatment
[10:56] <dimitern> fwereade_: hey, did you get the last link?
[10:56] <fwereade_> dimitern, I think I'd rather see a *WindowsRouteSource and a *LinuxRouteSource
[10:56] <fwereade_> dimitern, don't think so
[10:57] <fwereade_> dimitern, (both the above could be unit tested everywhere, I think?)
[10:57] <dimitern> fwereade_: here:https://play.golang.org/p/bW-TI4l8yI
[10:57] <fwereade_> ah I did see that one
 dimitern, or rather checking that some series return a *UpstartFoo and others a *SystemdFoo
 dimitern, is anything in there so platform-specific it needs build tags?
[10:58] <dimitern> fwereade_: my point is NewRouteSource() will be called somewhere early as part of a lot of tests, and by default it can use the dummyRouteSource
[10:58] <dimitern> fwereade_: it needs to use different sources (usually execute different tools and parse different outputs)
[10:58] <fwereade_> dimitern, I was thinking I'd rather have an explicit NewFakeRootSource() for tests?
[10:59] <dimitern> fwereade_: that's cleaner perhaps
[10:59] <fwereade_> dimitern, and, yeah, but you don't want to hit the actual OS with those calls in unit tests
[10:59] <dimitern> fwereade_: and the Fake one can implement e.g. SetRoutes() in addition to GetRoutes() from RouteSource
[11:00] <fwereade_> dimitern, yeah, that sounds good, or you could just pass them in in the ctor
[11:00] <fwereade_> dimitern, harder for people to induce races ;p
[11:01] <dimitern> fwereade_: I really don't want to repeat earlier mistakes, e.g. patching the package tests for GetRoutes() to use faked ones, but providing no easy way to do the same outside the package
[11:01] <fwereade_> dimitern, quite so, it feels to me like it's a foo/footest.NewRouteSource(...) situation
[11:01] <dimitern> fwereade_: routes as Fake ctor args is nice! will do that
[11:02] <fwereade_> dimitern, where do we need to thread the routes through to, by the way?
[11:03] <dimitern> fwereade_: and having specific ctor's (NewWindowsRouteSource) rather than a switch-sorta-factory feels better - NewWindowsRouteSource can still be there but it's impl. can be in a +build windows - guarded file
[11:04] <fwereade_> dimitern, why hide it away? just makes it easier to break when you're not running on windows
[11:04] <dimitern> fwereade_: atm I need to implement and parse "get default route", and then use it as part of the container provisioing step
[11:04] <fwereade_> dimitern, unless it's guarding actual syscalls I'd rather steer clear of +build where possible
[11:05] <dimitern> fwereade_: fair point
[11:05] <dimitern> fwereade_: it's more about guarding against the lack of a windows-specific tool
[11:05] <fwereade_> dimitern, ok, but we don't want to *actually* call the tool in the unit tests, regardless of system
[11:09] <dimitern> fwereade_: nope, only in the package tests
[11:09] <dimitern> fwereade_: we'll call a patched executable for the tool
[11:10] <dimitern> fwereade_: I was thinking of using natefinch's PatchExec that uses jujud as the binary to call
[11:10] <dimitern> fwereade_: and outside of the package, the NewDummyRouteSource() will be used in all tests
[11:15] <dimitern> fwereade_: how does that sound?
[11:18] <fwereade_> dimitern, do we have to PatchExec or can we supply, e.g., a `func RunCommand(string, ...string) (notsurewhattoreturn, error)`
[11:18] <dimitern> fwereade_: https://github.com/juju/testing/blob/master/cmd.go#L203
[11:19] <dimitern> it's essentially what it does - patching exec.RunCommand
[11:20] <dimitern> fwereade_: "patching" is incorrect here, as nothing is actually patched
[11:20] <dimitern> fwereade_: AIUI we're using GetExecCommand when needed in the suite, rather than using PatchValue()
[11:21] <axw> wallyworld: I gave that PR a LGTM on GitHub already
[11:22] <wallyworld> axw: oh great ty. just about to push up a new revision of the other. found a bug where we were setting up cfg with controller uuid and then initialising state with something else
[11:22] <axw> wallyworld: cool. I probably won't be able to review till the morning tho, sorry
[11:22] <wallyworld> and then there were inconsistencies. may have just been tests
[11:22] <wallyworld> that's fine
[11:24] <fwereade_> dimitern, I think it *does* still depend on some magic patching, from having to embed that suite, and I think it smells a bit maybe? -- but it *does* still give you a real *exec.Cmd, which *is* pretty cool
[11:25] <fwereade_> dimitern, so that sounds reasonable to me
[11:25] <dimitern> fwereade_: ah, sorry - PatchValue can be used after all (e.g. environs/tools/build_test.go:TestGetVersionFromJujud), but isn't necessary (e.g. cmd/juju/commands/main_test.go:TestFirstRun2xFrom1xNotUbuntu - we can just run the patched command directly with CaptureOutput)
[11:26] <dimitern> I quite like that approach :)
[11:26] <dimitern> s/that/that second/
[11:26] <dimitern> fwereade_: ok, cheers
[11:26] <fwereade_> dimitern, right, ok, but what's writing to os.Stderr/out in the first place? doesn't having to capture those imply broken isolation?
[11:27]  * fwereade_ may well be missing something
[11:27] <dimitern> fwereade_: I think it's still isolated, see: CaptureOutput creates both stderr and stdout in isolation
[11:28] <dimitern> https://github.com/juju/testing/blob/master/cmd.go#L307
[11:28] <fwereade_> dimitern, yeah, that's what's bothering me -- what is causing stuff to be written to os.Std* that we need to patch it out in :317?
[11:29] <dimitern> fwereade_: exec.Cmd.Run() does
[11:30] <fwereade_> dimitern, this feels like a sign that the (string, ...string) shortcut is maybe the source of the problem
[11:30] <fwereade_> dimitern, only if you don't set the command up properly ;p
[11:33] <fwereade_> dimitern, utils/exec doesn't seem that great for replacing either, though, what with RunParams actually being stateful
[11:33] <dimitern> fwereade_: so you're saying rather than embedding PatchExecHelper, then using GetExecCommand() and CaptureOutput, use a ctor e.g. NewWindowsRouteCmd() that sets it up to run "route print", and NewLinuxRouteCmd() doing "ip route ..", and a NewFakeRouteCmd() taking args and output?
[11:35] <dimitern> by "sets it up to run" I mean &exec.Cmd{Args: .., Path: .., Stdin: inBuf.Reader(), ..}
[11:35] <fwereade_> dimitern, I don't *think* so? if we need the types we need the routes, I presume -- clients will just want to accept a `Routes`, right?
[11:35] <dimitern> s/I mean/I mean return/
[11:36] <dimitern> fwereade_: Routes like []RouteInfo argument to the OS-specific RouteSource ctor?
[11:37] <fwereade_> dimitern, no, just a type encapsulating the routes, already created
[11:38]  * dimitern steps out for ~30m
[12:02] <frobware> dooferlad: ping
[12:04] <dooferlad> frobware: pong
[12:14] <frobware> dooferlad: for the reboot cloud-init stanzas - did that work for all of precise, trusty and xenial?
[12:17] <dooferlad> frobware: IIRC, yes
[12:20] <mup> Bug #1589471 opened: Mongo cannot resume transaction <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1589471>
[12:37] <dooferlad> frobware: that branch that did the reboot is gone :-(
[12:38] <frobware> dooferlad: do you recall the name of the branch?
[12:38] <dooferlad> frobware: no
[12:38] <frobware> dooferlad: I have you as a git remote
[12:41] <dooferlad> frobware: git reflog to the rescue :-)
[12:43] <frobware> dooferlad: http://pastebin.ubuntu.com/17060265/
[12:43] <dooferlad> frobware: yep
[12:45] <frobware> dooferlad: just shows how long we've been futzing with this
[12:46] <dooferlad> frobware: no wonder we have a bit of a bunker mentality
[14:00] <frobware> dooferlad: ping
[14:02] <dooferlad> frobware: pong
[14:08] <frobware> dooferlad: please could you capture the output (or perhaps lack of) for the bond/LACP issue and raise a bug.
[14:08] <frobware> dooferlad: asking as you definitively have more NICs.... :)
[14:11] <dooferlad> frobware: it simply hangs after the bridge script runs. Nothing more to say!
[14:13] <babbageclunk> dooferlad, dimitern, frobware: what do maas 1.9 node-groups correspond to in maas 2?
[14:13] <dimitern> babbageclunk: to rack controllers
[14:13] <babbageclunk> dimitern: thanks
[14:29]  * fwereade_ thinks he just barely resisted the urge to name a type *state.Less
[14:34] <natefinch> fwereade_: nice
[14:47] <alexisb> hey all, happy monday!
[14:48] <perrito666> hey
[14:48] <katco> alexisb: happy monday
[15:08] <babbageclunk> dimitern: ping?
[15:09] <dimitern> babbageclunk: pong
[15:12] <babbageclunk> dimitern: can I pick your brains about this maas spaces demo stuff in the juju-sapphire hangout?
[15:12] <dimitern> babbageclunk: yeah, ok - omw
[15:12] <babbageclunk> dimitern: thx!
[15:31] <katco> hey, does anyone know how to manually log into the controller's mongo instance now? the password in accounts.yaml doesn't seem to work
[15:36] <perrito666> katco: if mongo is v3 you need to install mongodb-org ppa and pull the 3.x client
[15:36] <perrito666> people at packaging are working to provide the client along with the tools soon
[15:36] <katco> perrito666: i'm on beta9, so i assume that v3
[15:36] <perrito666> so we dont have to
[15:36] <perrito666> katco: it actualy depends on your distro
[15:36] <perrito666> xenial?
[15:36] <katco> perrito666: the machine i have available atm is wily
[15:36] <perrito666> your => your machine 0
[15:36] <katco> perrito666: host machine
[15:37] <katco> perrito666: bootstrapped controller is xenial though
[15:37] <perrito666> then yes, mongo 3
[15:37] <natefinch> controller is what matters
[15:38]  * perrito666 is stuck waiting for the plumber and has no food, happy monday
[15:38] <natefinch> mramm: thank you for your repro case on lxd
[15:38] <natefinch> mramm: on that ip address setting bug
[15:39] <katco> perrito666: ta. do you have a url for that ppa?
[15:40] <perrito666> katco: https://docs.mongodb.com/v3.0/tutorial/install-mongodb-on-ubuntu/ sorry not a ppa, old style debline
[15:40] <katco> perrito666: ah ok
[15:41] <katco> perrito666: ta for your help
[15:41] <perrito666> np, ask if you need anything else
[15:42] <natefinch> my computer is not so happy about having a 13 machine LXD environment deployed :)
[15:43] <natefinch> obv time for a bigger machine
[15:45] <perrito666> natefinch: openstack bundle?
[15:52] <natefinch> perrito666: just a couple random bundles, HA/big data stuff
[15:53] <mramm> natefinch: yea, I just built a desktop machine with 64 gig ram because juju deploying so much stuff broke my (relatively powerful) laptop
[15:54] <perrito666> yep, lots of ram and lots of ssd :)
[15:55] <mramm> yep, two different SSD's on two different SATA channels, one for the system and one for the lxd filesystem
[15:55] <natefinch> yep... my laptop is quad core i7 with 16GB of RAM... I'm glad they started offering 32GB on new XPS 15s.  But I keep thinking that I should really just get a desktop and keep this laptop just for sprints.  for the amount I spent on this laptop I could get a ridiculous desktop
[15:56] <perrito666> go desktop, is the way
[15:56] <perrito666> I have done that and use the laptop for whenever I cant work at home
[15:56] <natefinch> plus it would be fun to build a desktop from scratch again... haven't done that in like a decade
[16:07] <redir> brb reboot
[16:09] <mup> Bug #1589385 changed: leftover eth0.cfg in /etc/network/interfaces.d <4010> <juju-core:New> <MAAS:Invalid> <https://launchpad.net/bugs/1589385>
[16:11] <perrito666> bbl, errands
[16:19] <bdx> I too had to throw together a more capacitive desktop for deploying lxd in my home lab
[16:19] <bdx> behold her beauty
[16:20] <bdx> http://imghub.org/image/UMUX
[16:20] <bdx> :-) :-)
[16:20] <bdx> http://imghub.org/image/UrGu
[16:21] <bdx> one more, http://imghub.org/image/UxWY
[16:24] <bdx> to be honest, I built her a few yrs ago ... she serves as my lxd lab now though
[16:24] <natefinch> nice cooling rig
[16:24] <mup> Bug #1589581 opened: Consistant basic use of debug-log between 1.25 and 2.0 <pyjuju:New> <https://launchpad.net/bugs/1589581>
[16:25] <natefinch> how many NICs are in there? looks like you have 4 ethernet cords plugged into it?
[16:27] <bdx> natefinch, yea .... things are arranged slightly different now, but I use to have to make up for not having 10G network infra
[16:27] <natefinch> bdx: ha.  yeah, must be hard roughing it on single gigabit ethernet
[16:29] <bdx> I would create iscsi extents and share them to different servers over different interfaces/networks to try to mitigate stomping the 1G
[16:29] <bdx> lol
[16:33] <bdx> now she has 10G, so I can share her fast zfs arrays to other servers more better
[16:35] <bdx> I use to be heavily into the gpu modding game ... those 660's in there are modded to grid k2's
[16:37] <bdx> they no longer exist tho
[16:38] <bdx> she is gpu-less nowadays
[17:34] <alexisb> cherylj, ping
[17:56] <cherylj> alexisb: pong
[17:56] <alexisb> heya cherylj
[17:56] <alexisb> welcome back
[17:59] <cherylj> thanks :)
[18:40] <mup> Bug #1588911 changed: Juju does not support 2.0-beta9 <blocker> <ci> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1588911>
[18:40] <mup> Bug #1589628 opened: Unable to bootstrap lxd with juju 2 because of x509 certificate error <juju-core:New> <https://launchpad.net/bugs/1589628>
[18:40] <mup> Bug #1589635 opened: github.com/juju/juju/state fails on TestMachinePrincipalUnits with an unexpected name <juju-core:New> <https://launchpad.net/bugs/1589635>
[18:43] <mup> Bug #1589628 changed: Unable to bootstrap lxd with juju 2 because of x509 certificate error <juju-core:New> <https://launchpad.net/bugs/1589628>
[18:43] <mup> Bug #1589635 changed: github.com/juju/juju/state fails on TestMachinePrincipalUnits with an unexpected name <juju-core:New> <https://launchpad.net/bugs/1589635>
[18:43] <mup> Bug #1588911 opened: Juju does not support 2.0-beta9 <blocker> <ci> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1588911>
[18:49] <mup> Bug #1588911 changed: Juju does not support 2.0-beta9 <blocker> <ci> <juju-core:Fix Released by natefinch> <https://launchpad.net/bugs/1588911>
[18:49] <mup> Bug #1589628 opened: Unable to bootstrap lxd with juju 2 because of x509 certificate error <juju-core:New> <https://launchpad.net/bugs/1589628>
[18:49] <mup> Bug #1589635 opened: github.com/juju/juju/state fails on TestMachinePrincipalUnits with an unexpected name <juju-core:New> <https://launchpad.net/bugs/1589635>
[18:56] <katco> perrito666: ping
[18:57] <perrito666> katco: pong
[18:58] <katco> perrito666: hey, are api calls currently carrying information about the user who's making it?
[18:58] <perrito666> iirc, the info is in the connection only
[19:00] <katco> perrito666: can you give me a jumping-off point?
[19:02] <perrito666> katco: certainly, if I am guession correctly what you are looking for, apisercer/client_auth_root.go is a great place to start, there you know the facade, method and the user all in the same place
[19:02] <katco> perrito666: awesome, that sounds like a winner, ta
[19:03] <perrito666> wow, my typo rate really worsens when my wrist is hurt
[19:03] <perrito666> katco: np
[19:10] <natefinch> anyone online know anything about the state.address struct?
[19:13] <mup> Bug #1589641 opened: github.com/juju/juju/state fails on ActionSuite.TestUnitWatchActionNotifications <juju-core:Incomplete> <juju-core service-to-application:New> <https://launchpad.net/bugs/1589641>
[19:36] <redir_lunch> natefinch: not I
[20:00] <natefinch> voidspace: don't suppose you're working late today?
[20:13] <mup> Bug #1589670 opened: backups does not implement Backups for non linux OSes <juju-core:New> <https://launchpad.net/bugs/1589670>
[20:15] <thumper> fwereade_: ping?
[20:33] <natefinch> alexisb: btw, we'll need to hand off this bug.  I'll be on later, but I'm not going to figure it out in the next half hour.  .
[20:43] <alexisb> natefinch, did you provide an update in the bug?
[20:43] <mup> Bug #1589680 opened: Upgrading to cloud-archive:mitaka breaks lxc creation <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1589680>
[20:44] <natefinch> alexisb: yep.  Huge brain dump in there
[20:44] <alexisb> thanks
[21:14] <thumper> davecheney: https://bugs.launchpad.net/juju-core/+bug/1588575
[21:14] <mup> Bug #1588575: allwatcher_internal_test has intermittent failure <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1588575>
[21:25] <davecheney> thumper: thanks, no promises I can start on it today, I need to verify that i've found all the places where we stop but don't wait for the watcher to die
[21:46] <mup> Bug #1576874 changed: restore-backup never completes <backup-restore> <blocker> <ci> <regression> <juju-core:Fix Released by hduran-8> <https://launchpad.net/bugs/1576874>
[21:53] <perrito666> wallyworld: ffs, that keeps bitting me
[21:53] <wallyworld> easy fix at least
[21:54] <perrito666> wallyworld: yeah, I keep forgetting we maintain all that thing in windows for no good reason
[23:06] <alexisb> heya wallyworld, do you have a few minutes for me?
[23:06] <wallyworld> suppose so :-)
[23:07] <wallyworld> have standup in 5, meet in 1:1?
[23:08] <wallyworld> alexisb: in hangout
[23:16] <wallyworld> axw: anastasiamac: perrito666: be there real soon
[23:16] <perrito666> k
[23:18] <axw> looking for the end of my webcam USB in the dark, be there soon too...
[23:28] <redir> axw: you coming back?
[23:54] <wallyworld> perrito666: here tis https://github.com/juju/juju/pull/5547
[23:54] <wallyworld> can you +1 and i'll land
[23:55] <perrito666> bastard you got review 4994
[23:55] <perrito666> ship it
[23:55] <wallyworld> ty