=== posulliv_ is now known as posulliv === cinerama_ is now known as cinerama === posulliv_ is now known as posulliv === matsubara_ is now known as matsubara [08:37] wahay [08:37] just got merge proposal 110000 [08:37] * thumper does a little dance [08:38] hey [08:38] 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] 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] === czajkowski changed the topic of #launchpad to: https://launchpad.net/ | Help contact: czajkowski | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad | For packaging help: join #ubuntu-packaging [08:39] like it keeps timeouting since [08:39] is that a known issue? [08:40] seb128: what oops are you seeing [08:40] I'm just triaging something similar here for another bug [08:40] (Error ID: OOPS- [08:40] 7a4ed505a6a7ca6b4f403f75264c0ac9 [08:40] ) [08:40] is the one I just got [08:40] czajkowski, can you load this page? [08:40] seb128: which page? [08:41] seb128: the bug you listed, yes [08:41] czajkowski, right, 711413, it doesn't timeout for you? [08:41] nope [08:41] czajkowski, 477d0110a8c8ada4c07a637a43d0a030 is another oops number I got [08:42] seb128: https://bugs.launchpad.net/launchpad/+bug/1012309 [08:42] Ubuntu bug 1012309 in Launchpad itself "timeout when attempting to add a distrotask to a new bug" [Critical,Triaged] [08:43] czajkowski, right, it's not only "when attempting to", in fact the adding worked, it's "impossible to add once ..." [08:43] like I can't load that bug since I nominated it for precise [08:43] czajkowski, thanks [08:44] wgrant: ^^ [08:44] czajkowski, wgrant: that's a blocker for distro [08:44] it's screwed LTS work [08:44] screwing [08:44] 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] like I can't load bugs that are nominated for precise [08:45] did you guys reduce timeouts delay recently? [08:45] seb128: not that I know of no. [08:46] ok, somebody on #ubuntu-bugs mentioned that yesterday [08:46] 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] czajkowski, wgrant: do you have any idea how long it's going to have it looked at? [08:47] seb128: maintence squad look at them but there are already a lot marked critical [08:49] czajkowski, well that one started recently and is breaking ubuntu security team and LTS team work, how can we escalate it? [08:50] seb128: let me just find out [08:51] It's mostly because it has a lot of dupes, it seems. [08:51] czajkowski: That bug is unrelated [08:52] wgrant, hum, it was loading fine before I nominated it for precise [08:52] but maybe I got lucky on the first try [08:55] seb128: 1012309 is specifically about nomination approval timing out. [08:55] Which this clearly is not. [08:55] 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] wgrant, both 7a4ed505a6a7ca6b4f403f75264c0ac9 and 477d0110a8c8ada4c07a637a43d0a030 are the same issue? [08:57] wgrant, well, the nomination timeouted and since I can't reload the bug at all [08:57] b2a034d4b516aa0bb1c5aa4cc1725851 this time [09:18] seb128: We've increased the bug page timeout so that should just be slow rather than broken. [09:18] wgrant, I can load that page against, thanks a lot! [09:18] doh, against->again === matsubara_ is now known as matsubara-lunch === matsubara-lunch is now known as matsubara === apw is now known as apw_ === apw_ is now known as cafetiere === cafetiere is now known as apw_ === apw_ is now known as cafetiere === cafetiere is now known as apw === geser is now known as geser_ === geser_ is now known as geser === yofel_ is now known as yofel === Ursinha_ is now known as Guest4406 === posulliv_ is now known as posulliv === zyga is now known as zyga-afk [16:54] 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] joey: ello, you do come up with some dooseies! :) [16:55] lemmie go and see [16:58] joey: no such luck found https://bugs.launchpad.net/maas/+bug/950804 but not teams :/ [16:58] Ubuntu bug 950804 in MAAS "Same email address for multiple users" [High,Fix released] [16:58] matsubara: ping [16:58] 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] 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] nods [17:00] czajkowski: I want the standard sysadmin email to be in use as the email contact for all those teams === deryck is now known as deryck[lunch] [17:00] and it won't let you? [17:09] czajkowski: right it won't because I used it for another team [17:09] sinzui: have you seen any issue like this before or is there a work around? [17:11] 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] joey: see sinzui knows all === czajkowski changed the topic of #launchpad to: https://launchpad.net/ | Help contact: | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad | For packaging help: join #ubuntu-packaging [17:14] sinzui: yeah for me that means google apps alias [17:14] sinzui: is there any particular reason that's still valid for that restrictive behaviour? [17:15] sinzui: email addys aren't used as a key in the table is it? [17:15] allows teams to share unique identification information leads to untrust and is an attack vector [17:16] We pondered removing team email addresses since we know a team does not have full control over it's email address [17:17] 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] joey, yes. I think the issue here is that we may want Lp to only send notification to team admins. [17:20] sinzui: THAT would be my ideal, yes [17:20] adding a member, admin, or none option may improve lp performance since sending to members can be very expensive [17:20] 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] ah, that would work [17:21] +1 for admin/owner notifications instead of all members [17:24] 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] sinzui: +1 on that [17:27] sinzui: so, you know me too well, answer the next question I'm going to ask :-) [17:28] 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] joey, are you concerned that members are seeing confidential information? [17:29] sinzui: thanks. :-) No security concerns on my end, just annoyance from users at LP spam [17:29] sinzui: if that issue is a bug can you please tag it with "linaro" and sub me to it please? [17:29] pretty please with sugar on top [17:30] 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] 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 === Ursinha_ is now known as Guest97209 [17:32] although, i do like that changes to bugs where teams are the driver/bugmaster/subscribed/whatever, mails all members [17:32] sinzui: I could envision a scenario for private teams where security might be an issue [17:33] but it is also annoying === Guest97209 is now known as Ursinha [17:33] sinzui: but my scenerio there is an edge case I think === Ursinha is now known as Guest86632 [17:35] 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] right [17:40] emphasis on rarely [17:41] 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] We all believe that. [18:13] joey, I think this might be related to your issue: https://bugs.launchpad.net/launchpad/+bug/156340 [18:13] Ubuntu bug 156340 in Launchpad itself "Need to be able to associate multiple email addresses with a team" [Low,Triaged] [18:14] but I'm not really here anymore :-) [18:14] and forgot to afk myself === matsubara is now known as matsubara-afk === deryck[lunch] is now known as deryck === JanC_ is now known as JanC [18:48] joey: you might want to hang out in #launchpad-dev [18:58] lifeless: is that an invitation or a threat? :-) [18:59] joey: yes. [19:00] 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] 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] 06:38 < sinzui> lifeless, joey can provide example of emails that he does not want members to get [19:00] joey: thrilling discussion you missed out on. [19:00] * joey sighs. "Ok brt" [19:09] joey: you got sorted then :) [19:10] czajkowski: Hi. heh... well not yet sorted but the right people with the right talent are thinking about it. [19:10] czajkowski: it's a headache for me but it's not the end of the world for LP you know [19:10] czajkowski: so I'm grateful for them reviewing it [19:10] excellent === Ursinha` is now known as Ursinha === Ursinha is now known as Guest57727 [20:35] any way i can subscribe to uploads here: https://launchpad.net/~xorg-edgers/+archive/ppa [20:35] like i can to debian BTS ? [20:36] i'm getting (OOPS ID: 2356canistellaunchpad637) while trying to log into stackoverflow using launchpads OpenID [20:37] few days ago i've tried to login with the same result [20:40] hi, I'm getting repeated oopses when trying to file a bug [20:41] here is the most recent one: OOPS-c60c307180525b438f024625703e22c0 [20:41] https://lp-oops.canonical.com/oops.py/?oopsid=c60c307180525b438f024625703e22c0 [20:41] what is the oops [20:41] thanks [20:41] about 5 or 6 so far [20:41] ah, forgot to mention, it's a timeout [20:41] ahasenack: use less terms in your subject [20:41] hm [20:42] ahasenack: like, way less. Less specific rather than super specific. [20:42] lifeless: ok, worked, thanks [20:42] ahasenack: you can do full detail after the dupe detection has run. [20:42] yep, good idea === Guest57727 is now known as Ursinha === Ursinha is now known as Guest2796 [21:34] (OOPS ID: 2356canistellaunchpad637) while trying to log into stackoverflow using launchpads OpenID