[16:00] <Ursinha> #startmeeting
[16:00] <Ursinha> Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.
[16:00] <MootBot> Meeting started at 10:00. The chair is Ursinha.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <Ursinha> [TOPIC] Roll Call
[16:00] <Ursinha> Apologies from matsubara, he's on leave today
[16:00] <MootBot> New Topic:  Roll Call
[16:01] <bigjools> me
[16:01] <flacoste> me
[16:01] <sinzui> me
[16:01] <Ursinha> me
[16:01] <Ursinha> of course
[16:01] <Ursinha> rockstar, hi
[16:01] <allenap> me
[16:01] <herb> me
[16:01] <rockstar> ni!
[16:01] <Ursinha> hahaha
[16:01] <Ursinha> henninge, hi!
[16:01] <henninge> hi Ursinha!
[16:01] <henninge> mi
[16:01] <stub> moo
[16:02] <Ursinha> so we're all here
[16:02] <Ursinha> [TOPIC] Agenda
[16:02] <Ursinha>  * Actions from last meeting
[16:02] <Ursinha>  * Oops report & Critical Bugs & Broken scripts
[16:02] <Ursinha>  * Operations report (mthaddon/herb/spm)
[16:02] <Ursinha>  * DBA report (stub)
[16:02] <MootBot> New Topic:  Agenda
[16:02] <Ursinha> [TOPIC] * Actions from last meeting
[16:02] <Ursinha> all items are okay, moving on
[16:02] <MootBot> New Topic:  * Actions from last meeting
[16:03] <Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[16:03] <Ursinha> we're also now going to talk about the scripts that are broken in this section
[16:03] <Ursinha> we want to make sure that these errors are tracked and solved
[16:03] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[16:03] <Ursinha> I have five bugs, one critical bug and two broken scripts
[16:03] <Ursinha> * OOPS report
[16:03] <Ursinha> sinzui, I have bug 396585 and bug 396383, maybe they can be fixed together?
[16:03] <Ursinha> flacoste, bug 397224 and bug 373837, this last one is targeted to 2.2.6
[16:03] <Ursinha> since, we had some DisconnectionError oopses yesterday, I decided to mention the bug here
[16:03] <Ursinha> rockstar, could you set the importance on bug 397220, please?
[16:04] <Ursinha> thanks ubottu
[16:05] <Ursinha> the ones for sinzui matsubara asked me to mention
[16:05] <sinzui> Ursinha: I am not sure about either of these
[16:06] <sinzui> Ursinha: the issue is somewhat deep. A foundational widget and the fact that we stupidly design schemes to use datetime stamps that no human will ever enter
[16:07] <flacoste> Ursinha: the DisconnectionError soft oops, i'll move to 2.2.7 and see if we have time to fix it, the other one, i don't understand
[16:07] <flacoste> Ursinha: i'll have a look at it and triage
[16:07] <sinzui> Ursinha: there are a few bugs open about the datetime stamps. I think all of those should be worked on. It is database work. I do not want to engage in that level of work for the next 3 months
[16:07] <Ursinha> sinzui, right
[16:07] <Ursinha> flacoste, thanks
[16:08] <Ursinha> [action] flacoste to take a look and triage bug 373837
[16:08] <MootBot> ACTION received:  flacoste to take a look and triage bug 373837
[16:08] <sinzui> Ursinha: The Launchpad date widget could be smarter. (which is why I changed the title) Note that the page that error came from has a date picker and states the expected format
[16:09] <Ursinha> sinzui, indeed
[16:09] <Ursinha> flacoste, and about the other one, the TraversalError one?
[16:09] <flacoste> Ursinha: that's the one i'm going to look and triage
[16:10] <Ursinha> flacoste, oh, I thought that would be the other one
[16:10] <flacoste> Ursinha: the other one, I'm moving milestone and we'll see if we have time to fix it
[16:10] <sinzui> Ursinha: so I think the oops is rightly classified as low. I'll look into fixing the date widget for another bug though, There are use cases where the default is the current date. The widget should show that
[16:10] <flacoste> Ursinha: any particular reason to bring it here?
[16:10] <Ursinha> [action] flacoste to take a look and triage bug 397224 and will move bug 373837 to 2.2.7 and see if it's possible to fix
[16:10] <MootBot> ACTION received:  flacoste to take a look and triage bug 397224 and will move bug 373837 to 2.2.7 and see if it's possible to fix
[16:11] <Ursinha> flacoste, we had some DisconnectionErrors yesterday and I saw this bug was targeted to an old milestone
[16:11] <flacoste> well, that's unrelated :-)
[16:11] <Ursinha> and it's a high bug
[16:11] <flacoste> well, foundations have a lot of High bugs unfortunately :-(
[16:12] <Ursinha> flacoste, I know :(
[16:12] <bigjools> you need a High High :)
[16:12] <flacoste> it's called Critical
[16:12] <bigjools> no, it's somewhere between!
[16:12] <flacoste> no, no
[16:12] <Ursinha> rockstar, hi :) can you set the importance in that bug, please?
[16:12] <flacoste> bigjools: there is critical, assigned High bugs and unassigned High bugs
[16:12] <Ursinha> I agree with flacoste
[16:13] <flacoste> Ursinha: so the DisconnetionError the 373837 bug are talking about are the ojnes we recover from
[16:13] <flacoste> Ursinha: when you see them on the OOPS report, we didn't recover from it
[16:13] <Ursinha> flacoste, hm, I see
[16:14] <Ursinha> the ones we didn't recover, do we know why?
[16:14] <flacoste> OOPS?
[16:15] <flacoste> (i didn't look)
[16:15] <Ursinha> flacoste, fetching one
[16:15] <Ursinha> flacoste, OOPS-1285J112
[16:16]  * Ursinha pokes the hell out of rockstar 
[16:17] <rockstar> Ursinha, sorry.
[16:17] <rockstar> Ursinha, I had done it when you asked.
[16:17] <Ursinha> sinzui, I'll make notes in the bugs then (if you didn't already - you're too fast :))
[16:17] <Ursinha> rockstar, thanks man
[16:17] <flacoste> Ursinha: that disconnection error is weird
[16:17] <flacoste> Ursinha: please file a bug about it
[16:17] <Ursinha> don't go away, I have one critical bug for you
[16:17] <Ursinha> flacoste, I will
[16:18] <Ursinha> [action] Ursinha to file a bug about OOPS-1285J112 and tell flacoste
[16:18] <MootBot> ACTION received:  Ursinha to file a bug about OOPS-1285J112 and tell flacoste
[16:18] <Ursinha> right
[16:18] <Ursinha> now I have one critical bug, that's code's
[16:18] <rockstar> Ursinha, is it the ACF one?
[16:18] <Ursinha> * Critical bugs
[16:18] <Ursinha> rockstar, bug 390563 is critical but has no activity since 06-29, is it really critical
[16:18] <Ursinha> tried to ask thumper yesterday about it but he was already gone, could you check this one with your team, please?
[16:19] <Ursinha> I guess so
[16:19]  * Ursinha looks
[16:19] <Ursinha> after guessing what ACF means :)
[16:19] <sinzui> Ursinha, flacoste: the datetime widget bug (while real) is not the bug in the oops as I read it. The restful marshaller expects a string, but the JSON serialized the numbers as numbers.
[16:19] <rockstar> Ursinha, there have been multiple team discussions about it.
[16:19] <Ursinha> rockstar, is that bug really critical?
[16:20] <sinzui> ^ We should probably add that as an expected exception to let standard error messaging handle the issue
[16:21] <Ursinha> sinzui, you may want to comment in the bug about it
[16:21] <rockstar> Ursinha, so, yes, it's really critical, but we're dependent on bzr fixing it.
[16:22] <rockstar> Ursinha, we may downgrade it for the sake of not misusing Critical.  We're still discussing it.
[16:22] <Ursinha> rockstar, I'm going to write this in the bug, so anyone that reads the bug report will know what's going on
[16:23] <Ursinha> rockstar, can you update the bug as soon as you have news, pretty please?
[16:23] <rockstar> Ursinha, will do.
[16:23] <Ursinha> thanks a lot rockstar
[16:27] <Ursinha> sinzui, do you want me to do something in that bug?
[16:27] <Ursinha> or maybe you want to discuss later
[16:27] <sinzui> I just updated it. It is an easy fix that I will make today since I have the file open
[16:27] <Ursinha> sinzui, great, thanks a lot
[16:28]  * sinzui just needs to workout where the bug really belongs? launchpad-foundation or lazr.restful
[16:28] <flacoste> leave it in foundations for now
[16:29] <Ursinha> let me just introduce the broken scripts we have, one seems to be yours sinzui
[16:29] <Ursinha> sinzui, productreleasefinder is having issues for quite some time, it's bug 394391
[16:29] <Ursinha> could you take a look at this one? maybe change the importance
[16:29] <Ursinha> also, I see that language-pack-exporter also failed to run, herb, henninge, do you know if that was expected?
[16:30] <henninge> I don't.
[16:30] <sinzui> Ursinha: I know how to fix that, and 3 other bugs. I am working on that on my own time
[16:30] <herb> I don't know either.
[16:30] <henninge> Ursinha: but it is a pretty long running script.
[16:30] <henninge> Ursinha: which run was it? when?
[16:31] <sinzui> Ursinha: I'm not certain it is not more important since it have been broken for 4 years and no one reported the bug before me
[16:31] <henninge> It is not uncommon for the script to be interrupted.
[16:31] <Ursinha> henninge, quoting the email: between 2009-07-07 17:00:04 and 2009-07-08 13:00:04
[16:32] <sinzui> Ursinha: but in the big picture, fixing 99% of all product-release-finder errors is a big win for me so I have started a plan to fix the bugs
[16:32] <Ursinha> sinzui, I see
[16:32]  * henninge just realizes he doesn't know the current schedule for that script.
[16:33] <Ursinha> sinzui, well, I think the important is that it's being fixed, not abandoned
[16:34] <Ursinha> that's what I'm trying to achieve mentioning them
[16:34] <sinzui> Ursinha: My team closed more than 40 low bugs last release. This is not forgotten there is a 30 point story attached to these PRF bugs
[16:34] <henninge> Ursinha: But really that script is monitored by the Ubuntu guys and they complain if they miss a language pack ...
[16:34] <Ursinha> gee
[16:34] <henninge> ArneGoetje to be exact.
[16:35] <Ursinha> henninge, monitored or maintained?
[16:35] <herb> l-p-e runs every monday,tuesday,thursday friday
[16:35] <herb> @2200 BST
[16:35] <herb> mon,fri for jaunty
[16:35] <herb> tue for intrepid
[16:35] <henninge> herb: ah, was gonna ask that
[16:35] <herb> thur for hardy
[16:36] <Ursinha> herb, thanks for the info
[16:36]  * Ursinha took notes
[16:36] <henninge> Ursinha: so that is that was the intrepid run failing. Not critical.
[16:36] <herb> the monday run finished at 0310 UTC on Tuesday
[16:36] <Ursinha> sinzui, thanks for that
[16:36] <Ursinha> henninge, right. if that keeps happening may I poke you? :)
[16:37] <herb> and it does look like intrepid was the one the failed
[16:37] <henninge> Ursinha: you may :)
[16:37] <herb> but it ran successfully the previous week.
[16:37]  * henninge looks forward to being poked by Ursinha because it will definietly happen ...
[16:38] <Ursinha> [action] Ursinha to watch the lang-pack-exporter script and poke henninge if it fails again
[16:38] <MootBot> ACTION received:  Ursinha to watch the lang-pack-exporter script and poke henninge if it fails again
[16:38] <Ursinha> well, let's move on
[16:38] <Ursinha> thank you all guys
[16:38] <Ursinha> [TOPIC] * Operations report (mthaddon/herb/spm)
[16:38] <MootBot> New Topic:  * Operations report (mthaddon/herb/spm)
[16:38] <herb> 2009-07-02 - Cherry picked r8700 to the scripts server.
[16:38] <herb> 2009-07-07 - Cherry picked r8766 to the scripts server.
[16:38] <herb> 2009-07-07 - Cherry picked r8729 to the importd slaves.
[16:38] <herb> Other than these it's been a quiet week. No service interruptions, a handful of minor incidents reported and no outstanding cherry pick or query requests.
[16:39] <Ursinha> herb, that's good to hear
[16:39] <Ursinha> does anyone have anything for herb?
[16:39] <Ursinha> hmm
[16:40] <Ursinha> moving on then :)
[16:40] <Ursinha> [TOPIC] * DBA report (stub)
[16:40] <MootBot> New Topic:  * DBA report (stub)
[16:40] <stub> A few accounts had to be repaired, fallout from the dodgy data repair work performed last week. These gave me more clues to track down some unreported ones, which have also been fixed. Hopefully everything is correct now.
[16:40] <stub> We will be testing the person pruner on staging, which should remove 90% of our Person records (which we can do because Account was split out of Person). When we run on production, it should have positive benefits throughout launchpad. The ValidPerson*Cache and TeamParticipation tables will shrink too, so three of our most common tables to join with will be much smaller. And lots of namespace will be freed up too.
[16:40] <stub> Not much in the way of db patches this cycle. Should have reviews all sorted and things ready to land tomorrow.
[16:40] <stub> oot.
[16:41] <Ursinha> stub, do you know if all accounts that were reporting problems on feedback@ were fixed?
[16:41] <stub> All that have been forwarded to me have been fixed.
[16:41] <stub> I don't personally monitor feedback@
[16:41] <Ursinha> okay, I'll check if there's any outstanding one
[16:42] <Ursinha> thanks stub
[16:42] <Ursinha> [action] Ursinha to check if all accounts requesting fix on feedback@ were fixed
[16:42] <MootBot> ACTION received:  Ursinha to check if all accounts requesting fix on feedback@ were fixed
[16:42] <Ursinha> anything else for stub?
[16:42] <Ursinha> or
[16:42] <Ursinha> anything else at all?
[16:43] <Ursinha> 5
[16:43] <Ursinha> 4
[16:43] <Ursinha> 3
[16:43] <Ursinha> 2
[16:43] <Ursinha> 1
[16:43] <Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs.
[16:43] <Ursinha> #endmeeting
[16:43] <MootBot> Meeting finished at 10:43.
[16:43] <Ursinha> thanks a lot guys
[16:43] <herb> thanks Ursinha
[16:45] <allenap> Ursinha: Dammit, I had to go out for 1 minute and I missed the anything else bit! Rats :)
[16:45] <allenap> I'll email the ml/
[16:45] <Ursinha> allenap, oops :)
[16:45] <allenap> Ursinha: Yep, my bad.
[16:45] <Ursinha> allenap, I should've poked you, sorry
[16:46] <allenap> Ursinha: No worries, I should have paid more attention.