[00:01] huwshimi: mumble? [00:02] sinzui: Sure [00:04] sinzui: added; please give another once-over. Thanks! [00:33] hmm [00:33] how does the lp wiki get wikinames these days? [00:33] SSO or LP ? [00:33] * sinzui wants to know that answer [00:33] we can close about 8 bugs id LP is not involved [00:33] hloeung: hi [00:34] lifeless: Hi [00:34] we're wondering how dev.launchpad.net gets its wikinames for users logging in via openid [00:34] is it via the SSO service [00:34] or via LP [00:34] lifeless: Wikinames? Doesn't it just use usernames? [00:35] It's not like the old days of the Ubuntu wiki. [00:35] well, consult - https://dev.launchpad.net/UserPreferences [00:35] Hm? [00:35] if someone does a timestamp [00:35] it uses their wikiname [00:36] but there is no ui to set it [00:36] Hmm, true. [00:36] so presumbably its coming from openid or *something* [00:36] wgrant: so I'm trying to poke dominator to handle my arch_any_all skew test case, and I'm really concerned about performance. To determine if a skew has happened, we need to query each SPH for a given binary package, and check to see what has published where. That's not going to be DB friendly ... [00:36] But it gets it through SSO, which doesn't expose wikinames. [00:36] Maybe it just uses displayname. [00:36] we're about to delete wikinames from lp [00:36] if that table is replicated to sso [00:36] It's not. [00:36] I can imagine Bad Things Happening [00:36] \d lp_ [00:37] NCommander: indeed. That would be fail. [00:37] Right [00:37] NCommander: What is the algorithm you are using? [00:37] We do far worse queries in the dominator now. [00:37] wgrant: I haven't written one yet [00:38] wgrant: well, for each BPPH, I need the SPH to grab the binary packages it generates, and then checks the dependencies to see if they would still be satisifiable if a package was marked SUPERSEDED [00:39] NCommander: I don't think you can sensibly parse dependencies. [00:39] NCommander: that is going to be terribly slow. [00:39] if they are modelled in the db we can do it [00:39] recursive query [00:40] wgrant, why does it have to be slow? [00:40] cody-somerville: death by a thousand cuts [00:40] Ideally, I want LP to make sure the archive is in an installable state [00:40] NCommander: you might like to look at the conflictchecker schema [00:40] NCommander, There are tools that exist that do just that. [00:40] cody-somerville: your not catching the point [00:40] NCommander: it handles in-db dependency queries to answer some very similar questions [00:41] The archive should NEVER be uninstallable as it disrupts image building on ports architectures [00:41] FWIW I agree [00:41] lifeless: right, but conflictchecker isn't run once an hour like the publisher :-) [00:41] NCommander: The publisher is run every 5 minutes. [00:41] * NCommander coughs [00:41] NCommander: no, but it can handle a single package change in typically 50-100ms [00:41] The primary archive publisher is a special case. [00:42] lifeless: the dominator does the entire archive at once. Not on a per package basis. Given we have 17-20k binary packages, that's going to add up [00:42] fast [00:42] NCommander: Not quite. [00:42] NCommander: you don't need to recheck things that aren't changing. [00:42] NCommander: I think they will still transition from Published->Superseded as normal. [00:42] NCommander: you need to check the implication of things that *are* changing. [00:43] NCommander: But Superseded will be included in indices, until removal is scheduled. [00:43] NCommander: judgeSuperseded will implement this logic. [00:43] wgrant: as it stands, shouldn't it be PUBLISHED if it should be in the index? [00:43] NCommander: It examines Superseded but uncondemned publications. It needs to implement this extension. [00:43] NCommander: Yes, but we are not talking about as it stands :) [00:45] At the risk of making a lot of pain for myself, but it might be saner to have a new PUBLISHED_SUPERSEDED status [00:45] Why? [00:45] instead of making SUPERSEDED now be inconsistant w.r.t. to something publishing status [00:45] All tools can now handle multiple versions in the indices. [00:45] Since Debian does it. [00:45] yes, but if I look at all SUPERSEDED packages, I no longer have an idea what may or may not be held in archive. [00:46] er, in the indices [00:46] Ideally, PUBLISHED_SUPERSEDED should also include a reason on why it hasn't left the incidies [00:46] The idea is that everything on disk will be in the indices. [00:46] stuff in superseded is on disk, right ? [00:47] So then SUPERSEDED should simply always be in the indicies. [00:47] until it reaches its execution time. [00:47] lifeless: Partly. [00:47] lifeless: status = SUPERSEDED AND dateremoved IS NOT NULL is on disk. [00:47] GRAR [00:47] s/NOT // [00:48] wgrant: won't that become DELETED on the next publisher run? [00:48] NCommander: No. [00:48] Superseded/Deleted/Obsolete are all final states. [00:48] Superseded == package was superseded [00:48] Deleted == package was explicitly deleted [00:48] Obsolete == series went obsolete. [00:49] Ah [00:49] So as I read domination, the only thing that tells LP is something is SUPERSEDED is if it pops multiple versions of a given package [00:49] That check needs to be made smarter [00:49] huh, no [00:49] Why? [00:51] bah [00:51] sorry [00:51] my brain seized [00:53] so if I'm following you, the 'correct' solution is to have everything that is SUPERSEDED end up in the indicies until its execution time, and then modify deathrow to be smarter about what packages it brings death to. [00:53] am I in the right ballpark? [00:54] * wallyworld grumpy. no coffee yet so far today. must rectify [00:54] NCommander: Until its *condemnation* time. [00:54] Removing it at the time of execution would leave stuff 404ing a lot. [00:55] We have no maintenance people around right now, do we? [00:55] lifeless: ^^? [00:55] Well, then the most straightforard thing to start off with is implementing that SUPERSEDED packages stay in indicies and fixing whatever breaks from that, then make deathrow smarter [00:55] wgrant: in this tz atm ? I think not. [00:56] lifeless: :( [00:56] maybe brad or someone. [00:56] lifeless: There are unlanded cowboys :( [00:56] they can be reapplied in a pinch [00:56] which sucks butwhatare yougoingtodo [00:56] Or we just exclude germanium this time. [00:56] right [00:58] * NCommander makes a new LP branch for changing how SUPERSEDED is handled [01:00] NCommander: We probably want to talk to Julian before you start on anything like this. [01:00] wgrant: fair enough. What time zone is he in? [01:00] NCommander: He's UK [01:01] So BST. [01:02] Yay, I can self-review without lifeless killing me now. [01:02] right, so I will see him in ~8 hours [01:02] NCommander: I hope not. [01:04] wgrant: ?, that would be at the start of his day [01:05] wgrant: I would never kill you :) [01:05] NCommander: Yes, but the middle of your night. [01:06] Hmm. [01:06] Is my connection dodgy, or is LP sending empty responses? [01:07] wgrant: well, that's hat caffiene is for, but hopefully he will be up when I get up (and that your timezone overlaps somewhere in there) [01:07] Overlap between the three of us is just about impossible. [01:08] Maybe late my evening. [01:40] Hm. [01:41] ShipIt is inactive, but the bugs are still open? [01:43] sinzui: Can we delete mailing-list-experts? [01:43] sinzui: It's not a celebrity any more, and its only related artifact is the deleted mailing-list-beta-testers [02:33] wgrant: you have some changes to lazr-js for the picker entry rendering? i need to hack in the same area - i want to extract out the picker entry rendering to a method that can be overridden. if you are done i can merge in your branch before i start hacking [02:35] or i can take just your lazr-js changes for the affiliation rendering work and go with that [02:41] wallyworld: Heh, no, the lazr-js changes are terrible hacks that need to be rewritten. And they're tiny. So you do your stuff, and I'll rework on top of that when you're done. [02:41] ok. thanks [02:59] Project windmill-devel build #159: STILL FAILING in 1 hr 6 min: https://lpci.wedontsleep.org/job/windmill-devel/159/ [02:59] StevenK, hey... where are you guys pulling python-testtools from? I'm not seeing 0.9.11-r189 on pypi (at least sudo easy_install "testtools>0.9.10" is not finding it) and I don't see it getting built in Ubuntu, either [03:00] its not released yet I don't think [03:01] __version__ = (0, 9, 11, 'dev', 0) [03:01] timrc: thats a snapshot [03:01] timrc: its in the lp download cache [03:18] lifeless, ah... rocketfuel-get is my friend [03:22] hi folks [03:22] Morning jtv. [03:30] u [03:30] hi jtv [03:31] hi [03:31] what does the "u" stand for? [03:31] jtv: bigjools suggested we have a call w.r.t. the persona discussion - I'd be delighted to do that sometime today if you want. [03:31] jtv: 'u' - up in gmail. [03:31] ewin? [03:31] yup [03:31] :) [03:32] Julian also suggested that we chat about another problem, but since I haven't had my coffee yet I can't even speak coherently about it [03:32] well there is no rush [03:32] I'm still in my workday for at least another 1.5 hours, and probably significantly more [03:34] Knowing you, you'll probably throw in another 17 of overtime. [03:34] yeah [03:34] I just won't feel guilty about wandering off during those hours :) [03:34] Good! [03:35] Well, I've made a note of the time and will definitely get that coffee first. [04:13] lifeless: Good plan to try GPGHandler first. [04:32] lifeless: the coffee is kicking in. Yes, I'd be delighted to have a chat about the persona thing if you still have time! [04:32] sure thing [04:35] lifeless: mumble? [04:36] lifeless hates freedom. [04:36] jtv: do you have canonical voip? [04:36] jtv: failing that skype ? [04:36] mumble to here is frankly terrible [04:36] I don't have the voip thing, no… let me start skype. [05:23] wgrant: O hai. Where does one get testr? [05:25] StevenK: from lp:testrepository, or packaged in https://launchpad.net/~testing-cabal/+archive/archive [05:25] StevenK: apt:testrepository [05:26] Fail, gnome-terminal doesn't link that. [05:26] apt://testrepository [05:26] Still fail. [05:26] Anyway, it's in the primary archive. [05:35] spiv, wgrant: Ta === almaisan-away is now known as al-maisan === Ursinha is now known as Ursinha-afk [06:09] Is anyone available to review? [06:10] StevenK: What's up? [06:11] wgrant: https://code.launchpad.net/~stevenk/launchpad/notify-announce-list/+merge/63067 [06:11] You've probably had enough of my reviews lately, though. [06:11] Haha [06:11] Aha. [06:11] This is a hopefully 1: short, 2: safe [06:12] Yeah. [06:12] It's not the branch I thought it was. [06:12] No, Julian subverted me. [06:14] StevenK: You've not cleaned up archiveuploader. Your point is invalid. [06:14] You can wipe announcelist out of archiveuploader entirely, AFAICT. [06:15] wgrant: I had not done so because I wasn't sure how much test fallout there would be. [06:15] Test fallout is better than tech debt in the most tech debty part of the tech debt that is our codebase. [06:15] wgrant: Let me wave the axe around more. [06:15] Thankyou sir. [06:17] * StevenK tries to remember where else he saw it [06:18] lib/lp/archiveuploader/uploadpolicy.py should be all that's left. [06:18] Except maybe tests. [06:18] But there probably aren't tests. [06:18] Because this is archiveuploader. [06:19] Ah, no, uploadpolicy.txt tests it vaguely. [06:19] I've just cleaned that up by removing the *ugly* property [06:19] Yup. [06:19] However, I can recall something that took announce_list as an argument [06:19] acceptFromQueue? [06:19] notify? [06:19] lib/lp/soyuz/browser/queue.py perhaps [06:19] * StevenK looks [06:19] A whole lot of other stuff which was sick and wrong? [06:20] Let me see if the test you mentioned is broken first [06:21] I changed the file already, so finding it is a simple matter of grep [06:21] Project windmill-devel build #160: STILL FAILING in 1 hr 9 min: https://lpci.wedontsleep.org/job/windmill-devel/160/ [06:25] wgrant: It was soyuz/scripts/queue.py [06:25] :( [06:25] I've cleaned it up too [06:33] StevenK: Done. [06:38] wgrant: Is http://pastebin.ubuntu.com/615643/ better? [06:39] Worse. [06:40] That linewrap makes me sad. [06:40] There's a reason I did it the other way :) [06:40] Sure, but distroseries.changeslist is longer :-) [06:41] If you must have the BACKPORTS line wrap, put it on a separate line and indent it. [06:42] Complex conditions want to be readable :( [06:42] wgrant: http://pastebin.ubuntu.com/615644/ [06:43] StevenK: At that point you might as well just move the whole thing on to a new line. [06:43] No parentheses, and it's clearer. [06:44] But that is better :) [06:44] wgrant: http://pastebin.ubuntu.com/615645/ [06:44] StevenK: Looks great, thanks. [06:45] Excellent. I've also eradicated announce list from queue.py and its tests, so I'll toss it at ec2. [06:45] Perfect. [06:46] wgrant: Also, not arguing about my changes? What, are you sick? :-P [06:47] This is a largely unoffensive cleanup :) [06:47] Tis not large enough for my liking [06:47] wgrant: Oh, was that your first code review? [06:47] (As opposed to code*) [06:48] Well, apart from the one yesterday where lifeless graduated me so he didn't have to find a mentor, yes. [06:48] Haha [06:53] * StevenK ponders a bug vs --no-qa [06:54] no-qa [06:56] lifeless: I see the notification on the blog... no issues with deploying the inTeam fix? === al-maisan is now known as almaisan-away [07:29] wgrant: no issues [07:31] Project windmill-db-devel build #354: STILL FAILING in 1 hr 5 min: https://lpci.wedontsleep.org/job/windmill-db-devel/354/ [07:33] lifeless: Thanks. [07:54] Yay [07:54] I think person search works OK when karma is added. [07:54] wallyworld: Do you have a newer query than the one you gave to lifeless yesterday> [08:27] Hmm. [08:27] Except team search. [08:27] This sort of completely breaks that. [08:27] Fail. [08:29] wgrant: Is that wallyworld's branch, or something else? [08:30] wgrant: i've included one in the mp: https://code.launchpad.net/~wallyworld/launchpad/person-picker-results-order/+merge/63057 [08:30] StevenK: I have added karma to his query. [08:30] And it works pretty well. [08:30] IRC nicks and email addresses are awkward, though :( [08:31] Since all we have is non-discriminatory prefix match. [08:31] They tend to dominate. [08:31] Karma mostly sorts that out. [08:31] But something longer-term would be nice. [08:46] I've had quite enough of this bouncing. Let's see if it gets better if I take wifi out of the loop. === jtv1 is now known as jtv [08:52] stub: I'm hoping to get a db review & patch number out of you for https://code.launchpad.net/~jtv/launchpad/db-bug-790161/+merge/63002 [08:53] wgrant: aggregate karma across the team ? [08:54] lifeless: That would work for ranking people and teams separately. [08:54] lifeless: But ranking them sensibly in a single listing borders on impossible. [08:55] average the karma across the team [08:56] That might actually work. [09:02] good morning [09:06] Hello [09:07] hi mrevell === almaisan-away is now known as al-maisan [09:35] jtv: k [09:35] ขอบ [09:39] stub: evening [09:43] jtv: Why is copy_policy free form test rather than something like an enum? [09:43] lifeless: yo [09:44] stub: otp [09:44] (yeah you know me) [09:52] anyone knows if there's an easy way to fetch multiple persons (given by their self_links) using API without doing multiple round-trips to the server? [09:53] You can't. [09:53] or, how would one best export a tuple over the API for use in JS (I want to get a tuple (BugSubscription, Person, Person [subscribed_by]) from an API call so I don't have to do multiple round-trips, but I'd also feel that such API wouldn't really be the best publicly facing thing one might have; or maybe it would be) [09:54] wgrant: "yay" [09:58] I am guessing I'll have to define a separate interface holding this information, because I want a collection of such tuples; or, is there a way to force "shallow" (1-level) snapshotting of particular attributes on an already exported interface? [09:58] danilos: you're probably best off defining a custom view which can return the json youneed [09:59] our API is hugely focused on types and URL mapping, sadly [09:59] lifeless, is that the practice we encourage? I kind of dislike that approach [09:59] danilos: to date folk generally throw their hands up and say 'man this is too hard' [10:00] lifeless, right, it's probably the simplest thing but the bug page is doing a bunch of that stuff and I'd rather do away with it (well, I'd still be able to get rid of 3-4 portlets, and introduce 1 new view, so it'd be an improvement, but I was hoping for 0) [10:00] danilos: I recall a page somewhere that exists just to give json to browser js scripts [10:01] lifeless, yeah, there's a few of those on the bug page, and some of them render the actual HTML that's loaded through AJAX (yuck) [10:01] danilos: the main API can do that too [10:01] danilos: I agree that its yuck. It makes the service proposal I have have some fugly bits [10:02] danilos: but all that said, I think if you have something pretty use case specific, putting it in the public API would be a little ugly [10:02] lifeless, right; still, useful to know that this is the approach I should take [10:03] lifeless, agreed, but if I need this (i.e. "get all subscriptions with subscriber Person fetched at the same time"), I am pretty sure public users might need it too [10:03] lifeless, but, then again it'd be opening a whole new can of worms, and I'd rather not go there [10:04] right [10:04] there is a broad issue with the API and performance [10:04] yup [10:04] launchpadlib cannot use point solutions [10:04] it needs some (perhaps easy) infrastructure and a defined pattern for the solutions to fit into [10:05] ok, thanks; I'll go with a view-provided JSON and load that on-demand, and I'll let you worry about coming up with nice infrastructure for this :P [10:05] There is a document about doing a V2 API by leonardr/benji/gary on the wiki [10:05] cool [10:28] stub: hi. i was hoping you could give me a db patch number for the person.displayname index creation script. it's included in mp https://code.launchpad.net/~wallyworld/launchpad/person-picker-results-order/+merge/63057 [10:28] wallyworld: I landed a patch to add the person.displayname index already [10:29] patch-2208-60-1.sql [10:30] stub: back. And that was opp, not otp. [10:30] stub: ok thanks. i thought you'd create the index but i needed to do the ptach still as part of my mp. i'll remove it. [10:31] stub: the boss specified a plain text field for the policy name because it's a bit easier to follow than an enum field. [10:31] wallyworld: no probs. I tend to create the patches that I apply live, since the live version is usually very similar to what needs to land and I want to minimize chances of administrative screwups [10:31] the policies are named rather than enummed :) [10:31] bigjools: enums are names stored as integers [10:31] But the names are crap :( [10:31] SIGH [10:32] nice constructive criticism there wgrant [10:32] 'insecure' doesn't make sense outside the uploader. [10:32] That is my only objection :) [10:32] bigjools: Is there a fixed set of names, or are they freeform input of some sort? [10:32] Well, it doesn't really make sense *in* the uploader either, but that's what we have. [10:32] * bigjools lets jtv continue [10:33] stub: fixed set, for matching policy classes. [10:35] So what is the advantage of a text field over an enum for that? We know the advantages of enum over text field which is why we normally use them. [10:36] Mostly that it takes us from a mapping between policies and names to a mapping between policies, names, and numbers. [10:37] Not lethal, but inconvenient. [10:37] I am not wedded to names, switch it if you want [10:37] The enum infrastructure means it is a mapping between policies and enums, not between policies, names and numbers. [10:38] * stub would love to use pg builtin enums, but not suitable for agile development until PG 9.1 [10:38] Well the enum provides a mapping between names and numbers; we'd add the mapping between names and policies ourselves. [10:39] I don't follow. You reference enums as names, not as numbers using some external mapping repeating what the enum infrastructure gives you for free. [10:40] Apart from getting ints in the database, of course. [10:40] job.copy_policy = CopyPolicy.ZAPIT [10:40] Right. And you don't see then in the Python code. [10:41] Well, apart from the one place of course. [10:41] Not trying to argue, really; just describing the inconvenience. [10:43] There is small inconvenience creating the enum definition, but advantages to using it (smaller tables, no toast, faster lookups, smaller indexes, typo catching, faster python code). So unless there is a good reason, we should switch that column to an integer and use the standard pattern. [10:43] Toast may be a bit of an exaggeration for this case. :) [10:44] But sure, I can switch it. [10:44] I think the toast table gets created when the main table gets created [10:45] Oh well [10:45] I can list more rationalizations for enums too if you like :) [10:45] No that's alright, thank you :) === al-maisan is now known as almaisan-away [10:56] stub: updated the patch. [11:06] jtv: Ta. Does allowing NULL still make sense ('not set' vs. explicit enum value)? [11:06] I expect so as not all jobs will use the field (?) [11:07] stub: that may depend a bit on where the class hierarchy goes, but I guess it would make sense for now to forbid it. [11:08] if it makes sense, make it not null. Or leave it as nullable if we are not sure yet. [11:08] I'll make it "not null." If we ever decide that's wrong, we can relax it. Easier than going the other way. [11:10] jtv: Unless we are mid cycle :) [11:10] * stub isn't helping [11:11] We'll just wake up an admin in the middle of the night to drop the constraint. [11:18] lifeless: did you see https://code.launchpad.net/~stub/launchpad/bug-758587-tests/+merge/63012 ? [11:19] make it default to the current "insecure" policy please jtv [11:19] jtv: Did you find that cpu indicator yet? [11:19] bigjools: it seems to make more sense to do that in the code, not in the db. [11:20] jtv: either is fine [11:20] At the DB level I think neglecting to provide a value should produce either a null or an error, even if we do require a value for PlainPackageCopyJob. [11:21] stub: no, I don't have it yet [12:04] Project devel build #771: FAILURE in 4 hr 52 min: https://lpci.wedontsleep.org/job/devel/771/ === almaisan-away is now known as al-maisan [12:19] rvba: reviewed your branch [12:21] jtv: thanks a lot! [12:21] np [12:22] I'll reply to your comments once I've finished my chicken :). === Ursinha-afk is now known as Ursinha [13:23] hello mrevell === matsubara-afk is now known as matsubara [13:42] Hm. [13:42] That is a /lot/ of failurse. [13:49] wgrant: it's so bad, it's even affecting your spelling :P [13:50] That's more the freezingness :( [13:50] wgrant: of your machine or of your fingers ? [13:50] hi matsubara [13:50] The latter. [13:50] hi jelmer [13:52] matsubara: I made some more progress on updating bzr - current work is at lp:~jelmer/launchpad/newer-bzr [13:53] jelmer, cool. should I merge your branch into mine and run tests to see if the errors are fixed? [13:53] oh, you merged my branch :-) [13:54] matsubara: it's too early for that, I'm still chasing some errors in bzr-git [13:54] jelmer, ok, thanks for letting me know. [14:01] Hey bac# [14:13] Hi, adeuring, abentley, and henninge. You guys have the standup yet? [14:13] deryck: no, waiting for you. [14:13] deryck: we are chatting but waiting for youi [14:13] yui? [14:13] ok, cool. thanks. coming.... [14:13] yiu? [14:14] :-D [14:14] if mumble will ever connect [14:16] henninge: mornin [14:17] deryck: do you want to Skype instead? [14:17] maybe so. let me try one more restart. [14:18] cjohnston: Hi! [14:18] cjohnston: otp now [14:18] ok [14:18] mine still need to be worked on? [14:18] cjohnston: the test run failed because of other errors. I just sent a mail to launchpad-dev. [14:19] cjohnston: the branch should be fine now, I expect [14:19] but don't know for sure [14:21] Is anyone else seeing "AssertionError: Name "id-only" is not registered as a view or navigation step for "Person" on "mainsite"." OOPSes on launchpad.dev instances? It happens on pretty much every page. [14:21] henninge: ok.. If you get an answer, let me know please :-) [14:34] matsubara or Ursinha, will either of you have some time for some exporatory testing tomorrow? And then we'll actually need some more probably Thursday of next week too [14:35] gary_poster, yep [14:35] *exploratory :-) [14:35] gary_poster, can you give me more details? [14:40] cool, thanks matsubara, I'll send you details the start of my day tomorrow. [14:40] Overview: the better bug notification feature had two bugs that meant rewriting large chunks of UI. We have one in db-devel now, and one will be ready for a no-downtime deploy after next Wed.'s downtime deploy. [14:40] Tomorrow, we need to make sure that the intermediate changes we have are OK for a few days in production; then next Thursday we need to make sure that the final changes are OK. Since they change a lot of code, and touch on a lot of the issues that were raised in the feature review, I thought exploratory testing would be a good idea. [14:40] Moreover, particularly for the intermediate changes, I know that we had hoped to get the final changes in before the db-deploy, so we were not as careful as we usually are, so another pair of eyes would be appreciated. [14:40] (done) [14:41] gary_poster, sure thing. I'll wait for the details tomorrow and let you know once I have done the testing [14:41] thanks matsubara! [14:41] I don't know one way or the other. Let me take a look real quick. [14:42] benji, you and your channels :-P [14:42]