/srv/irclogs.ubuntu.com/2015/08/28/#launchpad-dev.txt

cjwatsonwgrant: Does my amendment to https://code.launchpad.net/~cjwatson/launchpad/delay-ppa-publication/+merge/269090 look OK?08:40
cjwatsonwgrant: Also, want me to do your pending QA?08:40
wgrantcjwatson: Ah, if you could.08:40
wgrantSorry, been distracted the last couple of days...08:41
wgrantThat MP looks better now, thanks.08:41
cjwatsonOK, thanks.08:42
cjwatsonwgrant: I seem to get "URL not allowed" surprisingly often08:52
cjwatsone.g. http://lies.example.com/ resulted in that08:52
cjwatsonWhen I'd have expected "DNS lookup failed"08:52
wgrantHm.08:53
cjwatsonI mean, it's not actually breaking AFAICS, just surprising.08:53
wgrantYeah08:54
wgrantI guess it falls afoul of the IP address restrictions because it has none.08:54
cjwatsonAh, could be.08:56
wgrantI'll need to refactor the rules to remove the positive dst assertion, I think.08:56
cjwatsonhttp://www.ubuntu.com/ also gave me "URL not allowed" but that's more understandable.08:56
wgrantWhich is possible if they get split up, I think.08:56
wgrantRight, that is intended.08:56
wgrantI expected the DNS error to happen before the ACL check, TBH.08:57
cjwatsonTrying to think of a way to provoke a different error without actually having to bother setting up my own endpoint.08:57
wgrantYou can get connection errors by using a host that doesn't listen on HTTPS.08:58
wgrantOr HTTP.08:58
cjwatsonOh that's true08:58
wgrantHas to be port 8008:58
wgrantAnd HTTPS is dodgy because of httplib, so 80 is better to test.08:58
cjwatsonwgrant: https://oops.canonical.com/?oopsid=OOPS-86856e3812ab2bada21cf3f23ab8f83b09:01
cjwatsonThough apparently not a regression.09:01
wgrantHrmph.09:01
wgrantDid you provoke a timeout?09:01
wgrantIt indeed shouldn't OOPS.09:02
cjwatson(That's from trying my ADSL, riva.dynamic.greenend.org.uk, which doesn't listen on HTTP but also apparently doesn't actually reject it)09:02
wgrantAh.09:02
wgrantRight.09:02
cjwatsonUseful misconfigurations FTW09:02
cjwatsonAnyway, qa-ok since that's a pre-existing bug09:03
cjwatsonShall I file a bug?09:03
wgrantPlease do.09:04
wgrantcjwatson: https://code.launchpad.net/~wgrant/launchpad/bug-1489674/+merge/26948009:05
cjwatsonwgrant: https://bugs.launchpad.net/launchpad/+bug/148979209:08
mupBug #1489792: WebhookClient.deliver crashes if the endpoint times out <fallout> <oops> <Launchpad itself:Triaged> <https://launchpad.net/bugs/1489792>09:08
wgrantThanks09:08
cjwatsonwgrant: Mystifying, why is to_person ever a team there, let alone a private one?09:09
wgrantcjwatson: If the team has an email address.09:09
cjwatsonOh, right.09:09
cjwatsonAnd we don't need this in BaseMailer too?09:09
wgrantBaseMailer already seems to touch other attributes without rSP09:10
cjwatsonIt does, but I wonder if it has hitherto only been called from scripts09:10
wgrantSo I thought it must have done it globally somewhere else.09:10
wgrantThat is possible indeed.09:10
cjwatsonOne of these days the word order in ZopelessDatabaseLayer vs. DatabaseFunctionalLayer will stop confusing me.  Or I'll crack and rename one of them.09:12
wgrantZopelessDatabaseLayer needs to be renamed for two reason.09:12
cjwatsonwgrant: Anyway, r=me but I should check whether any of my BaseMailer conversions are potentially affected.09:12
cjwatsonI think team-mail for example can go wrong if you renew a team membership and one of the admins of the team is an inaccessible private team.09:16
wgrantYep09:16
cjwatsonget_recipients does rSP but BaseMailer doesn't.09:16
cjwatsonCan you think of any reason not to plaster rSP over all recipient attribute accesses in mailers?09:17
cjwatsonWith BaseMailer, it's always a separate mail to each recipient so there should be no leakage.09:18
wgrantIndeed.09:22
wgrantIdeally you could do it higher.09:22
cjwatsonMaybe in get_recipients?09:28
wgrantThat might not help with eg. the rationale calculation in TeamMembershipMailer.09:31
cjwatsonWhich bit of it?09:32
wgrantIt unusually grabbed the displayname directly for something.09:33
wgrantOne of the templates had %%(blahblah)s because it was formatting the format stirng.09:33
cjwatsonforExpiringMembership does admin.unique_displayname, if that's what you're thinking of09:34
cjwatsonThe stuff in TeamRecipientReason is fine because it always refers directly to the member or the team being operated on, rather than other members/admins of the same team; and when performing one of these operations you always have access to both the member and the team at hand.09:35
cjwatsonteam.teamowner is used, but that's constrained to be a public person.09:35
wgrantEeh.09:36
wgrantIndeed, probably safe.09:36
cjwatsonIt's true that forExpiringMembership would need its own handling as well.09:36
cjwatsonBut it actually needs some special handling no matter what, because it tells you the names of the team's admins.  If you're in the bizarre situation of being a member of a team with some admins you aren't allowed to know about, the expiring membership mail shouldn't tell you09:37
cjwatson(Is this really a possible setup?)09:38
=== mup_ is now known as mup

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