[00:11] wallyworld: I think I figured it out (notes logged to the lp issue) [00:12] ericsnow: sorry, still in meeting [00:12] wallyworld: the worker closes the channel when its loop finishes; so if the runner restarts the worker then it's using a closed channel [00:12] wallyworld: np :) [00:12] wallyworld: and I'm sorry you're stuck in meetings :/ [00:48] ericsnow: ah, good pickup. i now have 40 mins till next meeting :-) [01:13] wallyworld: yeah, I'm not aware of the precedent for dealing with that situation and simple solution isn't coming to mind [01:13] wallyworld: perhaps we should only close the channel when the worker's tomb is killed [01:16] Bug #1494542 opened: unit does not go to error state [01:19] ericsnow: maybe, i need to look atthe code in detail, haven't had a chance yet [01:20] wallyworld: np, I've got to EOD so if you don't pick it up I will tomorrow === natefinch-afk is now known as natefinch [02:17] waigani: hey, merge my PR! https://github.com/waigani/GoOracle/pull/19 [02:18] natefinch: yikes, I haven't looked at this in a while! thanks :) [02:18] waigani: :) Figured as a coworker, I had the right to poke you, especially since it's just docs ;) [02:20] natefinch: done [02:20] waigani: awesome :) [02:20] I know how it is. I have a couple outstanding PRs on my projects I need to attend to. [03:27] wallyworld: just managed to bootstrap :) I manually added a public IP to machine-0, but it's not hard to do that in code [03:27] axw: whoohoo [03:27] awesome [03:27] wallyworld: I'll write up my feedback email now. [03:28] tyvm [03:28] be gentle with them :-) [03:28] wallyworld: :) [03:38] gah, our inconsistent use of Id vs ID is sooo annoying [04:23] wallyworld: sent a big wall of text. lunch time [04:40] axw: np, ty, was just otp [05:29] well this week has pretty much sucked [05:29] glad it's over [05:29] time for wine [05:29] * thumper hopes for better next week === urulama__ is now known as urulama [07:36] TheMue: (not sure if message arrived) when you have time, could you please take a look at http://reviews.vapour.ws/r/2628/ ? note that this work is proposed for merging into a feature branch currently. thanks! [07:38] frankban: yep, will take a look [07:38] TheMue: ty === akhavr1 is now known as akhavr [08:05] frankban: you've got a review [08:06] TheMue: thanks! [09:03] dimitern, TheMue: standup time [09:04] frobware, we're there [09:04] frankban: we're, retrospective and planning [09:04] frobware, ah, sorry - it's a different link today [09:05] oops, frobware [09:05] https://plus.google.com/hangouts/_/canonical.com/sapphire [09:05] aha [09:16] TheMue: could you also take a look at the followup branch in http://reviews.vapour.ws/r/2630/ (still proposed against the feature branch)? [09:17] frankban: currently in retrospective HO, but then, yes [09:17] TheMue: ty! [09:38] Bug #1494661 opened: Old logs are not compressed or removed [11:33] dimitern, reviewed http://reviews.vapour.ws/r/2593/ at last, you might have thoughts re some of my comments [11:35] fwereade, sweet! thanks! [11:35] morning all [11:37] fwereade: could you re-look at http://reviews.vapour.ws/r/2592/ [11:37] pretty please? [11:37] perrito666, looking [11:46] * perrito666 really wishes he wasn't freezing [12:10] dimitern: frobware: TheMue: dooferlad: morning! [12:13] voidspace: heya, you missed a pretty long meeting today. ;) [12:18] TheMue: full team meeting? [12:18] voidspace: retro/planning [12:18] TheMue: ah! shame [12:18] TheMue: I should check the board [12:18] TheMue: it's just past 8am here, I still need coffee! [12:19] voidspace: no, too early for your time zone. you're still in the US? [12:19] TheMue: I'm back in Europe on Monday [12:20] TheMue: yep, still at Wayne's house [12:20] TheMue: he's now married and the big celebration is tomorrow [12:20] voidspace: relaxing after the wedding party :D [12:20] voidspace: oh, tomorrow, ic [12:22] frankban: you've got a review [12:22] TheMue: ty! [12:23] voidspace, hey there :) welcome back! [12:26] TheMue: great suggestion Errorf, I have been looking for something like that but did not find it for some reason [12:27] frankban: I would have called it Newf, so it's more easy to find. *bg* [12:27] TheMue: yeah [12:44] Bug #1494726 opened: TestGetUsesCache different mime-type centos [12:44] Bug #1494729 opened: Panic created by net/http.fileTransport.RoundTrip [12:47] voidspace, hiya - let's catch up monday as I have a couple of meetings RSN [12:55] dimitern, want to sync up? [12:58] frobware, I started to summarize my thoughts around the needed changes - how about I finish them and send you a mail with those? [12:58] dimitern, sure [12:59] frobware: ok, no problem [12:59] frobware, cheers [13:01] fwereade, ping? [13:01] mattyw, pong [13:02] fwereade, do you have 10 minutes to receiving a whinge? [13:02] mattyw, certainly, just between reviews :) [13:02] Bug #1494734 opened: Panic in jujud/agent on ppc64el [13:08] Bug #1494734 changed: Panic in jujud/agent on ppc64el [13:14] Bug #1494734 opened: Panic in jujud/agent on ppc64el [13:21] Bug #1494743 opened: TestMachineAgentRunsCertificateUpdateWorkerForStateServer timeout === tvansteenburgh1 is now known as tvansteenburgh [13:49] TheMue: time for a quick third and last one along the same line? http://reviews.vapour.ws/r/2633/ [13:50] Hello all. I have a service comprised of three units (all on different machines). If one of those machines disappears, should I expect to see one or both of cluster-{broken,departed} to be triggered on the other units? [13:51] Bug #1494749 opened: TestWorkerRetriesOnPublishError fails on wily [13:51] Bug #1494754 opened: TestActionsReceived failed on precise [13:51] (tvansteenburgh: ^^^) [13:52] Odd_Bloke: yeah, i'm eagerly awaiting the answer :) [13:56] is this the only place where users can look in order to choose a tools version to upgrade to? https://streams.canonical.com/juju/tools/releases/ [13:58] regarding #1494661, didn't we fix log rotation (including compressing/deleting) already? [13:58] Bug #1494661: Old logs are not compressed or removed [14:02] pmatulis: yes, those are the latest stable tools, there's also a devel folder with newer, but usually alpha or beta versions [14:13] fwereade: you have a few minutes (in a little while) to talk about how to fix #1493123? [14:13] Bug #1493123: Upgrade in progress reported, but panic happening behind scenes [14:13] [14:14] ericsnow, sure [14:14] fwereade: OTP, but I'll ping you soon :) [14:22] fwereade: you free? [14:23] ericsnow, yeah [14:24] Bug #1494765 opened: TestWorkerRemovesDeadAddress fails on ppc64el [14:24] Bug #1494774 opened: MetricSenderSuite fails on ppc64el panic [14:25] my juju is in a state where [14:25] "juju bootstrap -e local" hangs forever [14:25] after "Bootstrapping Juju machine agent" [14:25] anyone have an idea what might be going on? [14:26] tried --debug? [14:26] i can't even interrupt the bootstrap [14:26] it's hung at "Interrupt signalled: waiting for bootstrap to exit" [14:27] bogdanteleaga: so i *would* try --debug if i could get it to stop [14:27] C^Z and kill process? :) [14:27] yeah, i think i'll sigquit it [14:27] might have to clean up after it if you do that tho [14:27] bogdanteleaga: any idea what i might need to clean up? [14:28] any machines/networks it created I'm thinking [14:28] I usually just power off maas machines [14:28] not sure about local [14:28] bogdanteleaga: lxc-ls shows one entry [14:28] juju-trusty-lxc-template [14:29] * rogpeppe runs lxc-destroy [14:30] bogdanteleaga: i've got an lxcbr0 network interface [14:30] bogdanteleaga: do you think i should remove that too? [14:31] rogpeppe, hmm, not sure, I'm really not familiar with lxc [14:31] rogpeppe, the only lxc machine I have seems to not create that [14:32] bogdanteleaga: alright thanks [14:33] ha, "destroy-environment -y local" still leaves me with an entry in environments/cache.yaml [14:33] with an empty key [14:33] try --force [14:33] bogdanteleaga: i did [14:33] bogdanteleaga: (sorry, i didn't mention that) [14:33] * rogpeppe removes cache.yaml [14:33] rogpeppe, I never actually saw a cache.yaml before [14:34] bogdanteleaga: you only get it with the jes feature flag [14:34] rogpeppe, that makes sense :) [14:36] ericsnow: natefinch: ready? [14:36] yep [14:40] bogdanteleaga: for future reference: looking in ~/.juju/local/log/machine-0.log is dead useful :) [14:41] rogpeppe, I'll cherish the day I get to use local and not worry about boringly long deployment times [14:42] bogdanteleaga: :) [14:46] bogdanteleaga: filed https://bugs.launchpad.net/juju-core/+bug/1494787 [14:46] Bug #1494787: bootstrap cannot be interrupted if machine agent fails to start [14:57] Bug #1494782 opened: should *-broken *-departed hooks run when a unit goes AWOL? [14:57] Bug #1494787 opened: bootstrap cannot be interrupted if machine agent fails to start [15:15] Bug #1494774 changed: MetricSenderSuite fails on ppc64el panic [15:15] Bug #1494798 opened: Juju fails to report it cannot create buckets [15:18] Bug #1494798 changed: Juju fails to report it cannot create buckets [15:18] Bug #1494774 opened: MetricSenderSuite fails on ppc64el panic [15:21] Bug #1494774 changed: MetricSenderSuite fails on ppc64el panic [15:21] Bug #1494798 opened: Juju fails to report it cannot create buckets [15:27] Bug #1455625 opened: TestStateWatcherTwoEnvironments fails [15:30] Bug #1455625 changed: TestStateWatcherTwoEnvironments fails [15:39] Bug #1455625 opened: TestStateWatcherTwoEnvironments fails [15:56] natefinch: hey can you update bug 1486553 with the latest status? [15:56] Bug #1486553: i/o timeout errors can cause non-atomic service deploys [16:09] review anyone for a critical fix? katco, ericsnow, etc? http://reviews.vapour.ws/r/2636/ [16:09] breaking for lunch === natefinch is now known as natefinch-afk [16:10] natefinch-afk: I'll take a look [16:35] https://bugs.launchpad.net/charms/+source/openstack-dashboard/+bug/1494829 [16:35] Bug #1494829: Support for custom panels [16:42] Bug #1494831 opened: Windows instances on GCE will have the same hostname [16:45] Bug #1494831 changed: Windows instances on GCE will have the same hostname [16:48] Bug #1494831 opened: Windows instances on GCE will have the same hostname [17:12] Bug #1494848 opened: 1.24+ cannot upgrade in canonistack [17:24] Bug #1494848 changed: 1.24+ cannot upgrade in canonistack [17:27] Bug #1494848 opened: 1.24+ cannot upgrade in canonistack === natefinch-afk is now known as natefinch [17:39] ericsnow: lol @ comment about using a struct for the params... i have code doing exactly that on my machine, but getting this fix in first. [17:39] natefinch: np :) [17:40] natefinch: it's just less churn overall if you do it in this patch [17:40] ericsnow: yeah, but this patch needs to be in ASAP. I was going to do it all together, but it turned out this fix was needed faster than we expected. [17:40] natefinch: k [17:41] natefinch: +1 [17:41] ericsnow: making a test for it right now [17:41] natefinch: thanks [18:04] katco: gah, 1.25 is blocked. [18:05] natefinch: hmm [18:07] mgz: ping? [18:09] katco: hey [18:09] mgz: we'd like to land a fix for bug 1486553 [18:09] Bug #1486553: i/o timeout errors can cause non-atomic service deploys [18:10] mgz: but master is blocked [18:10] mgz: thoughts on jfdi? [18:10] yeah, please don't [18:10] katco: 1.25 [18:10] look at the history of OS-deployer job [18:10] katco: (I mean, master is also blocked, but the bug is for 1.25) [18:10] natefinch: mgz: oops sorry, for 1.25 [18:10] fine on 1.24 and feature branches [18:10] screwed on 1.25 and master [18:11] it's already too hard to pin down cause because too much stuff was piled on [18:11] mgz: this is a fairly hot bug [18:11] katco: if 1.25 is broken currently, getting my fix in won't help get it to customers [18:11] sure, but we can't release in the current state [18:11] so it's not like that fix on 1.25 will get anywhere [18:12] mgz: I guess we're past the point of being able to revert whatever it is? [18:12] natefinch: master can be reverted back to some kind of sanity [18:12] Bug #1494864 opened: TestBlockChangeServiceUpdate fails on windows [18:12] Bug #1494868 opened: TestAzureWindows fails on wily and centos [18:12] natefinch: how hard would it be to get into 1.24? [18:12] Bug #1494870 opened: TestMeterStatusEvents fails on wily and vivid [18:13] but yeah, as no one is taking my suggestion on backing out broken changes we now have regressions without clear blame [18:15] mgz: ty for the input... we won't land in 1.25 right now. natefinch, just learned this fix is needed in 1.24.6, so let's land there [18:15] katco: even better. [18:15] mgz: http://cdn.meme.am/instances2/500x/1820980.jpg [18:23] very small review for a critical bug on 1.24.6: http://reviews.vapour.ws/r/2638/ [18:23] mgz: are wily and centos tests running with another go version? [18:24] bogdanteleaga: wily uses go 1.5 [18:25] sinzui: what version of go is on centos? [18:25] bug 1494868 above is really interesting [18:25] Bug #1494868: TestAzureWindows fails on wily and centos [18:25] it should fail everywhere [18:25] but it fails only on wily and centos [18:25] because the test doesn't get ran on other platforms [18:27] bogdanteleaga: that is interesting. [18:27] mgz: bogdanteleaga looking. I thought the test log printed that for us [18:28] sinzui: I see the juju version but not the go version [18:28] mgz: our python test runner doesn't do a go version like our bash version :( [18:28] * sinzui visits the machine [18:29] mgz: bogdanteleaga go version [18:29] go version go1.4.2 linux/amd64 [18:29] bogdanteleaga: thae windows-public-clouds branch was retested and passed, which further persuades me it's not the cause of recent breakage [18:30] sinzui: ta! [18:31] http://reviews.vapour.ws/r/2640/ [18:32] natefinch: http://reviews.vapour.ws/r/2639/diff/# is the same as the one that was targetted to 1.25? [18:32] mgz: well, it can't be since you got the same failures on master [18:32] mgz: and, afaik that didn't get in master yet [18:32] bogdanteleaga: we got so many issues on master I was unpersuaded of anything [18:32] :) [18:33] fwereade: thanks for the review [18:33] fwereade: I tried to make the changes without any changes to the external api - e.g. the allwatcher [18:33] fwereade: where empty address was used to signal no address set yet [18:33] fwereade: I think that's specifically been changed on master already though [18:34] fwereade: so the same work on master looks better [18:34] katco: yep [18:34] fwereade: a bunch of good suggestions though (especially the transaction testing) [18:34] fwereade: I have left a couple of replies, working through the others [18:34] natefinch: go for it [18:34] natefinch: and i could use a review for: http://reviews.vapour.ws/r/2638/ [18:35] katco: ok looking [18:35] that goes for anyone ^^ 22 line change [18:35] critical bug for 1.24.6 [18:36] bogdanteleaga: renderers.ToBase64 returns a string? [18:36] fwiw, you ought to get https://bugs.launchpad.net/juju-core/+bug/1493887 fixed on windows first [18:36] Bug #1493887: statusHistoryTestSuite teardown fails on windows [18:36] since it might break other tests [18:36] katco: lgtm [18:36] I had a mail about this kind of failure on the ml before [18:36] cherylj: hey what's the status on bug 1494356 ? [18:36] bogdanteleaga: yeah, there's a bunch of things on master I'm afraid [18:36] Bug #1494356: OS-deployer job fails to complete [18:36] mgz: it very well could return a string [18:37] mgz: I just wanted to use deepequals everywhere for consistency [18:37] I mean, does it? it's a function with a call value [18:37] mgz: now the tests runs on all platforms and it's good [18:37] mgz: yeah, think of it like a transformer [18:37] just want to avoid the ugliness of a mismatch on []uint8 [18:38] mgz: that needs everything to move from jc.DeepEquals to str(x), gc.Equals, str(y) [18:38] mgz: because some functions in those suites give back strings and some give back byte arrays [18:38] mgz: can't really remember which do which right now [18:39] ;_; [18:39] bogdanteleaga: lgtmed [18:39] mgz: wasn't the best idea in hindsight :) [18:39] mgz: 1.25 is blocked though, right? [18:40] bogdanteleaga: what you need to do is write a jc.StringEquals that'll do the string conversion for you :) [18:40] katco: I think she's hoping for more data on lxc specifics still, I'm going to rerun against 1.25 with that shortly [18:40] mgz: ah ok [18:40] bogdanteleaga: yep [18:41] natefinch: that sounds useful, yeah [18:42] bogdanteleaga: it's 50% useful and 50% horrible.... since it produces a very squishy test that can pass when it really shouldn't. [18:42] katco: yeah, what mgz said [18:42] :) [18:42] cherylj: k ty :) [18:43] natefinch: I'm actually wondering if contains would work if they're equals [18:43] cherylj: note that the test just passed on the windows-pulbic-clouds branch which is 1.25 as-of-a-few-revisinos-back [18:43] * bogdanteleaga goes to the playground [18:44] mgz: I'm wondering if the test is just taking a long time, as we've seen some of the containers come up in some of the test runs. [18:44] cherylj: that is certainly part of it. [18:45] mgz: I'm running some manual testing in canonistack and it took over an hour to download the image to create the template container [18:45] don't know if it could be related or not [18:45] natefinch: deepequals still doesn't test that they have the same type though [18:46] Bug #1494876 opened: TestFatalErrors fails on wily [18:46] but compare the 1.24 runs. they're either done in 35-40 mins, or hit the *internal* deployer timeout [18:46] Bug #1494887 opened: uniterV1Suite.SetUpTest [18:46] mgz: hmm, good point [18:46] the master runs are *still deploying units* an hour in when our external job timeout hits [18:47] ouch [18:47] so like, at minimum it's a 50% perf regression due to either our box, the network, (but not as of today), or the code in master [18:49] mgz: Is there any way to access the machines once the test completes? I'm wondering if we need to examine the containers to see what's going on [18:50] or are they immediately released? [18:50] cherylj: let me check the job, most of them have a flag we can set to not destroy-environment after [18:53] cherylj, sinzui: I am setting --keep-env on OS-deployer job [18:54] mgz: I hope you remember to undo it before you sleep :) [18:55] also setting failure-threshhold to 1 [18:55] mgz: I've dont that. Once the job starts, you can restore the script., then wai 40 minutes for the job to get to your point of investifation [18:55] as this one ties up most of our maas we really can't be doing other things at the same time [18:59] fwereade: hmmm... and yes, setting the preferred addresses on set rather than on read is better [18:59] fwereade: only nuisance is we have two setters for addresses. Ah well, still better [19:04] mgz: hopefully it won't take too long to see what's going on with the containers. [19:19] Bug #1494894 opened: TestWatchInterfaces fails on wily [19:23] katco: can I persuade one of you to revert the last change on master before the weekend? [19:23] the dep change broke like four things, I don't see a good reason to leave it in place [19:27] mgz: sec meeting... was it cmars patch? [19:28] mgz, commit hash please? [19:28] katco: I can pick that up ^^ if you want. Pretty trivial... from Rogpeppe & frankban [19:28] natefinch: yep +1... go for it [19:29] katco, cmars: http://reviews.vapour.ws/r/2606/ [19:29] mgz, what tests fail? can I see a log? [19:30] bug 1494441 bug 1494864 two more unrelated windows test failures and who knows what else after the build succeeds [19:30] Bug #1494441: ppc64el: cannot find package "encoding" [19:30] Bug #1494864: TestBlockChangeServiceUpdate fails on windows [19:30] mgz, ty [19:31] cmars: can you rubber stamp the revert? http://reviews.vapour.ws/r/2641/ [19:31] it's just a PR created with the revert button in github [19:31] natefinch, i'm going to look at the test failures first [19:31] cmars: so, the ppc64 build failure is 'not your fault' but prevents us doing proper testing [19:32] cmars: I've looked at the 1494441: ppc64el: cannot find package "encoding" one [19:32] we had a fix to ggcgo that for whatever reasons didn't get back into trusty-updates [19:34] cmars: what he said ^ also, the windows one looks like a pretty standard "Someone doing file moves/deletes before they close the file" in windows [19:34] mgz: still here? [19:35] natefinch, mgz done [19:35] perrito666: I am [19:35] mgz: how much do you know about mong ca files and stuff? [19:36] cmars: I will file other bugs from the results we got, but can address and reland easily enough next week [19:37] perrito666: not much of the detail [19:37] mmmpf, bad luck [19:37] * perrito666 tries to setup mongo3 and it seems to want to authenticate with ssl certs [19:38] aghh finally [19:38] --sslWeakCertificateValidation [19:39] and by weak they mean nil [19:40] perrito666: well, that sounds better than what I think we had before which is just a password-style key file [19:40] of some number of random bytes [19:40] mgz: I am trying to get juju to run on a minimal mongo 3 [19:40] we can implement certs later on [19:40] but with that option it should be the same as we have now [19:47] I really hate that JFDI requires __ JFDI__ because the underscores get hidden by markdown [19:47] I screw it up every time [19:48] WTF [19:49] I guess having __JFDI__ in a previous comment is not good enough. sigh [19:52] Bug #1494912 opened: TestHookContextEnv fails on windows [19:52] natefinch: this isn't a jfdi, it's a fixes-1494441 [19:55] mgz: it doesn't fix anything, it just backs out the change... I mean, I guess it sorta does, but I figured it might be better to leave the bug around for when the code actually gets fixed. [19:55] mgz: since we are in it, can we have fixes be a bit more permissive? [19:56] mgz: fixes does not remove the block, it just lets your merge pass [19:56] I meant natefinch [19:56] mgz: could we have it also take fix- fix_ and fixes_ ? [19:57] we can still use the bug [19:58] mgz: I guess I find the wording of "fixes" to be inaccurate in the case of just backing out a change... but maybe I'm being too pedantic. [19:59] that bug is really about the ftb with gccgo, which backing out the change does address. I agree that that thinks can get complicated when using all the features of version control. [20:07] well, this is fun. [20:13] voidspace, yeah, the two setters are a bit of a hassle [20:19] natefinch: did your patch merge? [20:21] katco: both seem to have. [20:22] Bug #1494913 opened: TestNoSpoolDirectory fails on windows [20:22] Bug #1494917 opened: TestEnvSetsPath fails on windows [20:22] mgz: ty [20:26] katco: yep [20:32] katco: what do you think about making the rest of my changes for the add service stuff to 1.25 or master? Or should I be trying to get the rest of it into 1.24 as well? [20:40] gotta run for a while, will check in later === natefinch is now known as natefinch-afk [20:40] natefinch: i'd say no [20:40] yeah, the other half is trickier, I'd prefer 1.25 or later [21:16] Bug #1494936 opened: imageSuite.TestDownloadEnvironmentPath [21:16] Bug #1494938 opened: Panic DeploySuite.TestConfig on wily [21:16] Bug #1494939 opened: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily [21:19] Bug #1494936 changed: imageSuite.TestDownloadEnvironmentPath [21:19] Bug #1494938 changed: Panic DeploySuite.TestConfig on wily [21:19] Bug #1494939 changed: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily [21:22] Bug #1494936 opened: imageSuite.TestDownloadEnvironmentPath [21:22] Bug #1494938 opened: Panic DeploySuite.TestConfig on wily [21:22] Bug #1494939 opened: Panic backupsSuite.TestAuthRequiresClientNotMachine on wily [21:31] Bug # opened: 1494947, 1494948, 1494949, 1494951 [21:34] Bug # changed: 1494947, 1494948, 1494949, 1494951 [21:37] Bug # opened: 1494947, 1494948, 1494949, 1494951 [21:43] Bug # changed: 1494947, 1494948, 1494949, 1494951 [21:46] Bug # opened: 1494947, 1494948, 1494949, 1494951 [21:54] f/quit [22:06] anyone still around that could give me a quick review? http://reviews.vapour.ws/r/2644/ [22:16] ericsnow: tal [22:18] ericsnow: so for now the channel never gets closed, but it doesn't matter b/c its lifecycle is the same as the process? [22:18] *agent process [22:29] katco: pretty much [22:29] ericsnow: what is the harm in having a defer close? [22:29] katco: also, william indicated that not closing the channel would be fine [22:29] ericsnow: ah wait, that would close it as the function exited [22:30] ericsnow: not as the workers died [22:30] katco: yep :) [22:30] ericsnow: +2, ship it. good work [22:30] katco: thanks [22:32] blech, currently 7 blockers on master :( [22:33] wtf happened [22:33] hi btw [22:33] :) [22:35] perrito666: o/ [22:35] ericsnow: wow [22:35] ericsnow: i thought there was only 1 and nate had removed it [22:36] katco: you got us back to our previous blockers :) [22:36] mgz: face palm [22:36] which was why I was keen on the revert [22:36] mgz: understood... ty for pushing us in the rigth direction [22:37] trying to unpick which were due to the dep update and which were due to maltese-falcon was causing me headaches [22:37] fun fact: the rigth direction is an early Gaelic belief that an undiscovered direction existed. later, it was recoined as the "right" direction [22:37] or, alternatively, i just can't type. [22:38] now you've removed the dep update from the confusion [22:38] good to hear