/srv/irclogs.ubuntu.com/2012/08/21/#launchpad-dev.txt

wgrantwallyworld: Hum, interesting regression00:25
wgrantwallyworld: https://code.launchpad.net/~timkross/cjdns/cjdns00:25
wgrantwallyworld: Look at the "Edit import source or review import" link00:26
wallyworldyou mean it's split?00:27
wgrantwallyworld: It's overridden by JS to display a bug picker00:27
wallyworldah, i had logged out, just a sec00:27
wgrantAh00:28
wallyworldso it is :-(00:29
wallyworldi'll have to fix it00:29
wallyworldit's got an id of linkbug, that can't be sensible00:30
wgrantHeh00:32
maxbHow... special :-)00:53
=== bigjools-afk is now known as bigjools
* mwhudson wonders if that is his fault01:19
wgrantwallyworld: Thanks for the quick fix01:22
wallyworldneeded to be done01:22
StevenKwgrant: Is POLICY_ALLOWED_TYPES in branchnamespace private? I'm using it, but it's not in __all__.01:34
wgrantStevenK: That's a very good question01:34
wgrantStevenK: I'd rename and expose it01:35
wgrantStevenK: Same with the stuff in bugtarget01:35
wgrantWhich I added a few hours ago01:35
StevenKHas that landed?01:35
wgrantYeah, at 4am or something01:35
wgrantNot through buildbot yet01:36
StevenKRight, I'll rebase this on current devel01:36
lifelessflacoste: http://www.amazon.com/Running-Lean-Iterate-OReilly-ebook/dp/B006UKFFE0/ref=pd_sim_kstore_102:08
lifelessflacoste: looks intruiging02:08
bigjoolslifeless: it does02:23
StevenKsteven@undermined:~/launchpad/lp-branches/destroy-security-contact% bzr di -r submit: | diffstat -s04:00
StevenKUsing submit branch /home/steven/launchpad/lp-branches/devel04:00
StevenK 52 files changed, 61 insertions(+), 1240 deletions(-)04:00
StevenKRight, I think that's security contact eradicated04:01
StevenKForbiddenAttribute: ('remove', <storm.store.ResultSet object at 0x114dfa90>)06:04
StevenKHm. I thought that worked.06:04
wgrantNo06:05
wgrantIt's usually used on an unproxied resultset06:06
wgrantNot one that was returned from a model object06:06
StevenKWell, I don't care about the APGs I get back, I want to remove them06:06
StevenKMaybe I want to add revokeByPolicy()06:07
wgrantThat would be the correct thing to do, yes.06:08
=== almaisan-away is now known as al-maisan
wallyworldwgrant: i've got things all working for the team access policy stuff. one point to note - the bug says private teams need an APG but in fact any team needs an APG to see +junk private branches06:45
wallyworldperhaps I should check non teams as well06:46
=== al-maisan is now known as almaisan-away
StevenKNon teams?06:48
StevenKThe owner can implicitly access a personal +junk private branch06:48
wallyworldStevenK: when the owner was a team, they couldn't06:49
wallyworldwithout a subscription06:49
StevenKwallyworld: Right. The owner of the team can06:50
StevenKwallyworld: So non teams has to be people06:50
wallyworldsure, s/non team/person06:50
wallyworldi'm wondering now though, it we create an APG for +junk, we don't need to create the subscription anymore06:50
wallyworldit's sort of pointless subscribing to one's own +junk branch i would think06:51
StevenKwallyworld: We don't subscribe the team to a +junk branch06:51
StevenKThe owner or the team owner do get subscribed06:52
* StevenK refactors the garbo job to work on sets rather than looping06:52
wallyworldStevenK: incorrect i think - we do a subscribe(self.owner....)06:52
wallyworldand self.owner may be a team06:52
wallyworldso if we do the APG for +junk, then we can forget the subscribe(self.owner...) for +junk06:53
StevenKHm, probably06:54
wallyworldwell, that's my theory right now. i'll do the tests for it all and see how it pans out06:55
wallyworldactually, i wrote the tests for the team owners first, i need to add other tests06:55
wgrantwallyworld: Well, private +junk branches on public teams aren't meant to exist, but they can07:03
wgrantThe default subscription is partly there for MP notifications, IIRC07:03
wgrantcheck the initial mail settings07:03
wallyworldyes, it's nominally for MP notifications. but that then also grants access07:04
wallyworldi guess if the subscription were to be deleted07:04
wallyworldwe would then rely on the APG07:04
wgrantRight, exactly07:04
wgrantAnd the owner loses access07:04
wgrantAnd everyone is sad because nobody can recover it except ~admins :(07:04
wallyworldok. i'll incorporate that into the tests. i'll also only create the AGP for private teams07:05
wallyworldAPG07:05
wgrantI'm not quite sure when the AP/APG should be created. It's a bit of a difficult question07:05
wallyworldi do it in transitionVisibility07:05
wallyworldif visibility == private07:05
StevenKWhich isn't called if say the team is private?07:06
StevenKI think PersonalNamespace.createBranch() is the right place07:06
wallyworldit's called when the team is created. we do need data migration for existing teams07:06
StevenKI don't think we want an AP for every team07:07
wallyworldi create the AP in transitionVisibility and the APG in _reconcileAccess07:08
wallyworldi could move it though to all be done in createBranch07:08
wallyworldi guess when the branch is deleted, or the team is deleted, stuff needs to be cleaned up also. plus merges too?07:09
wgrantwallyworld: I'd suggest renaming AP.team to AP.person07:16
wgrantAs it's conceivable that we might want them for people as well, if we permit people to move private branches to their person07:16
wallyworldi did have that originally but it is a team07:16
wallyworldhmm. ok07:17
wgrantWe only clearly need them for private teams right now07:17
wgrantBut it may end up that we need them for others07:17
wgrantI suspect07:17
wallyworldok07:17
wallyworldwgrant: with deletions and merges, the AP and APG will need to be cleaned up to right?07:17
wgrantwallyworld: Yeah...07:18
wgrantI think we currently forbid merges if there are private branches involved07:18
wgrantSo you should be able to just delete the APG and AP07:19
wgrantSince they can't be referenced.07:19
wallyworlddo we clean up now for pillar APGs for deleting bugs and branches, i can't recall?07:19
wgrantNo07:20
wgrantStevenK's working on a garbo job that will remove unused APs and APGs if the project policy forbids them07:21
wallyworldso i propose i don't to the cleanup in this branch and defer it to another07:21
wgrantSo07:21
wgrantI would suggest that we actually put it in _reconcileAccess or BranchNamespace or something, maybe07:22
wgrantIt'll work for any person, then07:22
wgrantand a counterpart to StevenK's garbo job can clean them up if they're unused07:22
wgrantIt's slightly evil07:22
wgrantBut it's consistent.07:22
wallyworldthe APG bit is in _reconcileAccess07:26
wallyworldthe AP creation for the team is in transitionVisibility07:26
wallyworldfor if i do it in createBeanch, both can be done together07:26
wallyworlds/for/but07:26
wgrantOh07:26
wgrantThe APG and AP stuff should really be together07:26
wgrantWhy the difference?07:26
wallyworldAP and APG for pillars are not done together07:27
wgrantAlso, not just createBranch, but moveBranch, and transitionToInformationType :/07:27
wgrantwallyworld: Do you mean APG or APA?07:27
wallyworldAPG07:27
wallyworldno07:27
wallyworldAPA07:27
wgrantThat makes more sense :)07:28
wallyworldyeah, sorry too many TLa for disclosure07:28
wgrantFor non-pillars, each AP has one immutable APG07:28
wgrantSo they should probably be managed together07:28
wallyworldwgrant: fuck, forget what i said just above. yes, the AP and APG are done together07:29
wgrantRight07:29
wallyworldthe APA is done in _reconcileAccess07:29
wgrantSo the only concern is where we put them.07:29
wgrantYep07:29
wallyworldthe code is right, but i lose something in he translation typing into irc for some reason07:30
wgrantEasy to do :)07:30
wgrantI'm really not sure which is the best place to put this07:30
wgrant_reconcileAccess is the safest07:30
wallyworldi put the AP and APG in transitionVisibility because we only want to do that for private teams07:30
wallyworldand then the APA in _reconcile can assume the AP/APG is all set up07:31
wgrantwallyworld: It's not actually clear that we only want to do that for private teams.07:33
wgrantThe immediate problem is only for private teams, though07:33
wgrantBut what if I make my team public07:33
wgrantOr move a private branch to my public team07:33
wallyworldyou lose access to the private branch for public teams since we don't support that i thought07:33
wgrantThat might be a reasonable answer, yeah07:34
wgrantBut letting artifacts go into an unrecoverable situation is bad, if we can easily avoid it07:34
wallyworldyou mean when a team goes private -> public?07:34
wgrantI guess we should check on branch move that the information type is legal in the target07:36
wallyworldyes, i think that's best07:36
wallyworldlike we do for bugs07:36
wgrantCurrently I can do something like https://code.qastaging.launchpad.net/~wgrant/+junk/test607:37
wgrantWhich is a private branch on my person07:37
wgrantBy setTarget()ing it from a project with private branches07:37
wgrantThat reminds me07:38
wgrantWe should probably add a safeguard in reconcile_access_for_artifact07:38
wgrantThat the correct number of APs is returned07:38
wgrantOtherwise eg. if a bug happens to get a task added on a project that doesn't have a matching policy, it'll silently work but be partially invisible07:39
wgrantShould probably crash instead07:39
wgrantIf you're near that code atm and it looks easy, could you throw that into your current branch? If not I'll do it07:40
wallyworldok, i'll take a look. but i probably won't to it till tomorrow, since i want to write some more tests etc07:41
wgrantSure07:42
=== frankban changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: frankban | Firefighting: - | Critical bugs: 4.0*10^2
=== almaisan-away is now known as al-maisan
adeuringgood morning08:24
jelmermørgen08:33
adeuringfrankban: could you please review this MP: https://code.launchpad.net/~adeuring/launchpad/specification-auth-check/+merge/120430 ?08:45
frankbansure adeuring08:45
adeuringthanks!08:46
jamjelmer: I just saw a failure on your build, will it actually stop it?09:08
jamjelmer: http://paste.ubuntu.com/1158664/09:08
jelmerjam: doesn't look like it has :)09:08
jamjelmer: would it fail at the end, there is also: http://paste.ubuntu.com/1158667/09:09
jam(running bzr selftest vs bzr selftest -1)09:09
StevenKjelmer: You didn't look at my branch :-(09:09
mgzjam: the python test suite is less fancy than ours09:10
jammgz: sure, but it can a) Stop on first failure or b) Record a failing test suite at the end09:10
jelmerStevenK: Sorry09:11
jamor c) have failures and just ignore all of them09:11
jelmerStevenK: I did look :)09:11
jelmerStevenK: Just not get back to you09:11
jelmerStevenK: The changes all seem reasonable to me09:11
jelmerIncluding switch subvertpy to 0.9.009:12
jelmer*switching09:12
StevenKjelmer: Ah ha. I'll land it tomorrow then, thanks.09:13
jamjelmer: hmm.. interesting, looks like lots of failures, but still a clean pass09:34
jammgz: looks like it is (c) after all09:34
jamwhy run a test suite if you aren't going to have it pass09:34
mgzfor giggles!09:34
jammgz: yeah, but it would save a lot of time building python if we don't do steps that just get ignored anyway :)09:34
jamjelmer: so, next step is python-defaults?09:35
jamalso, *my* lucid vm is 32-bit. so I can't actually use the amd64 one... :(09:36
=== al-maisan is now known as almaisan-away
rick_h_morning10:56
jamjelmer: so where are we at for the python-2.6/7 stuff? need to dput python-defaults and ping to get it to jump the queue?11:14
jelmerjam: Yes, that's what I'm on atm11:15
jelmerjam: since 2.6 built ok11:15
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
jamjelmer: how's it going? (Just finished up a couple of interviews)13:02
BjornThow long does the staging.launchpad.net code update usually take?13:05
jelmerjam: about to do another upload13:06
wgrantBjornT: About five minutes, but there's nothing usual about this one13:09
wgrantBjornT: staging currently has no database due to the DC move. It'll be another day or so before it's rebuilt13:09
wgrantBjornT: Can you use qastaging instead?13:09
BjornTwgrant: ok. i guess i could try qastaging instead.13:11
wgrantjelmer: Do you want a score boost on that build?13:20
jelmerwgrant, that would be awesome13:20
jelmerwgrant, I'll ping one of the buildd admins once I've done the upload13:20
jelmerI guess you're still a buildd admin?13:20
wgrantYeah13:21
cjwatsonOr I can if wgrant's asleep13:21
abentleywgrant: Did lifeless have the right explanation of why you marked bug #1032717 "in progress"?13:22
_mup_Bug #1032717: blueprint schema doesn't support private projects <qa-ok> <Launchpad itself:Fix Released by abentley> < https://launchpad.net/bugs/1032717 >13:22
wgrantI marked the model one in progress13:23
wgrantOh13:23
wgrantIt was renamed :)13:23
* wgrant checks IRC logs13:24
abentleywgrant: It was really intended for the schema change, I just vague it up because lifeless doesn't like bugs that request a particular technical solution.13:24
wgrantAh, missed the ping, sorry13:24
wgrantYeah, lifeless' explanation was correct13:24
abentleywgrant: np.13:24
wgrantSorry if I misunderstood the bug13:24
abentleywgrant: Okay, np.  Perhaps my fault for vague bug.13:25
abentleyrick_h_: I don't know if this would be too much work, but it might be nice to mess with the other links on the walkthrough so that you can't wander off onto qastaging by accident.13:48
rick_h_abentley: yea, if I have time I'll try to hook up the ones that I end up with pages for13:49
rick_h_for instance, as I create the code mockup, the code links in the heading cam go somewhere13:49
abentleyrick_h_: right.13:50
rick_h_but after that, I'll probably just set something to kill other links if I get time to clean it up13:50
abentleyrick_h_: Maybe you could just rewrite qastaging links dynamically onload :-)13:50
rick_h_some delegate listener for all links that check for qastaging in the url and just halt() on that13:50
abentleyrick_h_: or that.13:50
rick_h_or that, but yea13:50
=== al-maisan is now known as almaisan-away
cr3hi folks, I pushed changes to a branch over an hour ago, but the branch page on launchpad still shows "updating branch..." and the recent revisions doesn't show the one I pushed yet. is this a known problem?14:58
=== deryck is now known as deryck[lunch]
abentleycr3: that does happen occasionally.  The branch may have taken too long to scan and the scan been terminated.16:11
cr3abentley: anything I can do to help things alog, like push again or something?16:23
cr3s/alog/along/16:23
abentleycr3: Yes, pushing again will re-trigger the scan.16:23
cr3abentley: thanks, and we are just talking about a branch and not a merge request, right?16:23
abentleycr3: yes.16:24
cr3even though I've had similar problems with merge requests, I don't mind exceptionally setting those to "merged" manually16:24
abentleycr3: Could you be more specific about "similar" problems?16:25
cr3abentley: instead of "updating branch..." in the branch, I would see "updating diff..." in the merge request16:26
abentleycr3: It will say that if a scan is needed, i.e. the branch page says "updating branch".16:27
cr3abentley: makes sense, so the problems are related.16:28
abentleycr3: right.  The fact that "merged" isn't set is because the scan hasn't completed, not because the diff hasn't been updated.16:29
abentleycr3: however, if you can specify *which* branch we're talking about, we can check the logs and see what happened.16:30
cr3abentley: this is the breanch I'm talking about: https://code.launchpad.net/~canonical-hw-cert/checkbox-editor/trunk16:33
cr3abentley: I tried pushing again, when you suggested it a few minutes ago, and we can still see: updating branch...16:33
abentleycr3: So, it looks like scans of your branch are oopsing, but the root cause is being masked by a database exception: https://oops.canonical.com/?oopsid=OOPS-20a29e8a7bf4295727dddba3ddb7579216:37
cr3abentley: permissions on the project relating to that branch were changed recently, might that be a reason? I can't imagine it would be because of the size of the branch, it's tiny and not many revisions16:40
abentleycr3: It's really hard to say, since we can't see the actual failure.  I'm not aware of any cases where permisions would affect branch scans, but...16:43
cr3abentley: branching the project returns the right revision, so only having the web interface updating the branch will not prevent me from getting work done. is there anything I should do to help, in case this might be a real bug that might affect other projects?16:45
abentleycr3: Bug 1039556 also involves checkbox.16:47
_mup_Bug #1039556: No diff generated when making a merge request or just uploading a branch <Launchpad itself:New> < https://launchpad.net/bugs/1039556 >16:47
cr3abentley: the symptoms look the same but, for your information, the checkbox-editor branch I mentionned earlier and checkbox don't share anything as far as bzr is concerned. however, they might have similar project configurations like driver, maintainer, etc.16:50
abentleycr3: The actual failure in the oops is different, too.  Very strange.16:50
cr3abentley: should I added a comment about the checkbox-editor branch mentionned earlier to the same bug report?16:55
abentleycr3: I'm filing a new bug report.16:56
cr3abentley: thanks!16:56
=== deryck[lunch] is now known as deryck
abentleycr3: bug 103963817:01
_mup_Bug #1039638: Scans of ~canonical-hw-cert/checkbox-editor/trunk oops with a database error <Launchpad itself:Triaged> < https://launchpad.net/bugs/1039638 >17:01
cr3abentley: should bug #1039556 be deprecated by that one?17:02
_mup_Bug #1039556: No diff generated when making a merge request or just uploading a branch <Launchpad itself:New> < https://launchpad.net/bugs/1039556 >17:02
=== frankban changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On call reviewer: - | Firefighting: - | Critical bugs: 4.0*10^2
abentleycr3: No, they could be separate issues.17:03
cr3abentley: ok, thanks!17:03
abentleycr3: np.17:03
cr3is it possible to build arm packages in a public personal ppa?18:54
jelmercr3: IIRC yes, but there's a flag in the PPA that has to be enabled by a commercial admin to allow ARM building18:58
cr3jelmer: excellent, so I should open a question against launchpad itself then. thanks!18:59
=== matsubara is now known as matsubara-afk
=== lifeless_ is now known as lifeless
=== matsubara-afk is now known as matsubara
lifelessfun - bug 103970220:34
_mup_Bug #1039702: Comments not posted <Launchpad itself:New> < https://launchpad.net/bugs/1039702 >20:34
=== Ursinha` is now known as Ursinha
sinzuiStevenK: This is my quick change to reconcile API and mail with UI22:19
StevenKsinzui: Found it and approved it.22:20
wallyworldsinzui: https://pastebin.canonical.com/72614/22:57
wallyworldsinzui: StevenK: https://pastebin.canonical.com/72745/23:00
sinzuiwallyworld: +1 from me23:01

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