[08:37] <thumper> wahay
[08:37] <thumper> just got merge proposal 110000
[08:37]  * thumper does a little dance
[08:38] <seb128> hey
[08:38] <seb128> I nomited https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/711413 for some ubuntu series and it seems to have "broken" it
[08:38] <ubot5`> Ubuntu bug 711413 in ubuntu-sso-client (Ubuntu Quantal) "ubuntu-sso-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-zPW5jjeWfI: Connection refused" [High,Triaged]
[08:39] <seb128> like it keeps timeouting since
[08:39] <seb128> is that a known issue?
[08:40] <czajkowski> seb128: what oops are you seeing
[08:40] <czajkowski> I'm just triaging something similar here for another bug
[08:40] <seb128> (Error ID: OOPS-
[08:40] <seb128> 7a4ed505a6a7ca6b4f403f75264c0ac9
[08:40] <seb128> )
[08:40] <seb128> is the one I just got
[08:40] <seb128> czajkowski, can you load this page?
[08:40] <czajkowski> seb128: which page?
[08:41] <czajkowski> seb128: the bug you listed, yes
[08:41] <seb128> czajkowski, right, 711413, it doesn't timeout for you?
[08:41] <czajkowski> nope
[08:41] <seb128> czajkowski, 477d0110a8c8ada4c07a637a43d0a030 is another oops number I got
[08:42] <czajkowski> seb128: https://bugs.launchpad.net/launchpad/+bug/1012309
[08:42] <ubot5`> Ubuntu bug 1012309 in Launchpad itself "timeout when attempting to add a distrotask to a new bug" [Critical,Triaged]
[08:43] <seb128> czajkowski, right, it's not only "when attempting to", in fact the adding worked, it's "impossible to add once ..."
[08:43] <seb128> like I can't load that bug since I nominated it for precise
[08:43] <seb128> czajkowski, thanks
[08:44] <czajkowski> wgrant: ^^
[08:44] <seb128> czajkowski, wgrant: that's a blocker for distro
[08:44] <seb128> it's screwed LTS work
[08:44] <seb128> screwing
[08:44] <czajkowski> seb128: annoying as it sounds, it's loading for me but I have seen some people say they cant load some pages when others can
[08:44] <seb128> like I can't load bugs that are nominated for precise
[08:45] <seb128> did you guys reduce timeouts delay recently?
[08:45] <czajkowski> seb128: not that I know of no.
[08:46] <seb128> ok, somebody on #ubuntu-bugs mentioned that yesterday
[08:46] <seb128> mdeslaur said he wasn't able to get any work done because launchpad keeps timeouting, I guess that's when he opened the bug you should pointed
[08:46] <seb128> czajkowski, wgrant: do you have any idea how long it's going to have it looked at?
[08:47] <czajkowski> seb128: maintence squad look at them but there are already a lot marked critical
[08:49] <seb128> czajkowski, well that one started recently and is breaking ubuntu security team and LTS team work, how can we escalate it?
[08:50] <czajkowski> seb128: let me just find out
[08:51] <wgrant> It's mostly because it has a lot of dupes, it seems.
[08:51] <wgrant> czajkowski: That bug is unrelated
[08:52] <seb128> wgrant, hum, it was loading fine before I nominated it for precise
[08:52] <seb128> but maybe I got lucky on the first try
[08:55] <wgrant> seb128: 1012309 is specifically about nomination approval timing out.
[08:55] <wgrant> Which this clearly is not.
[08:55] <wgrant> It's rendering just under the timeout for now. The OOPS ID you gave shows a 2ms query randomly taking 500ms, possible due to Python sucking at threading.
[08:57] <seb128> wgrant, both 7a4ed505a6a7ca6b4f403f75264c0ac9 and 477d0110a8c8ada4c07a637a43d0a030 are the same issue?
[08:57] <seb128> wgrant, well, the nomination timeouted and since I can't reload the bug at all
[08:57] <seb128> b2a034d4b516aa0bb1c5aa4cc1725851 this time
[09:18] <wgrant> seb128: We've increased the bug page timeout so that should just be slow rather than broken.
[09:18] <seb128> wgrant, I can load that page against, thanks a lot!
[09:18] <seb128> doh, against->again
[16:54] <joey> czajkowski: matsubara - howdy, I'm sure there is a bug against LP to allow the same email address to be used for multiple teams but I can't find one.  Any ideas?
[16:55] <czajkowski> joey: ello, you do come up with some dooseies! :)
[16:55] <czajkowski> lemmie go and see
[16:58] <czajkowski> joey: no such luck found https://bugs.launchpad.net/maas/+bug/950804  but not teams :/
[16:58] <ubot5`> Ubuntu bug 950804 in MAAS "Same email address for multiple users" [High,Fix released]
[16:58] <czajkowski> matsubara: ping
[16:58] <joey> czajkowski: thanks.  So the use case is that the ~linaro-sysadmins managed a number of teams and all the adds and removes during normal operations go to users and not to the sysadmins
[16:59] <joey> czajkowski: so I get questions about "what does ~linaro being made a member of ~linaro-lava-access mean to me and why did I get this email"
[16:59] <czajkowski> nods
[17:00] <joey> czajkowski: I want the standard sysadmin email to be in use as the email contact for all those teams
[17:00] <czajkowski> and it won't let you?
[17:09] <joey> czajkowski: right it won't because I used it for another team
[17:09] <czajkowski> sinzui: have you seen any issue like this before or is there a work around?
[17:11] <sinzui> czajkowski, joey. No. Emails cannot be shared. You can register a zillion alias at the mail provider, and then register each alias for a team
[17:13] <czajkowski> joey: see sinzui knows all
[17:14] <joey> sinzui: yeah for me that means google apps alias
[17:14] <joey> sinzui: is there any particular reason that's still valid for that restrictive behaviour?
[17:15] <joey> sinzui: email addys aren't used as a key in the table is it?
[17:15] <sinzui> allows teams to share unique identification information leads to untrust and is an attack vector
[17:16] <sinzui> We pondered removing team email addresses since we know a team does not have full control over it's email address
[17:17] <joey> sinzui: well in this case I only care about notifications to the team NOT going to the team members but to somewhere else
[17:18] <sinzui> joey, yes. I think the issue here is that we may want Lp to only send notification to team admins.
[17:20] <joey> sinzui: THAT would be my ideal, yes
[17:20] <sinzui> adding a member, admin, or none option may improve lp performance since sending to members can be very expensive
[17:20] <joey> sinzui: because my the OWNER of my teams is the same team (~linaro-sysadmins) and it uses the email address I want to use as the contact
[17:21] <sinzui> ah, that would work
[17:21] <dobey> +1 for admin/owner notifications instead of all members
[17:24] <sinzui> joey, dobey I am reporting this issue. We have a request to only send to members (which I think i bogus). Supporting admins only seems to also fix the root issue of why users want to reuse email addresses.
[17:27] <joey> sinzui: +1 on that
[17:27] <joey> sinzui: so, you know me too well, answer the next question I'm going to ask :-)
[17:28] <sinzui> joey. I do not know. I have friday to do what I want. I need to make a case that this is either a performance fix, or this is actually a part of disclosure...
[17:28] <sinzui> joey, are you concerned that members are seeing confidential information?
[17:29] <joey> sinzui: thanks. :-)  No security concerns on my end, just annoyance from users at LP spam
[17:29] <joey> sinzui: if that issue is a bug can you please tag it with  "linaro" and sub me to it please?
[17:29] <joey> pretty please with sugar on top
[17:30] <sinzui> okay. I will discuss this with the purple squad. wgrant may see a security benefit for this change. We certainly would get a performance benefit
[17:30] <joey> yeah definitely on performance.  Right now any change I make emails ~280+ people at least once vs just 1 email address (which is a  non-LP list0
[17:32] <dobey> although, i do like that changes to bugs where teams are the driver/bugmaster/subscribed/whatever, mails all members
[17:32] <joey> sinzui: I could envision a scenario for private teams where security might be an issue
[17:33] <dobey> but it is also annoying
[17:33] <joey> sinzui: but my scenerio there is an edge case I think
[17:35] <sinzui> dobey, right. I think the issue here is that there are cases where users must be members of team to have permission, but the members do not necessarily need/want all emails to the team. Lp rarely distinguished between an issue that only concerns the admin and one that concerns the members.
[17:37] <dobey> right
[17:40] <joey> emphasis on rarely
[17:41] <joey> sinzui: you could also make the subtle claim that LP notification spam is detracting from the user experience and overall happiness with LP
[17:42] <sinzui> We all believe that.
[18:13] <matsubara> joey, I think this might be related to your issue: https://bugs.launchpad.net/launchpad/+bug/156340
[18:13] <ubot5`> Ubuntu bug 156340 in Launchpad itself "Need to be able to associate multiple email addresses with a team" [Low,Triaged]
[18:14] <matsubara> but I'm not really here anymore :-)
[18:14] <matsubara> and forgot to afk myself
[18:48] <lifeless> joey: you might want to hang out in #launchpad-dev
[18:58] <joey> lifeless: is that an invitation or a threat? :-)
[18:59] <lifeless> joey: yes.
[19:00] <lifeless> joey: 06:31 < lifeless> sinzui: bug 1012787 - what mails are going to the team membership ? {I'm wondering if its unneeded complexity and that the actual problem is unnecessary notification emails/implicit subscriptions}
[19:00] <ubot5`> Launchpad bug 1012787 in Launchpad itself "cannot team restrict emails to go to the team admin" [Low,Triaged] https://launchpad.net/bugs/1012787
[19:00] <lifeless> 06:38 < sinzui> lifeless, joey can provide example of emails that he does not want members to get
[19:00] <lifeless> joey: thrilling discussion you missed out on.
[19:00]  * joey sighs. "Ok brt"
[19:09] <czajkowski> joey: you got sorted then :)
[19:10] <joey> czajkowski: Hi. heh... well not yet sorted but the right people with the right talent are thinking about it.
[19:10] <joey> czajkowski: it's a headache for me but it's not the end of the world for LP you know
[19:10] <joey> czajkowski: so I'm grateful for them reviewing it
[19:10] <czajkowski> excellent
[20:35] <scientes> any way i can subscribe to uploads here: https://launchpad.net/~xorg-edgers/+archive/ppa
[20:35] <scientes> like i can to debian BTS ?
[20:36] <BlessJah> i'm getting (OOPS ID: 2356canistellaunchpad637) while trying to log into stackoverflow using launchpads OpenID
[20:37] <BlessJah> few days ago i've tried to login with the same result
[20:40] <ahasenack> hi, I'm getting repeated oopses when trying to file a bug
[20:41] <ahasenack> here is the most recent one: OOPS-c60c307180525b438f024625703e22c0
[20:41] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=c60c307180525b438f024625703e22c0
[20:41] <lifeless> what is the oops
[20:41] <lifeless> thanks
[20:41] <ahasenack> about 5 or 6 so far
[20:41] <ahasenack> ah, forgot to mention, it's a timeout
[20:41] <lifeless> ahasenack: use less terms in your subject
[20:41] <ahasenack> hm
[20:42] <lifeless> ahasenack: like, way less. Less specific rather than super specific.
[20:42] <ahasenack> lifeless: ok, worked, thanks
[20:42] <lifeless> ahasenack: you can do full detail after the dupe detection has run.
[20:42] <ahasenack> yep, good idea
[21:34] <BlessJah> (OOPS ID: 2356canistellaunchpad637) while trying to log into stackoverflow using launchpads OpenID