/srv/irclogs.ubuntu.com/2011/01/10/#launchpad-dev.txt

thumperhow warm / cold is it in Dallas?00:08
thumpershould I pack warm clothing?00:08
jelmerthumper: I'd recommend a winter coat00:11
jelmerIt's 2 or 3 degrees (Celcius) at the moment I think00:11
thumpercrap00:15
thumperjelmer: I take it the hotel is warm enough?00:15
wgrantthumper: It's going to vary.00:15
wgrantthumper: It looks like 16-17 early next week.00:15
wgrantBut 1 tomorrow.00:15
wgrantAnd 4 later next week.00:15
thumperhmm...00:15
wgrantYou'll need to take roughly everything.00:15
jelmerthumper: the hotel is nicely warm. At least they don't have the airco on "freeze" mode like in some places.00:16
thumperwgrant: when are you heading out?00:16
wgrantthumper: Sunday.00:17
wgrantYou?00:18
thumpersame00:20
lavidhello! i'm trying to fix https://bugs.launchpad.net/bzr-hg/+bug/518510 (since it's blocking something else i'm working on) and i'm trying to get my launchpad instance to import a mercurial repository so i can reproduce the bug locally. i don't think that functionality works on dev instances of launchpad. does anyone have any tips on either: how to better debug this issue or how to get my dev instance of launchpad to also support runn00:27
_mup_Bug #518510: assertionerror in _find_most_recent_ancestor  <Bazaar Hg Plugin:Triaged> < https://launchpad.net/bugs/518510 >00:27
wgrantlavid: You shouldn't need to run a local Launchpad instance to test that.00:28
jmlhuwshimi: hello & welcome!00:29
lavidwgrant: fair enough. i guess i was hoping to get a better idea as to what's happening further up the stack trace. how'd you recommend tackling this?00:30
jelmerlavid: install bzr-hg as a plugin in bzr00:39
jelmerlavid: then try to clone a mercurial branch and doign incremental pulls into it00:39
wgrantI am trying to provide a precise recipe, but my machine is being objectionable.00:40
jelmerOne of the key things to the bug appears to be that it only happens on incremental pulls that import new revisions.00:40
lavidjelmer: cool. thanks. any tips for running the bzr-hg plugin via eclipse or some other visual debugger?00:41
jelmerlavid: Setting BZR_PDB=1 will open a pdb interactive debugger for you when an exception occurs in bzr00:41
jelmerI don't have any experience with Python in Eclipse, sorry00:42
pooliehi jelmer, wgrant00:42
lavidjelmer: ooh, tasty! thank you!00:42
jelmer'evening poolie00:42
wgrantMorning poolie.00:43
wgrantOr evening, I guess.00:43
jmlsee you all in a bit.01:00
* jml is off for stuff.01:01
thumperoh FSF02:23
thumperFFS02:23
thumpermake build dying on OSError: [Errno 4] Interrupted system call02:23
thumperstill02:23
=== Ursinha is now known as Ursinha-afk
wgrantthumper: Didn't it work on Friday? :/02:25
thumperwgrant: it did03:10
thumperwgrant: so it seems to be temperamental03:11
wgrantthumper: Yay.03:12
wgrantthumper: It wasn't a parallel make?03:12
thumperI don't think so03:13
wgrantthumper: Does it die on the .join()?03:16
thumperwgrant: no, times out03:16
thumperwgrant: actually, yes03:17
thumperFile "./utilities/create-lp-wadl-and-apidoc.py", line 86, in main03:17
thumpersorry, didn't look enough up the stack03:18
thumperwgrant: any idea how to get around the make problem?04:37
thumperI can't make run04:37
thumper:(04:37
thumperwhich makes it hard for me to test this thing04:37
=== lavid is now known as lavid_
wgrantthumper: You could hack it to not use multiprocessing. Or use multiprocessing, but serially.04:41
wgrantIt is tempting to debug, except for the whole POSIX signal fuckedness.04:41
* thumper loses the will to fix it on a Monday afternoon and calls it a day04:43
lifeless=== Top 10 Time Out Counts by Page ID ===06:06
lifeless    Hard / Soft  Page ID06:06
lifeless      63 /  293  BugTask:+index06:06
lifeless      36 / 4408  Archive:+index06:06
lifeless      21 /  294  Distribution:+bugs06:06
lifeless      13 /  112  ProjectGroupSet:CollectionResource:#project_groups06:06
lifeless      12 /  177  POFile:+translate06:06
lifeless      12 /    0  ProjectGroup:+milestones06:06
lifeless       8 /   12  NullBugTask:+index06:06
lifeless       7 /  201  Question:+index06:06
lifeless       6 /   13  Branch:+index06:06
lifeless       5 /    4  Cve:+index06:06
wgrantDoes anyone happen to know why Storm would be doing lots of 'SELECT 1 FROM foo WHERE foo.id=bar' in a test after invalidating the store?06:08
wgrantIt doesn't seem to do that in production.06:08
=== almaisan-away is now known as al-maisan
adeuringgood morning08:48
al-maisanGood morning !09:06
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== matsubara is now known as matsubara-lunch
=== henninge_ is now known as henninge
bigjoolsbenji: good morning14:09
benjimorning, julius maximus14:10
=== yofel_ is now known as yofel
bigjoolsheh, never been called that before14:10
bigjoolsI'm still struggling to get my dev environment fixed :(14:10
bigjoolsI downgraded launchpadlib to 1.6.5 (which is the last version I had an egg for)14:11
bigjoolsand the librarian won't start up in tests still, I  get loads of "No handlers could be found for logger "librarian""14:11
benjihmm, that doesn't sound related to launchpadlib; I can't imagine why it'd be screwing with the librarian's logger14:12
bigjoolsme neither14:13
jcsackettbenji: can you do qa for bug 686690?14:16
_mup_Bug #686690: 1.8.0 breaks login_with() API compat with existing credentials files, and forces keyrings <desktop-integration> <qa-needstesting> <regression> <launchpadlib :Fix Committed by benji> < https://launchpad.net/bugs/686690 >14:16
leonardrjcsackett: martin has confirmed the behavior, so i think we are ok14:18
jcsackettleonardr: ok, so i can mark that as qa-ok then?14:18
leonardrjcsackett: i'm about to upgrade launchpadlib in launchpad again. let's mark it qa-ok after i test that14:19
jcsackettleonardr: sounds good. thanks.14:19
jcsackettgmb: can you do qa for bug 686690?14:22
_mup_Bug #686690: 1.8.0 breaks login_with() API compat with existing credentials files, and forces keyrings <desktop-integration> <qa-needstesting> <regression> <launchpadlib :Fix Committed by leonardr> < https://launchpad.net/bugs/686690 >14:22
jcsackettsorry, gmb, bad copy paste. i meant bug 68367214:22
_mup_Bug #683672: Bug description in verbose footer should be indented by 2 spaces <lp-bugs> <qa-needstesting> <story-better-bug-notification> <trivial> <Launchpad itself:Fix Committed by gmb> < https://launchpad.net/bugs/683672 >14:22
gmbjcsackett: I will be doing so shortly; just waiting for deryck to get up-and-running with the staging mailbox.14:26
jcsackettgmb: cool, thanks.14:26
bigjoolsbenji: at what point is the keyring doing stuff it should not at import time?  When it loads the backend, or something else?14:50
bigjoolsI made a keyringrc.cfg to force an alternative backend and it still goes bang14:50
benjibigjools: it's certainly doing backend selection at import time, but it may well be doing other things; did your bang look related to the SIGCHLD stealing or something else?14:52
bigjoolsbenji: yeah, same EINTR stuff14:52
benjilet me look at the keyring code and see where it's doing that registration14:52
bigjoolsI forced anUncryptedFileKeyring backend14:53
bigjoolsbenji: I'm just trying to hack anything in to get me unblocked :(14:53
benjibigjools: hmm, I don't see anywhere that it explicitly registers a SIGCHLD handler; wait, didn't you say you downgraded to a pre-keyring launchpadlib?  if so, keyring shouldn't ever be imported14:55
bigjoolsbenji: I've gone back to the latest lplib since the other once had that logger problem14:57
bigjoolswell, the librarian problem14:57
benjiah, ok14:57
bigjoolsthe sigchld is registered somewhere in PyQt414:57
benjiI figured. :(14:57
bigjoolsaccording to my strace anyway14:57
bigjoolsit's all so frustrating :/14:58
benjibigjools: I think you can hack your launchpadlib to never import the keyring module (just comment out the import) and your LP will work (some tests will fail)14:59
bigjoolsok, never thought of the obvious :)14:59
=== matsubara-lunch is now known as matsubara
bigjoolsbenji: ok, that reduces me back to the No handlers could be found for logger "librarian"15:01
bigjoolsmaybe if I bang my head up the wall a bit more....!15:01
lifelessgary_poster: around?15:09
mwhudsonwho is release manager this time?15:09
mwhudsoni ought to know this15:09
gary_posterlifeless: I am15:09
gary_postermwhudson: jcsackett15:09
lifelessjc I thought15:09
mwhudsongary_poster: thanks15:09
lifelessgary_poster: hi; thanks for fast tracking the oops prefix updates15:09
gary_posterlifeless: hi, np.15:10
mwhudsonjcsackett: which revno is being released today?15:10
lifelessgary_poster: I'm wondering when that goes live (and if it will mean that the oops reports mailed to the list change accordingly)15:10
mwhudsonah, db-stable 1011915:10
gary_posterlifeless, the intent is today, and yes.15:11
lifelessmwhudson: huh no15:11
lifelesswe deploy from stable15:11
lifelesshttps://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html15:11
lifelessmwhudson: rev 1217715:11
lifelessmwhudson: and we're blocked on rev 1216715:11
lifelessjcsackett: ^15:11
mwhudsonah cool15:11
mwhudsonwell, not the being blocked part15:12
mwhudsonbut that means the fix i care about (and just qa-ed) is going to be released15:12
jcsackettmwhudson: we're deploying on the 12th, not the 10th. did i say the 10th in an email?15:13
mwhudsonerrr15:13
mwhudsonno,15:13
* jcsackett has written a lot of emails lately, very well could have goofed.15:13
mwhudsoncan i blame jetlag?15:13
mwhudson:-)15:13
jcsackettmwhudson: yes you can. :-)15:13
lifelessjcsackett: we ar edeploying from stable, right ?15:13
lifelessgary_poster: sweet, thanks.15:13
gary_posternp15:13
jcsackettlifeless: correct.15:14
lifelessjcsackett: great, my heart can start beating again15:14
jcsackettwe need to deploy at least through r12177 on stable.15:14
jcsackett10119 was the db revision we qa-ed and merged on friday, lifeless.15:15
lifelessjcsackett: thanks15:15
jcsackettnp.15:15
bigjoolsgary_poster: can you spare me a moment please?  I've worked around the keyring problem for now, but still have a problem with the librarian in tests :(   http://pastebin.ubuntu.com/552492/15:16
gary_posterbenji, leonardr, can either of you help bigjools ?15:16
benjigary_poster: I can take a look; not done much with the librarian yet though15:18
lifelessbigjools: thats weird15:18
gary_posterbenji: ack.  Lemme check in with the other pending pings and I'll see what needs to be handled15:18
bigjoolsbenji: I would have asked you but you were busy fixing the keyring :)15:18
lifelessbigjools: when did this start?15:18
bigjoolslifeless: once I worked around the keyring problems just now15:19
lifelessalso I hate python logging, I truely do15:19
bigjoolsI've not had a working dev environment since Thursday last week15:19
lifeless2011-01-10 20:30:34+0530 [-] No handlers could be found for logger "librarian"15:19
benjibigjools: it's nice to be loved15:19
bigjoolslifeless: I share your hate15:19
lifeless-not- a sane failur emode15:19
lifelessbigjools: do you have a /var/tmp/fatsam.test/librarian.pid ?15:20
bigjoolslifeless: ignore that, it's a relic of the earlier failure15:21
lifelessok15:21
bigjoolsI delete fatsam each run15:21
lifelessok15:21
lifelessso its leaving the pid file when it fails to start? Could you file a bug on that - we should fix that too15:21
* bigjools tries again15:21
bigjoolsdidn't we discuss that some time ago and it was hard to fix for some reason?15:22
bigjoolsARGHHHHH15:22
bigjoolsit's working now15:22
lifelessdunno; the code is a lot cleaner than it was it should be fixable.15:22
bigjoolsthere was a librarian left running15:23
lifelessdeleting old ones on start is problematic; dealing with a failed start is simpler15:23
bigjoolsthought I'd killed it15:23
lifelesshowever it sounds like it was behaving correctly ;)15:23
bigjoolsdefine correctly :)15:23
lifelessnot connecting you to an existing librarian on the statically defined port15:23
lifelesshowever the diagnostics are terrible - please do file a bug that it didn't manage to tell you15:24
bigjoolsroger15:24
gary_posterbigjools, benji, sorry, I misunderstood thought the librarian thing was a webservice/keyring thing15:24
gary_posterbut so anyway, that's "resolved" enough for benji to get back to what he was doing before, bigjools15:25
gary_poster?15:25
lifelessit might have been :)15:25
bigjoolsgary_poster: in all fairness, it might have been!  I had no idea what was up.15:25
gary_posterheh15:25
bigjoolsgary_poster: yes, thanks, I've commented out the keyring import for now15:25
bigjoolslifeless: to confirm, what did you expect it to do that it was not doing?  Telling you about an existing librarian, or something else?15:27
gary_posterbigjools: ack, and that solved it, or...something solved and you are moving on?15:27
bigjoolsgary_poster: "worked around" would be the right phrase :)  benji is fixing the keyring code to not do stuff when it's imported15:28
lifelesshi flacoste15:28
gary_posterbigjools: lol, ack, right.  thanks15:28
bigjoolsgary_poster: I'm gonna have to do some work now it's fixed.  Darn.15:29
gary_posterbigjools: lol, sorry :-)15:30
bigjools:)15:30
flacostehi lifeless15:45
=== flacoste changed the topic of #launchpad-dev to: Launchpad Development Channel | New starters: huwshimi | 11.01 Release Week 3 | PQM in RC for devel | RM: jcsackett | firefighting: - | Get the code: https:/​/​dev.launchpad.net/​Getting
bigjoolssinzui: around?15:47
sinzuibigjools: yes15:56
bigjoolssinzui: when you have a moment, it's not urgent, but I'd appreciate your feedback on the mockups for the new +addseries page and its new +initseries, see https://dev.launchpad.net/LEP/DerivativeDistributions#Mockups15:57
sinzuibigjools: thanks15:58
bigjoolssinzui: thank *you*15:58
jcsackettbenji: are bugs 651852 and 669701 qa-able?16:05
benjijcsackett: looking16:06
jcsackettthanks.16:06
lifeless /win 7016:07
benjijcsackett: both are; 651852 is now marked qa-ok, but 669701 will have to be QAed by someone that has write permission for feature flag rules, a LOSA perhaps16:08
jcsackettbenji: dig.16:09
=== Ursinha is now known as Ursinha-lunch
jcsackettthanks.16:09
lifeless /win 7016:18
lifelessbah16:18
=== beuno is now known as beuno-lunch
lifelesswgrant: *all* oops/timeout are 'high'16:29
lifelesswgrant: per ZeroOopsPolicy16:29
gmbjcsackett: Bug 683672 is now qa-ok.16:54
_mup_Bug #683672: Bug description in verbose footer should be indented by 2 spaces <lp-bugs> <qa-ok> <story-better-bug-notification> <trivial> <Launchpad itself:Fix Committed by gmb> < https://launchpad.net/bugs/683672 >16:54
jcsackettgmb: thanks!16:54
flacostelifeless: we have a problem, project can only be part of one project group16:55
flacostewhich means that lazr projects cannot be part of both lazr and launchpad16:56
flacostewe could make them all part of launchpad16:56
flacostemaybe except lazr-js16:56
flacosteand even then16:56
lifelessflacoste: ah, yes we should fix that ;)17:00
flacostelifeless: i'm moving all of them to launchpad, leaving a URL to the other lazr project17:00
flacosteanything lazr is vapourware17:00
flacosteso not really worth separating out17:00
=== deryck is now known as deryck[lunch]
=== benji is now known as benji-lunch
lifelessflacoste: ah17:03
lifelessflacoste: I fear that if we don't have a brain-dead-simple way of querying all the bugs that lp interrupt squads should care about, that ones outside the default-set will get starved17:04
flacostelifeless: i agree17:04
flacostethat's why i'm moving all the projects which we maintain to launchpad-project17:04
lifeless\o/17:04
flacosteexcept storm17:05
lifelesswhich we don't maintain :)17:05
flacosteright17:05
flacosteand when it affects us17:05
flacostewe usually have a bugtask on launchpad for it17:05
flacostelifeless: all done17:09
lifelessgaaarh17:12
lifelessthe list of projects is cached I guess17:12
bigjoolsflacoste: what about launchpad-buildd?17:12
flacostelifeless: it is17:12
lifeless:(17:12
flacostebigjools: already there i think17:12
* lifeless embugginates17:12
lifeless'launchpad auto build system'17:12
bigjoolsflacoste: well generally I mean, it wasn't folded into launchpad like the others, do we intend to keep it separate?17:13
bigjools(given the bug about splitting out the code from the tree)17:13
flacostebigjools: being part of Launchpad project is orthogonal to having a separate tree17:13
flacostebigjools: wait a moment17:14
flacostea) yes, it should be a separate project17:14
flacosteb) it should be part of the launchpad-project so that its bugs are part of the overall bugs we need to fix17:14
flacostelist17:14
bigjoolsok17:14
flacostec) we should move it out in a separate code tree17:14
bigjoolssounds reasonable to me17:14
flacostelike lazr.restful or wadllib17:14
* flacoste goes to lunch17:15
lifelessflacoste: so, I can bug triage now17:35
lifeless?17:35
=== Ursinha-lunch is now known as Ursinha
=== beuno-lunch is now known as beuno
=== deryck[lunch] is now known as deryck
=== gary_poster is now known as gary-lunch
flacostelifeless: yep18:27
=== al-maisan is now known as almaisan-away
sinzuimatsubara: Ursinha: I am looking a bug 687465. The code thinks it is reporting oopses, but I never see them in oops reports. Can you confirm that production mailman is generating oopses and we rsync them19:27
_mup_Bug #687465: add oops reporting to the xmlrpc queue runner <lp-registry> <mailing-lists> <Launchpad itself:Triaged> < https://launchpad.net/bugs/687465 >19:27
matsubarasinzui, /me looks19:27
=== gary-lunch is now known as gary_poster
matsubarasinzui, which machine does production mailman runs one?19:32
sinzuimatsubara: I do not know. Chex do you know ^19:33
Chexmatsubara: forster19:37
matsubarasinzui, there's a /srv/launchpad.net-logs/scripts/forster/mailman-xmlrpc dir in devpad and the last oops dir there is 2009-10-06. I'm trying to find a newer mailman-xmlrpc dir in devpad19:42
matsubaraChex, thanks19:42
matsubarasinzui, ./staging/asuka/mailman-xmlrpc19:50
matsubara./scripts/forster/mailman-xmlrpc19:50
matsubara./qastaging/asuka/mailman-xmlrpc19:50
matsubarathose are the dirs where I'd expect mailman oopses to show up19:50
matsubaraand by mailman oopses I mean those with MMX prefix19:51
matsubaraor QSMMX for qastaging nad SMMX for staging19:51
sinzuimatsubara: I think the product config says the oopses start with a c19:51
sinzuimatsubara: as I noted in the bug, I found bugs in the database there were never in the daily reports19:52
pcjc2sinzui?19:55
matsubarasinzui, the reason OOPS-1795C1521 doesn't appear in the report (https://devpad.canonical.com/~lpqateam/oops-summaries/lpnet-2010-11-30.html#informational-only-errors) is because it's hidden amongst the 2858 error of the same kind. the report just show a sample of 1020:02
matsubarait's very likely OOPS-1795D3104 doesn't show up for the same reason20:02
sinzui:(20:02
pcjc2hi Sinzui, I've provided updated information on the my LP bugs you triaged earlier20:03
sinzuimatsubara: what can we do to ensure mailman oopses are not information-only-errors20:03
sinzuipcjc2: I dedupped the bug20:04
sinzuiwell I undid regardless of that word I just mad up20:04
sinzuimade20:04
* sinzui gives up20:04
pcjc2cool - was a little frustrating to see them closed down so quickly given a LP dev had asked me to file them20:05
matsubarasinzui, why do you think OOPS-1795C1521 is a mailman oops?20:05
pcjc2Is the canonical-identity-provider code available to take a poke at?20:06
pcjc2or is that a closed-source part of LP?20:06
sinzuimatsubara: the TB: Module lp.registry.xmlrpc.mailinglist, line 200, in getMembershipInformation20:07
matsubarasinzui, OOPS-1795C1521 has no traceback information and is the informational only oops20:08
sinzuimatsubara: since mailman is an antonymous system, most of its issues will appear  related to MailingListAPIView20:08
matsubarasinzui, OOPS-1795D3104 is not an informational only oops20:08
sinzuihttps://lp-oops.canonical.com/oops.py/?oopsid=1795D310420:08
sinzuihas a tb20:08
matsubarayep, and that one is not informational only20:09
* pcjc2 found the identity-provider branch20:09
sinzuimatsubara: as for https://lp-oops.canonical.com/oops.py/?oopsid=1795D3104, Chex saw it in mailman's log we know the runner reported it20:09
sinzuimatsubara: I have the death trail of Mailman's failure in November. There are a lot of oopses it reported hours before it's death http://pastebin.ubuntu.com/552570/20:13
matsubarasinzui, OOPS-1795D3104 is a timeout. it didn't show up in the report because there were a total of 218 unique timeouts on that day and only 15 showed up in the report https://devpad.canonical.com/~lpqateam/oops-summaries/lpnet-2010-11-30.html#time-outs20:15
sinzuimatsubara: okay. We may need to think about that because mailman thinks it is being DoSed20:18
matsubarasinzui, so the runner tried to get_subscriptions but LP was timing out on that call and recording each oops correctly20:18
pcjc2I'm trying to login to the staging server, but it won't auth with the API provider20:18
pcjc2Sorry - OpenID provider...20:18
pcjc2Does the staging server sync the user database for production regularly? The user I'm trying to use is for a robot, and I created the account only a couple of days ago20:19
sinzuimatsubara: since we are getting the oopses. I will change mailman to send the 503 and 504 information as oopses so we see mailmans conclusion that life has no meaning and kills itself20:19
sinzuipcjc2: I do not have an answer. SSO is not launchpad and we do not control it. Canonical's ISD group does and they can set Lp staging to use their staging version of SSO. We do not know the state of their DB20:20
pcjc2ok I hadn't appreciated the division there20:21
sinzuipcjc2: try qastaging. The DB is many weeks old, but it does using production SSO (login.ubuntu.com)20:21
pcjc2is that LP database ok to screw with arbitrarily?20:22
pcjc2(I'm writing a robot, and don't want to mess things up where I shouldn't!)20:22
sinzuipcjc2: as long as there is a login.launchpad.net, no one will know there that they have two separate systems20:22
sinzuipcjc2: you can do what ever you need. The DB will be restored in a week or two20:22
pcjc2Is there a political divide?20:22
StevenKAwww, mwhudson's cloak changed :-(20:23
pcjc2ok - will create some bugs against our project and play with them20:23
mwhudsononly 8 months later or whatever20:23
matsubarasinzui, sounds sensible. at least that way we'll see those reported as XMLP kind of oopses, right?20:24
lifelesspcjc2: there are different teams20:24
pcjc2ValueError: qastaging is not a valid URL or an alias for any Launchpad server20:24
lifelesspcjc2: we see eye to eye but we (effectively) cannot change stuff in that code20:24
sinzuipcjc2: No. We do not want to be in the OpenID biz. Users want more from it than we do. So gave it to Ubuntu. We want to allow users to login using any OpenID service. The problem is that setting up a domain that looks like launchpad, bug does not work like Launchpad was a mistake20:24
pcjc2credentials.get_request_token(web_root="qastaging") <-- is there a URL I can use there instead?20:25
pcjc2sinzui: I'm glad you want to let logins from any OpenID service20:25
pcjc2We just migrated our bugs and stuff to LP, and some of our users wanted to use existing OpenID logins etc..20:25
sinzuipcjc2: I use launchpadlib.launchpad.Launchpad.login_with('testing', 'https://api.qastaging.launchpad.net/')20:29
=== almaisan-away is now known as al-maisan
pcjc2needed to drop the "api." for the credentials.get_request_token(web_root="https://qastaging.launchpad.net"). but it worked20:40
pcjc2Thanks20:40
=== matsubara is now known as matsubara-afk
* pcjc2 does find the distinction between loging on to LP and loging on at login.launchpad.net a little amusing20:43
pcjc2but it seems less strange to me as I know vaguely how it works ;)20:43
pcjc2I wish LP had an option to let me masquerade as another user20:44
pcjc2(my robot), rather than forcing me to log off all the way20:44
pcjc2https://launchpad.net/~gpleda-launchpad-robot20:45
pcjc2Would also be nice to have somewhere that I (or the developer team) "own" that user account20:45
sinzuiThere is a very old bug suggesting that we provide I way to become another user or change privileges temporarily. I do not think we plan to work on it any time soon.20:45
pcjc2sounds like many of the feature requests for our project.. nice idea.. no time ;)20:46
pcjc2(or other priorities)20:46
=== Ursinha is now known as Ursinha-afk
pcjc2Is there a schedule for when DB updates to staging / qastaging get made?20:55
pcjc2OOPS-1836QS2421:04
pcjc2Can someone check that for me?21:04
pcjc2Getting a HTTP Error 404: Not Found for bug.bug_tasks on this bug:21:05
pcjc2https://bugs.staging.launchpad.net/geda/+bug/69399121:05
_mup_Bug #693991: compiz crashed with SIGSEGV in nux::IOpenGLSurface::UnlockRect() <amd64> <apport-crash> <apport-failed-retrace> <decorations> <gnome> <metacity> <natty> <window> <compiz (Ubuntu):New> < https://launchpad.net/bugs/693991 >21:05
jcsackettis there an easy way to run ec2 tests with a different version of dependencies? say if i'm working on changes to a lazr lib? i can't find anything in the wiki.21:06
lifelesspcjc2: hasn't mirrored yet21:07
lifelessjcsackett: edit your versions.cfg21:07
lifelessand setup.py21:08
lifelessec2 test is meant to propogate that21:08
jcsackettlifeless: i may be (read: probably am) wrong, but it looks like that requires existing version numbers. is there a way to use something that only exists as a branch i'm working on?21:11
jcsacketti see my earlier question wasn't clear. my apologies.21:11
lifelessjcsackett: once you've added it to the download cache, its fine21:11
jcsackettlifeless: ah! so i add the tarball or what have you to that, and ec2 pulls info from there? i didn't realize. that's cool.21:12
lifelessits documented on ze wiki I think21:12
lifelessyou add the tarball, bzr add, bzr commit21:12
pcjc2OOPS-1836QS42  ?21:12
lifelesspcjc2: also won't have syncted yet :)21:13
jcsackettlifeless: dig. thanks!21:13
pcjc2what is the timeframe?21:13
lifelesspcjc2: generally 15 minutes IIRC21:13
pcjc2gah, I'm being a tool...21:13
pcjc2I filed the bug on staging, not qastaging21:13
mwhudsonwgrant: are you awake yet?21:31
lifelesspcjc2: hmm, so21:36
lifelessoops 1836QS2421:36
lifelesshow did you generate that oops ?21:36
pcjc2from the API, accessing a non-existant bug21:36
lifelesshmm21:36
lifelessshouldn't OOPS21:36
pcjc2Here is a real one which is annoying me: 1836O154321:36
lifelesswhat was the API call you made ?21:37
pcjc2OOPS-1836O1543 (this was jut now, so need to wait a bit) It is a bug search timing out21:37
lifelesssure21:37
lifelessso, QS2421:37
lifelesswhat does the code look like that triggered it ?21:37
jmllifeless: hello. where are you?21:38
lifelessB21:38
pcjc2>>> from launchpadlib.launchpad import Launchpad21:38
pcjc2>>> from launchpadlib.credentials import Credentials21:38
pcjc2>>> credentials = Credentials.load_from_path ("commit_robot_qastaging.credentials")21:38
pcjc2>>> launchpad = Launchpad(credentials, service_root="https://api.qastaging.launchpad.net")21:38
pcjc2>>> bug=launchpad.bugs[123456789]21:38
pcjc2>>> print bug21:38
lifelesslinaro room21:38
pcjc2In the response, there was: x-lazr-oopsid: OOPS-1836QS4621:39
lifelessyeah21:39
jmllifeless: do you want to grind more on persistence layer stuff?21:39
lifelesssure21:39
pcjc2The search oops I'm hitting is via the normal web interface - was looking to find all open bugs in the project with no tags21:40
lifelessjml: can yo ucome here first ?21:40
lifelesspcjc2: yeah, hang on21:40
lifelesspcjc2: need to wait for it to sync21:40
jmllifeless: sure.21:42
jmllifeless: omw21:43
lifelesspcjc2: O1543 is still pending rsync21:43
jmllifeless: which linaro room?21:44
lifelessballroom B21:44
jmllifeless: I'll try again.21:44
lifelessback right21:45
lifelessright of main desk21:45
jmlhuwshimi: hello21:53
huwshimijml: Morning21:53
jmlhuwshimi: how'd it go yesterday?21:54
lifelesspcjc2: ok21:54
lifelesspcjc2: slow sql21:54
huwshimijml: Good thanks. Just getting Launchpad set up locally21:54
lifelesspcjc2: what did you search for ?21:55
jmlhuwshimi: all set up w/ wiki access?21:55
huwshimijml: Yup21:55
wgrantmwhudson: Hi.21:57
wgrantlifeless: It's only a soft timeout so far.21:58
lifelesswgrant: ah; well it can be real anytime you like :>21:58
mwhudsonwgrant: hi, i wanted to ask you about openid identifier/account merge crazyness21:58
mwhudsonwgrant: but we found mbarnett instead21:58
lifelesspcjc2: https://bugs.launchpad.net/launchpad/+bug/70125021:59
_mup_Bug #701250: Product:+bugs timeout with search  <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/701250 >21:59
wgrantmwhudson: It should all be pretty much fixed soon, after the next SSO deployment.21:59
mbarnettwoot22:00
wgrantBut who knows when that will be.22:00
lifelessmatsubara-afk: \o/ codebrowse oopses are visible22:02
=== al-maisan is now known as almaisan-away
pcjc2lifeless: 17 seconds is a long SQL query...22:39
pcjc2Bad DB index?22:39
sinzuipcjc2: Most long queries are because the there to too much data being collected, most of which will not be used22:43
pcjc2in terms of row count, or data join'd from other tables?22:43
sinzuidata in other tables and columns. Bug queries are undermined by the ORM in a way22:44
flacostehi huwshimi! welcome aboard!22:50
lifelesspcjc2: indeed22:53
lifelesspcjc2: we need to debug this a little against staging22:53
pcjc2we? as in me you and me?22:53
flacostehuwshimi: subscription to canonical-launchpad approved22:59
jmlhuwshimi: btw, give us a holler if there are issues with getting a dev env set up22:59
huwshimijml: Thank you. It's taking a while to pull everything down, but it is working.23:01
StevenK*Another* Sydney-sider?23:02
wgrantToo many.23:02
StevenKOh, so clearly I need to move to Melbourne?23:02
wgrantYes.23:02
wgrantOr follow the others' lead, and move to another country!23:02
mwhudsoni guess QLD is not looking such a good option currently23:02
StevenKQueensland has other problems.23:03
StevenKSuch as being full of Queenslanders.23:03
jmlStevenK: now now.23:03
huwshimiflacoste: Thanks you! Sorry only just noticed your message.23:10
mkanatWhat does it take to get ~/launchpad-pqm/loggerhead to be set up on qastaging as codebrowse, and then pushed to production?23:16
mkanat~launchpad-pqm/ that is.23:16
mkanatOkay, I guess I need to update sourcedeps first.23:17
mkanatDo I propose merges against edge and then those go into stable...?23:29
StevenKmkanat: No, propose merges against lp:launchpad, which is the right place23:30
mkanatOkay.23:30
lifelessthere is no edge23:32
mkanatlifeless: There's lp:launchpad/edge23:32
jmllifeless: hello23:32
lifelesslet me just delete that23:33
mkanatlifeless: Okay.23:33

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