[00:14] <wallyworld> babbageclunk: i have to head out for a bit soon to take kid to doctor in case you need me
[00:14] <babbageclunk> wallyworld: no, I'm good for now
[00:45] <menn0> babbageclunk: bug 1641824 is fixed right?
[00:45] <mup> Bug #1641824: Migrating a model back to controller fails: model XXXX has been removed <model-migration> <juju:In Progress by 2-xtian> <https://launchpad.net/bugs/1641824>
[00:46] <babbageclunk> menn0: hmm - all but the last case.
[00:48] <babbageclunk> menn0: I need to chase down the stuff that calls the NewHandlerArgs.Connect function and ensure that it calls release on the state at some point. I tried a while back but got lost in all the component stuff.
[00:50] <menn0> babbageclunk: ah right. that rings a bell.
[00:50] <menn0> babbageclunk: critical for 2.1?
[00:51] <babbageclunk> menn0: oh hey, you fixed that bit to use my stateForRequestAuthenticatedTag func - that should make it easier.
[00:53] <menn0> babbageclunk: hooray :)
[00:53] <menn0> babbageclunk: that rings a bell too :)
[00:53] <babbageclunk> menn0: I guess so - state leak on any model that uses resources.
[00:53] <babbageclunk> menn0: sorry - I mean, I guess it's critical in that case.
[00:53] <menn0> babbageclunk: if you can find to take a look before the release goes out that would be awesome.
[00:55] <anastasiamac> babbageclunk: menn0: this week only beta release is going out (beta3), first week of Jan - rc1 (tentative), 2nd week final (tentative too)... just an fyi \o/
[00:56] <babbageclunk> menn0, anastasiamac: I'll take another look now.
[00:56] <menn0> anastasiamac: ok thanks
[01:00] <babbageclunk> menn0: Ok, I think I see how to do it now.
[01:03] <anastasiamac> menn0: thumper: Ci is still seeing this issue https://bugs.launchpad.net/juju/+bug/1620438
[01:03] <mup> Bug #1620438: model-migration pre-checks failed to catch issue: not idle <ci> <intermittent-failure> <regression> <juju:Fix Committed by thumper> <https://launchpad.net/bugs/1620438>
[01:03] <anastasiamac> the latest failure was on Dec 13.... on 2.1
[01:04] <anastasiamac> menn0: thumper: is there a backport that needed to happen?
[01:06] <menn0> anastasiamac: not sure when the fix was made. thumper ?
[01:07] <anastasiamac> menn0: last PR on the bug was merged 14 days ago...
[01:07] <anastasiamac> menn0: and since it went into develop... I am guessing the issue is not fixed :(
[01:08] <menn0> anastasiamac: or the test is trying to start a migration before the model has actually finished deploying
[01:09] <anastasiamac> menn0: http://reports.vapour.ws/releases/issue/57ce2d2b749a563a65a52631
[01:09] <menn0> anastasiamac: let's reopen it for now
[01:09] <anastasiamac> menn0: or that :)
[01:09] <menn0> so we don't forget
[01:10] <anastasiamac> menn0: doen
[01:10] <anastasiamac> done even
[01:21] <menn0> anastasiamac: that last resource migration PR landed btw
[01:21] <anastasiamac> menn0: \o/ (I saw)
[01:21] <anastasiamac> menn0: well done
[01:21] <babbageclunk> menn0: What's a charm I can deploy that uses resources?
[01:23] <menn0> babbageclunk: cs:~cmars/mattermost
[01:23] <menn0> babbageclunk: that actively uses them
[01:24] <menn0> babbageclunk: etcd uses a resource too but it's only tied to a specific action
[01:24] <menn0> babbageclunk: just a placeholder resource after deploy
[01:24] <menn0> depends what you want to test
[01:24] <babbageclunk> menn0: wow, the resources stuff doesn't have good test coverage, huh? I just changed the signature of several bits and still have a know nil pointer exception in my code but I can't make any of the tests fail.
[01:24] <babbageclunk> *known
[01:25] <menn0> babbageclunk: yep :(   I've found a bunch of places where there's no tests at all
[01:25] <menn0> babbageclunk: fixing one of those now while fixing a bug
[01:32] <anastasiamac> menn0: should bug 1649738 be targeted to 2.1.1? or later like 2.2?
[01:32] <mup> Bug #1649738: migrations should support renaming of models <model-migration> <juju:New> <https://launchpad.net/bugs/1649738>
[01:33] <anastasiamac> menn0: my understanding that 2.1.1 should b mainly bug fixes for 2.1.x rather than new functionality..
[01:33] <menn0> anastasiamac: 2.2 is more realistic given that it's potentially a big piece of work but alexis suggested 2.1.1
[01:34] <menn0> anastasiamac: depending on where model names are still used to tag things, it might be quite small/easy or big/horrible
[01:34] <anastasiamac> menn0: k. this means alexisb has a plan \o/ will go with her suggestion :D
[01:34] <anastasiamac> menn0: well, we are all about extremes nowdays - nothing in the middle ;)
[01:39] <alexisb> babbageclunk, validation complete :)
[01:39] <alexisb> thank you
[01:40] <babbageclunk> alexisb: yay!
[02:15] <menn0> thumper, anastasiamac or babbageclunk: https://github.com/juju/juju/pull/6702
[02:16]  * anastasiamac looking
[02:22] <menn0> thumper: so what do we want the policy to be wrt downgrades with migrations?
[02:23] <menn0> thumper: 1.2.4 to 1.2.3 is ok?
[02:24] <anastasiamac> menn0: lgtm
[02:24] <menn0> thumper: that is, only check major.minor?
[02:24] <menn0> anastasiamac: tyvm
[02:25] <anastasiamac> menn0: anytime (...almost) \o/
[02:26] <babbageclunk> menn0: to make mattermost use resources, do I need to deploy it with an overriding resource, or is just deploying it enough?
[02:26] <menn0> babbageclunk: with mattermost, deploying it is enough
[02:26] <babbageclunk> :(
[02:26] <babbageclunk> I can't get it to hit my problem code.
[02:27] <menn0> babbageclunk: the mattermost binary distribution is a resource, used during the install hook
[03:01] <wallyworld> menn0: thumper: is there a meeting today?
[03:01]  * thumper votes no
[03:01] <wallyworld> sgtm
[03:02] <menn0> wallyworld: I'd forgotten about it. I vote no as well.
[03:04] <thumper> menn0: re downgrade, I'd suggest patch only
[03:04] <thumper> so 2.0.3 -> 2.0.2
[03:04] <thumper> 2.1.0 -> 2.0.2 seems more dodgy
[03:05] <menn0> thumper: cool, that's what I've done.
[03:05] <thumper> menn0: we don't have a way to negotiate a version to talk to
[03:05] <menn0> thumper: basically, patch, build and tag are ignored
[03:05] <thumper> what if 2.0.3 modifies the descritpion format and 2.0.2 doesn't understand
[03:06] <menn0> thumper: 2.0.3 shouldn't do that
[03:06] <menn0> thumper: it's for bug fixes only
[03:06] <thumper> we should ensure that is the case then
[03:06] <menn0> thumper: the description format should arguably only be allowed to change if the minor version increases
[03:06] <thumper> something to add to a checklist
[03:07]  * thumper is testing HA pubsub branch
[03:07] <menn0> thumper: or we can allow downgrades only if the build or tag is different?
[03:07] <jam> menn0: did you still want to meet in an hour?
[03:07] <thumper> I like your first idea better
[03:07] <thumper> ensure that the descirption format doesn't change in bug fix releases
[03:08] <menn0> jam: i'm happy to skip. lots of little bits of tidy up for the 2.1 release.
[03:08] <jam> menn0: sgtm, hope you have a good day.
[03:08] <jam> btw, I agree with the "major.minor" stuff
[03:08] <anastasiamac> menn0: resources fix landed on 2.1... if ther is a chance plz forwardport to 2.2 (develop)
[03:08] <menn0> jam: and we only just had the sprint
[03:08] <jam> though we have *not* been good about keeping real differences out of the micro releases
[03:09] <menn0> anastasiamac: not forgotten. I have a list of branches to forward port and that's on it.
[03:09] <anastasiamac> jam: mayb it should b our NY resolution :D
[03:09] <anastasiamac> menn0: \o/
[03:09] <menn0> jam, thumper: i'm not sure how we robustly enforce it...
[03:10] <thumper> I'm not sure we can effectively...
[03:10] <thumper> could just be convention
[03:10] <thumper> and beatings
[03:11] <anastasiamac> a cycle on a team that supports users?
[03:12] <menn0> anastasiamac: that's just crazy talk...
[03:13] <menn0> so a checklist then ... where to keep it?
[03:14] <anastasiamac> menn0: part of review checklist? along with the item of 'did u consider upgradability?'
[03:14] <menn0> anastasiamac: but it's more of a thing to check at review time
[03:14] <menn0> anastasiamac: when commiting a PR you don't always know which version of Juju your change is going to land in
[03:15] <menn0> thumper, jam: there's a problem with relaxing the migration version check: post-migration you end up with a model with agents that are running tools ahead of the controller
[03:15] <anastasiamac> menn0: hmmm if only we had some set of rules that could check codebase...
[03:15] <thumper> menn0: no...
[03:16] <thumper> menn0: we shouldn't support that
[03:16] <thumper> consider this
[03:16] <thumper> migrating from 2.0.2 -> 2.0.3 controller
[03:16] <thumper> the model doesn't change
[03:16] <thumper> it is still 2.0.2
[03:16] <thumper> you can migrate it back then
[03:16] <thumper> but if you upgrade the model
[03:16] <thumper> nada
[03:16] <thumper> sorry
[03:16] <thumper> no move back for you
[03:17] <menn0> thumper: well that's already supported as it is now, without my PR
[03:18] <thumper> that is what we need to support...
[03:18] <thumper> I don't think we should support other than that
[03:18] <menn0> thumper: ok... well that works right now
[03:20] <menn0> thumper: what's missing is that we don't check controller versions, only the model version to the target controller version
[03:20] <menn0> thumper: there's a gap there where the model might be compatible with the target controller but the source controller is ahead of the target controller, meaning that migration API support might be missing
[03:20] <menn0> thumper: fixing that now
[03:22] <thumper> ok...
[03:22] <thumper> but ...
[03:22] <thumper> hmm...
[03:23] <thumper> so testing that target controller version >= source controller version, or just patch levels behind, yes?
[03:23] <thumper> menn0: ^^ that
[03:23] <menn0> thumper: quick HO?
[03:23] <thumper> sure
[03:28] <babbageclunk> menn0, thumper: could one of you take a look at https://github.com/juju/juju/pull/6703
[03:29] <babbageclunk> It fixes the resource state leak.
[03:31] <babbageclunk> I'mm'a go for a run
[03:31]  * babbageclunk goes for a run
[03:43] <babbageclunk> gah, no I'm not - still doesn't work
[03:45] <wallyworld> babbageclunk: i'll have a PR ready for review a bit later, after your EOD. if you could look when you start tomorrow that would be greate
[03:45] <babbageclunk> wallyworld: wilco
[03:46] <wallyworld> babbageclunk: it's to change how register remote relation works so we can remove a hack needed to lookup the remote app id on the consuming side
[03:47] <anastasiamac> wallyworld: have u seen this one? remoteRelationsSuite.TestRemoteRelationsDead got nil instead of changes: https://bugs.launchpad.net/juju/+bug/1646861
[03:47] <mup> Bug #1646861: remoteRelationsSuite.TestRemoteRelationsDead got nil instead of changes <ci> <intermittent-failure> <regression> <unit-tests> <juju:Triaged> <https://launchpad.net/bugs/1646861>
[03:47] <wallyworld> that got fixed last week IIANM
[03:48] <anastasiamac> wallyworld: do u have a PR? and do u know what branch it landed on?
[03:48] <wallyworld> develop
[03:48] <anastasiamac> before we branched?
[03:49] <wallyworld> https://github.com/juju/juju/pull/6685
[03:49] <wallyworld> no idea
[03:49] <wallyworld> maybe after
[03:49] <anastasiamac> according to http://reports.vapour.ws/releases/issue/58418a80749a5656beeae59f, it was seen on Dec 12 on 2.1
[03:50] <wallyworld> must have been after then
[03:50] <wallyworld> backport time
[03:50] <anastasiamac> could u plz backport to 2.1? u may need to consider if it needs to b on 2.0 too
[03:50] <anastasiamac> \o/
[12:19] <voidspace> jam: ping
[12:19] <jam> voidspace: ?
[12:20] <voidspace> jam: hey, you said you thought you'd seen code explicitly discarding constraints  when there is placement
[12:20] <voidspace> jam: above the container creation level
[12:20] <voidspace> jam: and indeed the bundledata spec explicitly states this to be the case (but we'd like to change it)
[12:20] <voidspace> jam: I wondered if you recalled whereabouts you'd seen this code?
[12:21] <jam> voidspace: checking
[12:21] <voidspace> jam: I don't *think* the charm package itself discards this information
[12:25] <jam> voidspace: I don't see it right now. It was just something I came across in the past, might have been in lots of places as I've been digging in a lot of code lately.
[12:25] <voidspace> jam: ok, no problem
[12:26] <voidspace> jam: I'll keep digging
[12:26] <voidspace> jam: it is explicitly documented in charm bundledata - so I'll construct a test to see if it does come out of that package
[12:33] <jam> voidspace: I didn't think it was there, I thought it was somewhere like worker/provisioner
[12:59] <voidspace> jam: rick_h: juju deploy ubuntu --constraints="mem=888M" --to kvm:0
[12:59] <voidspace> jam: rick_h: the constraint is honoured and works
[12:59] <voidspace> jam: rick_h: definitely bundle specific
[13:39] <jam> voidspace: good to know, sad to hear :)
[14:05] <alexisb> perrito666, ping
[14:11] <perrito666> alexisb: pong
[14:11] <perrito666> sorry was taking a pill because yesterday I used my back in the wrong way
[14:12] <perrito666> plus my internet is down :p good thing I have a backup internet
[14:12] <perrito666> feels like monday
[14:17] <alexisb> perrito666, it is monday for you isnt it?
[14:17] <perrito666> it is, nad I have not had a Monday so Monday in months
[14:18] <alexisb> perrito666, to help improve your monday...
[14:18] <alexisb> I have a bug for you
[14:18] <alexisb> https://bugs.launchpad.net/juju/+bug/1640210
[14:18] <mup> Bug #1640210: Restore-backup model is not usable because upgrade in progress <ci> <intermittent-failure> <regression> <restore-backup> <juju:Triaged> <https://launchpad.net/bugs/1640210>
[14:18] <perrito666> also something triggered my differencial breaker in the office so after EOD ill have to run a full diagnostic to make sure nothing is leaking current
[14:18] <alexisb> your favorite kind of bug
[14:19] <alexisb> perrito666, please dont burn your new house down
[14:19] <perrito666> alexisb: lol, lovely, Ill jump on it since my pending work from the sprint is awaiting for axw's patch to merge
[14:20] <alexisb> I knew you would appreciate that bug ;)
[17:32] <voidspace> wallyworld: ping - don't suppose you're around yet?
[17:41] <perrito666> brb, relocation
[17:42] <perrito666> voidspace: he will be here in about 5 hs
[17:43] <alexisb> voidspace, wallyworld typcially starts around 9PM UTC
[17:46] <voidspace> alexisb: thanks
[17:46] <voidspace> perrito666: I guess I'll catch him later tonight
[17:46] <voidspace> I have questions about the bundlechanges packages
[17:46] <katco> voidspace: it's a lie; he is omnipresent
[17:46] <voidspace> haha
[17:46] <katco> voidspace: he's watching right now
[17:46] <voidspace> katco: that would be nice...
[17:47] <jam> frobware: voidspace: do you know if we ever implemented the default space as a configuration setting?
[17:47] <voidspace> no-one has much experience with bundlechanges, but as usual it's more wallyworld's fault than anyone else
[17:47] <voidspace> jam: I don't believe so
[17:47] <jam> I'm wondering if "machine.AllSpaces" should be returning the default space if nothing else has been specified
[17:48] <voidspace> jam: it would be better for us always to be explicit about spaces
[17:49] <voidspace> jam: so machine.AllSpaces can always tell the truth
[17:50] <jam> voidspace: well at some point we need to do *something* when requesting a container or machine that doesn't have a "--bind" or "--constraint space=" set
[17:50] <jam> so *something* has to determine that the container/machine needs to go in the default space
[17:51] <jam> voidspace: is there a bit of code that knows about the default space, or is it just that we let MAAS/EC2 give us a machine, which can be in any subnet/space ?
[17:51] <jam> voidspace: theoretically there was supposed to be a default space that you would bootstrap into (detected at bootstrap time if nothing else supplied)
[17:52] <jam> the extra cheap has is that it is the one that is named "default", but that especially feels bad on MAAS where you want to name them something meaningful to you
[17:52] <voidspace> jam: my goodness, this was a while ago and you're making me think
[17:52] <voidspace> jam: yep, on maas you should be able to specify which is the default
[17:53] <voidspace> jam: I don't think we *enforce* the restriction that every machine must be in "the controller space", we just assume that everything is routable
[17:54] <jam> voidspace: right, but there should also be a default space that applies to all machines when you don't specify something
[17:54] <voidspace> jam: for ec2 we always have a default space and we don't let you remove spaces
[17:54] <jam> which is not the controller space
[17:54] <jam> but if you specify *nothing* then controller = default = whatever we bootstrap into
[17:54] <voidspace> yep
[17:54] <jam> voidspace: but is that *named* default, or is it a named space that we treat as default ?=
[17:54] <jam> named "default"
[17:55] <voidspace> jam: bah, so my understanding was a named space called "default" as it wasn't configurable
[17:55] <voidspace> jam: I may be incorrect I'm afraid though
[17:56] <voidspace> jam: gah, it's near EOD and I have my head in the bundlechanges code - I ought to be able to navigate this though
[17:57] <jam> voidspace: sorry to distract you. good luck
[17:57] <jam> voidspace: able to trace the calls through?
[17:57] <voidspace> jam: no problem, I'm annoyed it isn't clearer
[17:57] <jam> (for containers, if you haven't specified anything, but end up on a machine, if *it* is in a single space, then it seems ok to just use it)
[17:58] <voidspace> yep, that has to be true
[17:58] <jam> but that feels more like it should have only picked a machine that would have fit in the first place
[18:46] <natefinch> rick_h, katco: currently add-credential requires a parameter specifying the cloud to which you're adding a credential.  Do we want to make that optional?  It would be more consistent with add-cloud if you could run interactive with zero args
[18:47] <rick_h> natefinch: not at the moment
[18:47] <rick_h> natefinch: for now let's leave that part
[18:47] <natefinch> rick_h: yeah, outside the scope of this PR, you're right
[18:47] <rick_h> natefinch: i agree that in interactive mode that's the consistent work we want, but there's bigger fish to fry atm
[19:13] <fengxia41103> Any document on developing juju provider?
[19:15] <perrito666> back
[19:16] <redir> fengxia41103: There's this https://github.com/juju/juju/wiki/Implementing-environment-providers
[19:19] <natefinch> ruh roh  juju.tools.lxdclient client_instance.go:278 while removing instance "juju-e2f2ef-0": Failed to destroy ZFS filesystem: cannot open 'lxd-pool/containers/juju-e2f2ef-0': dataset does not exist
[19:21] <natefinch> hmm... that might be fixed by now, realized this is an old test
[19:21] <natefinch> er old test run
[19:59] <natefinch> mgz, sinzui: is there something wonky with the representative tests?
[20:00] <natefinch> abentley: ^
[20:00] <natefinch> http://juju-ci.vapour.ws/job/github-check-merge-juju/441/
[20:00] <mgz> natefinch: they have sadly been pretty wonky for a while
[20:00] <mgz> anything in particular? I'll look.
[20:00] <natefinch> 19:30:24 ERROR cmd supercommand.go:458 failed to bootstrap model: refreshing addresses: instances not found
[20:01] <mgz> oh, that message again... that's a new(ish) thing masking real problems
[20:02] <mgz> natefinch: means the lxd container didn't come up
[20:02] <mgz> natefinch: machine is probably full or similar again
[20:02] <mgz> natefinch: request, can you send a message to a list, any list, mentioning that the check job is failing your branch?
[20:03] <mgz> I've been fixing this stuff as people mention it and I think the overall message about things being screwed has not propogated upwards
[20:05] <redir> brb reboot
[20:18] <abentley> sinzui: could you please review https://code.launchpad.net/~abentley/juju-ci-tools/manual-endpoint-xfail/+merge/313274 ?
[20:25] <natefinch> mgz: will do
[20:38] <abentley> mgz: Do you suppose it's because the representative tests can run concurrently?
[20:46] <redir> how does one relate application in different models?
[20:46] <redir> applications
[20:46] <mgz> abentley: I think that is certainly a factor
[20:48] <abentley> mgz: test_check_token_win_remote_failure is failing on my machine.  Is this due to your "OSX/Windows client tests now more useful" changes?
[20:53] <rick_h> redir: that's the cross model relations work that wallyworld is driving and is behind a feature flag
[20:53] <rick_h> redir: what makes you ask?
[20:54] <redir> rick_h: OCR trying to verify QA but I don't know the spelling for making that relation.
[20:54] <redir> rick_h: on a CMR bit wallyworld has a PR for
[20:54] <rick_h> redir: juju relate model/application:endpoint I think
[20:55] <redir> figured I'd dig up the spec if the lazy IRC didn't help
[20:55] <redir> ahh / I tried :
[20:55] <redir> but that's already used, duh.
[20:58] <redir> doesn't work. I bet I need to run with a feature flag or something
[20:59] <rick_h> redir: yea, need to have the FF enabled, probably at bootstrap time
[20:59] <wallyworld> redir: rick_h: that syntaxt isn't used yet. for now you 1. offer "juju offer mysql:db local:/u/me/mysql" and 2. relate "juju relate wordpress local:/u/me/mysql". steps 1 and 2 are done in different models
[20:59] <rick_h> wallyworld: doh! ok I wasn't sure
[20:59] <wallyworld> tis ok, all wip
[20:59] <redir> wallyworld: what's the FF magic incantation?
[21:00] <wallyworld> ff is called "cross-model"
[21:14] <babbageclunk> wallyworld: sorry, still going through yours - thumper tried to trick me into looking at one of his, he was all "he's asleep, he won't mind"
[21:14] <wallyworld> lol
[21:16] <babbageclunk> Alice is taking the baby birds we found in our Christmas tree to the SPCA.
[21:16] <redir> Nice
[21:24] <natefinch> mgz, abentley, sinzui: is there a fix for the representative tests machines?  I can't land stuff right now because I don't know if the representative tests pass.  I mean, I guess I could just ignore it and try to merge anyway, but that seems bad.
[21:25] <rick_h> natefinch: what branch is this?
[21:25] <redir> babbageclunk: are you looking at 6707
[21:25] <redir> ?
[21:26] <natefinch> rick_h: the add cred updates and model status stuff
[21:26] <rick_h> natefinch: so the add-cred updates we were going to hold until beta3 is tagged?
[21:27] <natefinch> rick_h: right, right, sorry, got distracted by the test failures
[21:27] <rick_h> natefinch: all good
[21:27] <rick_h> natefinch: might as well hold both at this point since we're looking to tag just to not introduce anything the day of please
[21:27] <rick_h> natefinch: and that'll give folks time to look and correct things
[21:27] <natefinch> rick_h: sure thing
[21:27] <rick_h> natefinch: ty for the email
[21:28] <babbageclunk> redir: yeah, wallyworld emailed me it last night
[21:30] <redir> oh
[21:31]  * redir stops looking
[21:32] <wallyworld> redir: sorry, i thought you we almost done and when babbageclunk stood me up in favour of thumper i figured you would come to the rescue :-)
[21:32] <redir> well QA checked out
[21:33] <wallyworld> good cause it worked for me too
[21:33] <redir> and I got as far as that one comment.
[21:34] <redir> but I know babbageclunk is working on CMR with you so prolly more useful to have him looking at it
[21:34] <wallyworld> yeah
[21:34] <natefinch> trivial port anyone? https://github.com/juju/juju/pull/6710    +10 -40, exactly same code merged into 2.1
[21:35] <anastasiamac> natefinch: ports do not need review unless they r vastly different from original
[21:35] <natefinch> anastasiamac: cool
[21:35] <anastasiamac> natefinch: self-stamp :D
[21:42] <alexisb> wallyworld, ping
[21:42] <wallyworld> yo
[21:42] <alexisb> do you mind if we meet early for our 1x1?
[21:43] <alexisb> I am ready anytime
[21:43] <wallyworld> alexisb: sure, give me 10?
[21:43] <alexisb> yep meet you in the HO
[22:32] <babbageclunk> wallyworld: reviewed, sorry for the delay!
[22:32] <wallyworld> np at all ty
[23:14] <wallyworld> babbageclunk: changes pushed
[23:32] <perrito666> I am getting a few mins late to standup caught in traffic
[23:33] <thumper> perrito666: no standup today
[23:34] <perrito666> Oh didn't know, why?
[23:35]  * perrito666 stops driving like a mad man
[23:35] <perrito666> Irc on the phone is fantastic for traffic jams
[23:35] <thumper> perrito666: due to not many people
[23:37] <veebers> thumper: hah, the one time since I'm back that I remember about the standup and it's not happening :-)
[23:44] <redir> well looks like bluejeans isn't happening either
[23:44] <perrito666> I wanted to try my new webcam :p
[23:47] <redir> so maybe bluejeans is working fine, but chromium 53 is not.
[23:47] <menn0> redir: i'm on chromium 53 and bluejeans appears to be working
[23:47] <redir> menn0: don't update
[23:49] <redir> or something. Appears related to https://sslmate.com/blog/post/ct_redaction_in_chrome_53
[23:49] <redir> which is definitely happening for me on other sites (smile.amazon.com)
[23:50] <redir> and if I look at the network requests when loading bluejeans I see that error too
[23:50] <redir> this started after I updated and rebooted today.
[23:53] <anastasiamac> menn0: redir: chromium did not work for me with bluejeans. had to use chrome :D otherwise i had no sound
[23:58] <redir> are we not having standups this week or just today?