/srv/irclogs.ubuntu.com/2010/03/12/#launchpad-dev.txt

mwhudsonhm02:45
mwhudsonwhat to do for the last ~2 hours of work on a friday afternoon02:45
lifelessmwhudson: pawn?02:50
lifelessmwhudson: land that bzr-git change I did for you02:50
mwhudsonoh right yeah02:50
lifelessI need a teddy bear02:51
lifelessfor a bzr patch.02:51
mwhudsonlifeless: i can try02:52
lifelessI want to make commitfromnews also set --fixed02:52
lifelessthis means a hook to run after the commit message is set by the user02:53
lifelessrather than at generation time02:53
mwhudsonthat makes sense i guess02:53
mwhudsonone could imagine something similar involving debian/changelog02:53
lifelessright02:53
lifelessin fact commitfromnews could look at debian/changelog if wanted02:54
lifelessor bzr-builddeb can supply the changelog entries as a template02:54
lifeless$whatever02:54
lifelessso the questions are02:54
mwhudsoni think it already does02:54
lifelessshould the message be editable at this point (by the hook)02:54
lifelesse.g.02:54
lifelessit could look for a02:55
lifeless----bugs----02:55
lifelesslp:123402:55
lifelessdeb:45602:55
lifeless--endbugs--02:55
lifelessregion, strip that from the commit and turn it into properties02:55
lifelesscommitfromnews and others could put this in the template02:55
lifelessand a user can then correct it if desired02:56
lifelessor should the message be immutable02:56
mwhudsonyou could put that --bugs-- stuff after the "-- the part of the message after this marker will be ignored --" i gues02:57
lifelessmwhudson: sadly no02:57
mwhudsonalthough that might lead to people not reading it02:57
lifelessmwhudson: because it gets stripped off early02:57
mwhudsonoh right, i guess the hook probably wouldn't see it then?02:57
mwhudsonheh02:57
lifeless'tada' :P02:58
=== jamalta-afk is now known as jamalta
lifelessI think the constraints are:02:59
lifeless - humans can correct the heuristics02:59
lifeless - not -too- ugly if the plugin to do bug handling is missing/disabled for some reason02:59
lifelessany feedback02:59
mwhudsonlifeless: another constraint might be: allowing a way for a gui to be more tasteful in handling this03:00
lifelessso the msg template does have a commit object passed in03:01
lifelessI was thinking to have all the plugins that find bugs tell the commit object03:02
lifelessand the callback in builtins.py (this is really ugly)03:02
lifelessadd the visibilty stuff03:03
lifelessso a gui could do better03:03
lifelessthere is so much code in builtins.py that doesn't belong there.03:03
mwhudsonyes03:03
mwhudsonlifeless: i think what you first suggested sounds good enough to be worth trying to use for a while03:04
lifelessargh, lenovo please please please provide more visibilty03:04
mwhudsonlifeless: the part that's unsettling is making the commit-message-as-edited into some semi structured thing03:05
* lifeless tries a summary:03:05
lifelessa) CLI case03:06
lifeless1) message templates provide a template and also call into the commit to say 'possibly fixes X'03:06
lifeless2) CLI UI layer says 'template += list of bugs fixed'03:06
lifeless3) CLI UI layer strips out list of bugs fixed and adds them as really fixed to the commit03:07
lifelessdone03:07
lifelessb) GUI cas03:07
lifeless1) same03:07
lifeless2) GUI shows additional widget; easy.03:07
lifelessCLI with commit -m - what happens here?03:07
lifelesstemplate doesn't run, no prompt, fail.03:08
lifelesstake 3)03:08
lifelessrather than message templates use a Commit hook to scan for bug status, which can look at:03:08
lifeless - the diff03:08
lifeless - commit message03:09
lifeless - $whatever03:09
lifelessso the CLI case calls this hook after getting the message template from the user03:09
lifelessadds it to the template03:09
lifelessthen parses the result back out again03:09
lifelesscli with -m, shows the commit editor when the detected candidate bug list != supplied bug list from the command line03:10
lifelessand doesn't show the commit message itself03:10
lifelessso 'commit message' here means either 'template or final commit message depending on whether the user has supplied it or not'03:11
lifelessmwhudson: so sounds plausible?03:25
* mwhudson rubs eyes, reads again03:26
mwhudsonlifeless: yeah, i think so03:26
lifelessthis seems too complex03:38
lifelesstake 403:38
lifelesswhat I specifically want is 'bzr commit' -> editor -> adds --fixes for me03:40
lifelesswith, also specific, the ability to correct mistakes03:41
lifelessthe easiest thing is to not do this when -m is supplied03:41
mwhudsoni think not worrying over much about what happens whem -m is supplied makes sense03:42
lifelessthat binds it to the UI03:42
lifelesswhich as a heuristic, is appropriate.03:42
thumperlifeless: nudge re: code snippet03:43
lifelessoh right03:43
lifelessuhm committing patches right03:43
* mwhudson leaves the cafe03:48
mwhudsonprobably back on line for a bit later03:48
lifelesshttp://pastebin.org/11038403:53
lifelessthumper: &03:53
thumperlifeless: ta03:54
lifelessmy fault if it works, yours if it fails03:54
thumperlifeless: does bzrlib have any context managers yet for handling locks?03:55
lifelessthere was a branch03:55
lifelessdunno if its landed03:55
lifelesswe write to 2.4 still though03:55
lifelessso we can't use or even really test them.03:55
thumperlifeless: I was considering targetting 2.6+ for my work so I can use them :)03:56
lifelessthumper: note that the approach I use is a bit fugly04:00
lifelessyou could check Merge3Merger to see how the regular merge code detects conflicts04:01
lifelessbut the class I use is the one you should use04:01
thumperlifeless: thanks04:01
* thumper EODs04:18
wgrantjtv: Morning.04:20
jtvwgrant: afternoon!04:21
wgrantThat too.04:21
wgrantSo, I had a look at the hanging problem this morning.04:21
wgranttwisted.web.xmlrpc.Proxy.callRemote is hanging when you attempt to run build()04:21
wgrantThere are two bugs here: 1) It hangs when you give it the extra_args dict with None as a value. I don't know why this is. 2) You are using IBranch.url, which is None, when you in fact mean IBranch.composePublicURL().04:22
wgrantFixing the latter makes it dispatch.04:22
wgrantBut it gets aborted on the next scan cycle, since TTBB doesn't have a build, and doesn't override verifySlaveBuildID.04:23
wgrantOnce you override that properly, it gets dispatched and finishes fine, although the slave seems to just return filenames rather than a tarball right now.04:23
jtvwgrant: my apologies for my silence; I was looking at a different workspace04:29
jtvWhere are we using IBranch.url?04:30
jtvI specifically wrote IBranch.composePublicURL for this... it'd be an embarrassing oversight if I then neglected to use it in creating the job parameters.04:30
wgrantjtv: TTBJ.dispatchBuildToSlave04:30
wgrantEr, TTBB, I guess.04:31
jtvOMG04:31
jtvand through sheer coincidence it comes out as a http URL that does work for the slave?  weird04:31
wgrant.url comes out as None, which causes the hang.04:32
wgrant.composePublicURL comes out an an HTTP URL which works perfectlyt.04:32
jtvBut I was seeing the proper URL in my BranchJob!?04:32
jtvYes, that's why I wrote the damn thing.  This is galling.  My compliments on finding it!04:33
wgrantThe URL isn't contained in the brnachjob...04:33
wgrantIt just references a branch ID.04:33
jtvthe json_data is {'branch_url': 'http:....'}04:34
wgrantjtv: I appear to have two branch jobs for each scan. One has a URL, and one has from_revision_id/force_translations_upload.04:35
jtvah04:35
wgrantIs the one with the URL the translations job?04:35
wgrantI haven't actually checked the type enum...04:35
jtvthey're both translations jobs, of different kinds :-)04:35
jtvIIRC RosettaUploadJob has a type 3 or 4.  Mine has type 6.04:35
wgrantAhh.04:36
wgrantSo the BranchJob row has a URL, but dispatchBuildToSlave then inaccurately recalculates it?04:36
jtvI guess!04:38
jtvI think dispatchBuildToSlave should just use BranchJob.json_data04:38
jtvWell, I think it's called metadata or something04:39
wgrantI don't see why you precalculate the URL.04:39
jtvOne very stupid practical reason is that it makes it a lot easier to see what's going on in psql!04:39
wgrantshh.04:40
jtvWell, when I'm not second-guessing it and replacing perfectly good json data with the wrong dict.04:40
wgrantHmm.04:40
wgrantHenning's latest branch (lp:~henninge/launchpad/bug-507680-upload-templates) seems like it's attempting to do the upload from the slave.04:40
wgrantI don't think that's going to work.04:40
jtvNo, that wouldn't04:40
jtvYou're talking about the upload to the translations import queue?04:41
wgrantThat's what the comments suggest.04:41
* jtv looks04:41
jtvwgrant: I'm looking at the version I merged into my local branch, but don't see it there04:46
jtvwgrant: oh, you're looking at the branch for bug 507680?04:47
mupBug #507680: Upload buildfarm-generated templates <wellington> <Launchpad Translations:In Progress by henninge> <https://launchpad.net/bugs/507680>04:47
jtvI'll add a note to the bug04:49
wgrantjtv: Yeah, that one.04:51
jtvWow, thanks for spotting that.  It's obscene how much we've come to rely on you.04:52
wgrantHeh.04:53
=== jamalta is now known as jamalta-afk
jtvhi henninge!06:08
henningeHi jtv! ;)06:10
henningejtv: thanks for the comment.06:11
jtvhenninge: ah, you saw that :)06:11
henningeI had already gotten the feeling that I had something wrong in my thinking therer.06:12
wgrantIt looks like you're very close.06:12
jtvanother thing: don't call tarfiles "zipfile," or confusion and the possible collapse of civilization will ensue.06:12
wgrantDispatching all works, so you just have to get the tarball out of the slave now.06:12
jtv(there's a builtin module called zipfile, and we use it elsewhere in our code)06:12
jtvOkay, I may be exaggerating a tiny bit06:12
henningejtv: talking to me?06:12
henninge;)06:12
jtvhenninge: yes.  Okay, I may be understating the "tiny bit" of my exaggeration.06:13
henningeyes, right.06:13
henningejtv: how do I get the tarball from the slave to the master?06:14
jtvgrawr, I hate how my mouse pointer moves because my hands are near the touchpad while I'm typing06:14
wgrantjtv: Karmic and above should disable that by default.06:14
* henninge was going to look at other builder's code but might as well ask ... ;)06:14
wgrantCheck System->Preferences->Mouse->Touchpad, the "Disable touchpad while typing" checkbox.06:14
jtvwgrant: this is karmic, but I think I disabled it by hand06:14
jtvyes, it'd be nice if that actually worked, wouldn't it  :)06:15
wgranthenninge: I see you have code to produce a tarball. You'll need to add that into the returned filemap somehow.06:15
jtvhenninge: see my comment... that part is already done06:15
wgranthenninge: The other slaves do that by looking at a changes file.06:15
jtvah, right, you do need to put it in filemaps06:16
wgrantOnce it's in there, it's trivial to get to it from the master code.06:16
jtvhenninge: IIRC I hard-coded a path for the tarball06:16
jtvah yes, "translation-templates.tar.gz"06:17
jtvfeel free to change that; it's just a placeholder06:17
wgrantSee gatherResults in the Debian and SourcePackageRecipeBuildManagers.06:17
wgrantI suspect that you'll need to copy your file into the filecache, and then call addWaitingFile.06:17
henningewgrant: yes, saw that codenow . I'll look deeper into it to find out exactly.06:22
henningejtv: I saved the world! ;)06:22
henningei.e. renamed zipfile to tarball06:22
jtvmillions sigh in relief06:23
jtv\o/  \o/  \o/06:23
al-maisanhenninge: nice way to end the week :)06:23
jtvlol06:23
al-maisansaving the world06:23
wgrantHeh.06:23
wgrantMorning al-maisan.06:23
henningeal-maisan: yes, feels so good06:23
jtvokay, who's going to put al-maisan on the quotes page?06:23
henningeMoin al-maisan!06:23
al-maisanGood morning henninge, jtv and wgrant :)06:23
jtv:)06:23
henningeOh yes, good afternoon wgrant!06:24
jtvwgrant: in the slave, iterate_CLEANUP calls buildComplete regardless of success, but it turns out buildComplete expects to be coming from a BUILDING state.06:25
wgrantjtv: Why would it be building but not BUILDING?06:25
wgrantCLEANUP is still called during BUILDING.06:25
jtvwgrant: this may be a cleanup after failure06:25
wgrantAt which point alreadyfailed should be True, but the status should still be BUILDING, IIRC.06:26
jtv(as in my case it probably is)06:26
jtvunless the failure happened in a different state...06:26
wgrantIn what other state would it fail?06:26
wgrantYou shouldn't be setting builderstatus yourself at all, I don't think.06:28
jtvpretty much anything at this stage06:28
* henninge gets breakfast06:28
wgrantOh, are you talking about the case where iterate_CLEANUP throws it to BUILDERFAIL, then calls buildComplete?06:29
wgrantWait what.06:29
* jtv looks again06:29
wgrantOh, right.06:29
wgrantAre you aware of the difference between builderstatus and buildstatus?06:30
wgrantIt's very confusing if you forget that they are separate.06:30
wgrantiterate_CLEANUP will set the buildstatus to OK or BUILDERFAIL.06:30
jtvwait, you're talking about build status the database field?  I don't see a connection06:30
wgrantBut the builderstatus should remain BUILDING until buildComplete sets it to WAITING.06:30
wgrantNo, the slave property.06:30
jtvnow _that_ is confusing :)06:31
wgrantYes!06:31
wgrantSo the slave returns something like (BuilderStatus.WAITING, BuildStatus.OK)06:31
wgrantOr (BuilderStatus.WAITING, BuildStatus.BUILDERFAIL)06:31
jtvok06:31
wgrantIs the initial non-BUILDING thing you brought up actually appearing in practice?06:32
jtvSo BuilderStatus.BUILDING should start as soon as the builder accepts a job?06:32
jtvwgrant: yes, that's why I'm bringing it up.06:32
wgrantI think so, yes.06:32
wgrantIDLE -> BUILDING -> WAITING -> IDLE -> ... is the normal path.06:33
wgrantAny of the other states are probably buggy and won't work properly.06:33
wgrant(although the translations job handles ABORTING much much better than binary builds)06:34
=== jtv1 is now known as jtv
wgrantjtv: So, got any more info on the odd failure?06:38
jtvwgrant: yup!  tiny innocuous little line: 2010-03-12 13:38:33+0700 [-] Builder 'bob' rescued from 'bf-test-14': 'Malformed build ID'06:40
jtvAnd the FSM goes through INIT-UNPACK-CLEANUP06:40
wgrantjtv: Ahaha, so it was ABORTING after all.06:40
jtvAnd to some extent, recovering which is also cool.06:41
wgrantYeah, that doesn't work for binary builds.06:41
wgrantBut yours isn't horrible so it might work better.06:41
jtvOh, I missed today's Hacker Minute06:43
wgrantHm?06:44
jtv13:3706:45
wgrantAh.06:46
jtvThen again, last night I finally attended the fortnightly hacker get-together again.  Finally saw James Clark again, which was so much fun after all those years.06:46
jtvAnd of course one Catalan hacker who somehow knows I used to live in his town, and we find a common acquaintance.06:47
jtvThis world is insane.  Run by someone with a sense of humour.06:47
wgrantHaha.06:47
jtvStill, that flight to Wellington takes the cake.06:47
wgrantI was thinking of that, yes.06:48
wgrantQuite incredible.06:48
jtvFunny... it looks as if I'm expected to generate an id consisting of "buildid-buildqueueid" where "buildid" is ignored.06:48
wgrantNot ignored.06:49
wgrantIt's compared down the bottom.06:49
wgrantBut I wrote that method, and I expect you to override it.06:49
wgrantSince you don't have a build.06:49
wgrant(it used to be prettier, but then we got more job types)06:50
jtvoverride verifySlaveBuildID?  Right ho.06:51
wgrantRight.06:52
wgrantI just said 'pass' in my version, but you can probably do slightly better than that.06:52
jtvMakes it a bit dual-purpose though, so maybe I should break that method in twain—"verify that the id makes sense for this job type" and "verify that this BuildQueue object exists."06:52
jtvThe latter is generic.06:52
wgrantIt's entirely up to the BuildFarmJobBehaviour to decide the slave build ID string.06:53
wgrantSo it might not contain the buildqueue ID, but it probably does.06:53
jtvTrue, but a helper seems useful (also means you don't need to look up the utility)06:54
wgrantIndeed.06:54
wgrantAlso, I see some workarounds in the slave for parts of the interface that don't quite make sense for you.06:55
wgrantRemember that you can refactor it too...06:55
jtvotp with hardcore Windows dev06:59
jtv"you didn't hear this from me, but I'm thinking of switching to Ubuntu Server"06:59
wgrantHaha.06:59
wgrantGood to know.06:59
jtv"I didn't realize that Ubuntu had a Server edition"07:00
jtvOuch, he really wants to do it all by mouse.07:04
noodles775Good day :)07:05
jtvhi noodles77507:06
noodles775Hi jtv07:06
wgrantMorning noodles775.07:07
noodles775Hi William.07:08
noodles775jtv: thanks for the explanation about your objections to the with statement.07:09
jtvnoodles775: I didn't _want_ to write a novel, but given that it wasn't yet completely clear...  :-)07:11
noodles775jtv: no, it was exactly what I was interested to know.07:11
jtv"This Ubuntu website is amazing!  Very easy, it's listing all the advantages and features and technologies... fucking wow!"07:12
jtvHe's considering jumping ship from Windows 7, mainly because of licensing cost07:14
wgrantWow.07:14
jtvnoodles775: you came in in the middle of this...  I'm otp with a hardcore windows dev07:14
noodles775Ah, I was wondering what the context was.07:14
noodles775jtv: and regarding the benefit of switching back afterwards (back on the context manager), I was thinking whether it could be something re-usable for other tests, where in the setup code you need to switch db users to set something up and then switch back.07:16
noodles775wgrant: if you've time, can you add your thoughts/disagreements/clarifications to bug 536700 (I added a png of the current db tables with some notes).07:17
mupBug #536700: Present other build types in a PPA context <wellington> <Soyuz:Triaged> <https://launchpad.net/bugs/536700>07:17
noodles775And feel free to simply edit the description where necessary of course.07:19
jtvnoodles775: might be, yes, but a proper switch back may involve a commit; plus switching back and forth in a test is probably an indicator that you're doing too much in one test.  So I don't particularly feel like doing work to encourage it.  :)07:19
wgrantnoodles775: Is the source for that image around somewhere.07:21
wgrant?07:22
wgrantI want to shuffle it around a bit.07:22
noodles775wgrant: one tick, I'll upload the .dot file that I used.07:22
noodles775The only way I could produce it was to use postgres_autodoc to generate the source for *all* tables, and then edit the file removing all the other tables/relns...07:23
wgrantAh :(07:23
noodles775wgrant: http://people.canonical.com/~michaeln/tmp/launchpad_dev.dot07:24
noodles775I then ran that through `dot -Tpng -o build-related.png launchpad_dev.dot`07:25
wgrantI wonder why it is laying it out so badly.07:26
noodles775Yeah, I used dia once before for the recipe tables, which allows you to lay it out of course, but it was a pain as it crashed every few minutes, hence trying dot this time.07:27
noodles775(although it might be better on Lucid, that was on Karmic).07:28
wgrantOdd. Dia has been just about unchanged for many years, and is reasonably reliable for me.07:28
* wgrant tries.07:28
wgrant(and dot normally does a better job than it has this time)07:28
noodles775wgrant: I think it was more to do with the size of the file... it may have been that once I manually deleted all the other tables it was stable, I can't remember.07:29
wgrantAh.07:30
wgrantYeah, I guess it could be pretty huge otherwise.07:30
noodles775I generated a png of the complete schema just for fun... it was 22mb, and looked very scary ;)07:30
wgrantHeh.07:31
wgrantnoodles775: Dia gets very very slow with the entire scheme, but it hasn't crashed yet.07:44
noodles775Great.07:45
adeuringgood morning07:57
stubwgrant: Unfortunately, dot is pretty bad at laying out stuff like ORM diagrams. Its designed for other stuff.08:05
wgrantstub: So it seems :(08:17
wgrantkfogel: Oops. Pushing removal now.08:19
kfogelwgrant: ah, great.  I'm still up; I'll pqm-submit it afterwards.08:20
wgrantkfogel: Thanks.08:20
kfogelwgrant: you've tested your latest at /Draft, right?08:23
wgrantkfogel: Except for the comment removal, I believe so. let me try again, just in case.08:25
kfogelwgrant: I believe this fixes bug 436957; do you concur?08:25
mupBug #436957: Contributions script gets confused with db-stable=>devel merge <Launchpad Foundations:Triaged by kfogel> <https://launchpad.net/bugs/436957>08:25
wgrantkfogel: Ah, so there is a bug!08:25
wgrantAnd I even filed it.08:26
wgrantyes, it does fix it.08:26
kfogelwgrant: ok, listing in PQM msg08:26
kfogelwgrant: can you link your branch to the bug please/08:26
kfogel?08:26
wgrantkfogel: Done.08:27
kfogelwgrant: arrrgh.  how to make pqm submit your branch instead of ~kfogel/launchpad/community-contributions-fixes (which doesn't exist).08:29
kfogelsigh08:29
* kfogel growls at bzr pqm-submit08:29
wgrantIt does exist, though.08:30
wgrantOr at least yours popped up too when i searched for my branch.08:30
kfogelwgrant: well, I could push to my own area and then land that, but it seems so silly.08:31
kfogelI want to land *yours*.08:31
kfogelwgrant: hunh.  THe "--public-location" option seems to have done it.  I wouldn't have expected that to work.08:32
kfogelbzr pqm-submit -m "[r=kfogel][ui=none][bug=436957] In the community-contributions.py script, snarf contributors from both devel and db-devel branches, and fix a sorting bug." --public-location=lp:~wgrant/launchpad/community-contributions-fixes/08:32
kfogelwgrant: okay, it's in the Now Playing queue.  I'm off to bed.  Thank you SO much for fixing these long-standing problems!08:33
wgrantThanks for the review and landing!08:33
wgrantNight.08:33
jtvwgrant, noodles775: I'd like to make some Build and BuildQueue objects for my tests... do you happen to have any handy makeBuild[Queue] functions lying around that I could move into the factory?08:44
wgrantjtv: See SoyuzTestPublisher.08:45
noodles775jtv: yeah, the SoyuzTestPublisher is what we usually use.08:45
wgrantAlso see noodles' blog post.08:45
noodles775it's in lib/lp/soyuz/tests/test_publishing08:45
jtvcool, thanks08:45
wgrantstub: I wondered about indices. I guess we'll see.09:03
wgrantThanks.09:03
mrevell_Morning09:15
=== jelmer_ is now known as jelmer
=== noodles785 is now known as noodles775
deryckMorning, all.11:03
jmlmorning11:08
=== matsubara-afk is now known as matsubara
=== salgado-afk is now known as salgado
=== mrevell is now known as mrevell-lunch
jmlintellectronica, it turns out that renaming attributes is difficult.13:21
jmlintellectronica, thank heavens for our test suite13:21
intellectronicajml: right. feel free to rename them only in the api if it turns out too difficult to change them internally13:22
=== mrevell-lunch is now known as mrevell
jmlintellectronica, it's been easy enough, I just missed a couple of places.13:43
intellectronicacool13:49
rockstarHas anyone done anything about the buildbot failure?14:11
gary_posterrockstar: apparently not.  I'll own the db-devel failure, since it is the librarian.  Hopefully someone else can step up for the devel failure in malone.14:18
rockstargary_poster, I'm working on the devel one right now.14:18
gary_posterrockstar: awesome thanks14:19
rockstarhenninge, the buildbot failure email came to you 2 hours ago. Why did you not at least reply to the list with the causation?14:19
deryckadeuring, intellectronica, gmb, allenap -- is someone looking into our failure gary_poster mentions above? ^^14:19
deryckoh, I see rockstar says he is.14:20
deryckrockstar, thanks!14:20
henningerockstar: sorry, I was going to but got distracted ...14:20
* henninge hides in shame14:20
rockstarderyck, can I get you to review the fix?14:21
deryckrockstar, sure.14:23
=== jamalta-afk is now known as jamalta
gary_posterflacoste: I know zero about the librarian, and we have a seemingly spurious failure on db-devel because of it (https://lpbuildbot.canonical.com/builders/db_lp/builds/591/steps/shell_7/logs/summary).  Who knows the librarian right now?  You and stub?  ...I think I'm going to force db-devel right now but should not let this lie.14:26
flacostegary_poster: do we have /var/tmp/librarian.log14:27
gary_posterflacoste: no14:28
flacostegary_poster: there isn't much to do beside restarting, without that file we have no idea what went wrong14:29
flacostegary_poster: is that a first?14:29
gary_posterflacoste: to my knowledge, yes14:29
gary_postersomething to do in the abstract: contemplate buildbot slaves sending files if there are failues.  But that's wasted work, since we are moving the slaves to the DC14:30
adeuringderyck: no, I haven't looked yet14:30
deryckadeuring, no need now, rockstar is on it.  sorry for the mass ping.14:32
rockstarderyck, https://code.edge.launchpad.net/~rockstar/launchpad/testfix/+merge/2124314:33
* rockstar waits for diff14:33
rockstarderyck, diff is there.14:33
deryckrockstar, r=me.  Thanks!14:35
* deryck curses at page tests14:35
jmlgood news!15:04
adiroibanx15:05
jmlsubunit output is now in zope.testing on trunk15:05
jmlI can delete my horrible hack once they release.15:05
rockstargary_poster, so, the devel testfix is in and should make buildbot green there again.15:07
gary_posterrockstar: Awesome, thanks.  I forced db-devel, so we should now be out of testfix15:08
intellectronicamrevell: we shouldn't use bug.reporter@gmail.com in our text if we don't own this address. we should use example.com. we can change that in another branch, though.15:36
=== salgado is now known as salgado-lunch
mrevellintellectronica, Good point! I'll change it in this branch; no harm doing that.15:47
intellectronicamrevell: lovely, thanks15:47
=== matsubara is now known as matsubara-lunch
=== beuno is now known as beuno-lunch
gmballenap: Does this look sane? I went with BugWatchActivity rather than *History; it seemed to lead to nicer column names. http://pastebin.ubuntu.com/394114/16:29
allenapgmb: So, success = (error_type IS NULL)? Perhaps a column for the OOPS number?16:31
allenapgmb: Might need an index on bug_watch, but I guess that's up to stub.16:32
gmballenap: Yes, that's how I see us working out success. OOPS number is a good idea. Isn't bug_watch indexed by default, being an FK?16:33
allenapgmb: Maybe it is indexed.16:34
gmballenap: Ah, no, I'm misreading the output of \d.16:34
gmballenap: It probably should be indexed; I'll add one.16:35
=== deryck is now known as deryck[lunch]
=== matsubara-lunch is now known as matsubara
=== salgado-lunch is now known as salgado
Breaking_PittI have tried to putt the launchpad opent to all the computer in my network but I have get the following message17:28
Breaking_Pitt The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.17:28
Breaking_Pittfollowing this info https://dev.launchpad.net/Running/RemoteAccess17:29
Breaking_Pittsome advice about what can cause this?17:29
bjfif launchpad is telling me "This bug report was marked for expiration 164 days ago." then why hasn't it "expired", what does "expire" mean?17:33
=== beuno-lunch is now known as beuno
jmlbjf, "expire" means "automatically set to Invalid", I think.18:04
bjfjml, ok, but nothing seems to be "automatically" setting the bugs to Invalid18:04
=== deryck[lunch] is now known as deryck
deryckbjf, jml -- yes, expired means set to invalid.  This is currently disabled, so the messages are incorrect.18:08
deryckwe're doing work soon (likely this month) to renable it with an EXPIRED status.18:08
bjfif I were so inclined, can I hack on launchpad on lucid (the web page says Hardy, Jaunty and Karmic)?18:17
=== gary_poster is now known as gary-lunch
=== kfogel is now known as jimb_intestines
=== jimb_intestines is now known as kfogel
maxbbjf: it's less well supported19:07
maxbwhich is to say, yes, but expect things to break19:08
maxbmuch like lucid itself, I guess :-)19:08
maxbhttps://dev.launchpad.net/Running/Lucid19:08
=== gary-lunch is now known as gary_poster
jmlalso, the Canonical Launchpad folk are switching to lucid on the beta, so it'll probably get better quickly19:16
=== Ursinha-lunch is now known as Ursinha
deryckLater on, everyone.... have nice weekend.20:11
=== jamalta is now known as jamalta-afk
=== jamalta-afk is now known as jamalta
=== matsubara is now known as matsubara-afk
=== salgado is now known as salgado-afk
sinzuigary_poster: ping21:39
gary_postersinzui: pong.21:39
sinzuigary_poster: bug 538207 may require a bandaid or a team of people to fix. Or we can rollback one of salgado's landings21:40
mupBug #538207: Opps calling view/isRedirectInhibited from non-launchpadview <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/538207>21:40
gary_postersinzui: I was just looking at that one actually.21:40
gary_postersinzui: so lp.registry.browser.teammembership.TeamMembershipEditView does not inherit from LaunchpadView?  I was just about to go there in my investigation of what was going on21:41
sinzuiI favor fixing the views (I am certain I can fix the registry ones), but I think we have views that are defined in ZCML only, so they will never have the needed attribute21:41
gary_postersinzui: you mean without a view class.  Right.21:42
sinzuigary_poster: yes, that is what I mean21:42
gary_postersinzui: what do you think of this instead:21:44
sinzui ‏‎gary_poster: we would also have to fix this bug too bug 43307421:44
mupBug #433074: Remove launchpad-addform.pt and launchpad-editform.pt <tech-debt> <Launchpad Registry:Triaged> <https://launchpad.net/bugs/433074>21:44
gary_postermove isRedirectInhibited to the request21:44
gary_posterchange that template to say request/isRedirectInhibited21:44
gary_posterand move on21:44
sinzuigary_poster: ah...You are thinking much more clearly than myself21:44
sinzuiWe do get to fix a lot of tech-debt if we refuse to inline the python21:45
gary_postersinzui: ok, seems like you like that idea.  I don't know how critical this is.  What do you think?  Is this a drop everything and do it now, or do it early next week?  Without your adjustment, I will schedule for Monday21:46
sinzuiThis is not critical yet, collin disable the redirect to complete his task21:47
gary_postertrue21:47
gary_posterok thank you sinzui.  I'll follow up on bug21:47
sinzuiWe should fix it next week. I was concern that if we did want everything to descend from LPVIew, that we need to get several people involved21:48
gary_posterunderstood, cool21:48
wgrantgary_poster: Bug #529348 hasn't been fixed yet, has it? (re. #launchpad)21:55
gary_posterwgrant: it is waiting for an RC.  I21:55
gary_posterwill land the branch on devel when it goes into production21:56
gary_poster(so as not to call attention to it)21:56
wgrantHm, OK, so there is something else going on.21:56
wgrantYep.21:56
gary_posterhm, not on #launchpad, looking21:56
wgrantgary_poster: c_korn is getting an Unexpected Form Data error on what appears to be all LP forms.21:57
gary_posterthat's more than a little bit weird, yes, wgrant22:00
wgrantI don't think UFDs return an OOPS number, though they do give a traceback if you're in ~launchpad. :(22:01
gary_posterah, wgrant. :-(22:03
=== jamalta is now known as jamalta-afk
gary_postersinzui: I unintentionally stomped on you for https://bugs.edge.launchpad.net/launchpad-foundations/+bug/53823622:56
mupBug #538236: UnexpectedFormData submitting answers comment <Launchpad Foundations:Triaged> <https://launchpad.net/bugs/538236>22:56
sinzuistomp away22:57
gary_postersinzui, I was going to change this bug to say that we don't give adequate feedback for UnexpectedFormErrors.  I agree that user was missing REFERER.  However, there's no way for user or us to know that.  You agree?22:58
sinzuiyes. I agree22:59
gary_postercool thanks22:59
wgrantgary_poster: Simple solution being the adapter?23:08
peitschiehi everyone :)23:49
gary_posterwgrant: yes, the adapter to the AssertionError, as opposed to the adapter to something like a PublicAssertionError23:55
wgrantHm, OK.23:56
peitschiehey... i was wondering if anyone knows who is best to talk to about getting a patch into the python launchpad integration source?23:56
wgrantpeitschie: python-launchpad-integration, or python-launchpadlib?23:57
peitschiewgrant: the first :)23:57
wgrantpeitschie: I believe that's in Ubuntu's domain, not Launchpad's.23:58
peitschiewgrant: ahh.  you wouldn't happen to have the room for them handy by any chance would you?  Thanks by the way :)23:59
wgrantpeitschie: #ubuntu-bugs might be able to help.23:59

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