1 <Ursinha> #startmeeting
2 <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.
3 <MootBot> Meeting started at 10:00. The chair is Ursinha.
4 <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
5 * flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting
6 <Ursinha> [TOPIC] Roll Call
7 <Ursinha> Apologies from matsubara, he's on leave today
8 <MootBot> New Topic: Roll Call
9 <bigjools> me
10 <flacoste> me
11 <sinzui> me
12 <Ursinha> me
13 <Ursinha> of course
14 <Ursinha> rockstar, hi
15 <allenap> me
16 <herb> me
17 <rockstar> ni!
18 <Ursinha> hahaha
19 <Ursinha> henninge, hi!
20 <henninge> hi Ursinha!
21 <henninge> mi
22 <stub> moo
23 <Ursinha> so we're all here
24 <Ursinha> [TOPIC] Agenda
25 <Ursinha> * Actions from last meeting
26 <Ursinha> * Oops report & Critical Bugs & Broken scripts
27 <Ursinha> * Operations report (mthaddon/herb/spm)
28 <Ursinha> * DBA report (stub)
29 <MootBot> New Topic: Agenda
30 <Ursinha> [TOPIC] * Actions from last meeting
31 <Ursinha> all items are okay, moving on
32 <MootBot> New Topic: * Actions from last meeting
33 <Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
34 <Ursinha> we're also now going to talk about the scripts that are broken in this section
35 <Ursinha> we want to make sure that these errors are tracked and solved
36 <MootBot> New Topic: * Oops report & Critical Bugs & Broken scripts
37 <Ursinha> I have five bugs, one critical bug and two broken scripts
38 <Ursinha> * OOPS report
39 <Ursinha> sinzui, I have bug 396585 and bug 396383, maybe they can be fixed together?
40 <Ursinha> flacoste, bug 397224 and bug 373837, this last one is targeted to 2.2.6
41 <Ursinha> since, we had some DisconnectionError oopses yesterday, I decided to mention the bug here
42 <Ursinha> rockstar, could you set the importance on bug 397220, please?
43 <ubottu> Launchpad bug 396585 in launchpad-registry "/projects/+review-licenses OOPSes with subscription date" [Low,Triaged] https://launchpad.net/bugs/396585
44 <ubottu> Launchpad bug 396383 in launchpad-foundations "date widget could be smarter, giving a date in format DDMMYYYY OOPSes" [Low,Triaged] https://launchpad.net/bugs/396383
45 <ubottu> Launchpad bug 397224 in launchpad-foundations "TraversalError in person page accessing openid_identity_url" [Undecided,New] https://launchpad.net/bugs/397224
46 <ubottu> Launchpad bug 373837 in launchpad-foundations "DisconnectionError should log a soft OOPS" [High,Triaged] https://launchpad.net/bugs/373837
47 <ubottu> Launchpad bug 397220 in launchpad-code "Better validation for project field in new code import form" [Undecided,Triaged] https://launchpad.net/bugs/397220
48 <Ursinha> thanks ubottu
49 <Ursinha> the ones for sinzui matsubara asked me to mention
50 <sinzui> Ursinha: I am not sure about either of these
51 <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
52 <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
53 <flacoste> Ursinha: i'll have a look at it and triage
54 <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
55 <Ursinha> sinzui, right
56 <Ursinha> flacoste, thanks
57 <Ursinha> [action] flacoste to take a look and triage bug 373837
58 <ubottu> Launchpad bug 373837 in launchpad-foundations "DisconnectionError should log a soft OOPS" [High,Triaged] https://launchpad.net/bugs/373837
59 <MootBot> ACTION received: flacoste to take a look and triage bug 373837
60 * gmb has quit ("Coyote finally caught me")
61 * gmb (n=gmb@seagoon.grahambinns.com) has joined #launchpad-meeting
62 <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
63 <Ursinha> sinzui, indeed
64 <Ursinha> flacoste, and about the other one, the TraversalError one?
65 <flacoste> Ursinha: that's the one i'm going to look and triage
66 <Ursinha> flacoste, oh, I thought that would be the other one
67 <flacoste> Ursinha: the other one, I'm moving milestone and we'll see if we have time to fix it
68 <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
69 <flacoste> Ursinha: any particular reason to bring it here?
70 <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
71 <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
72 <ubottu> Launchpad bug 397224 in launchpad-foundations "TraversalError in person page accessing openid_identity_url" [Undecided,New] https://launchpad.net/bugs/397224
73 <ubottu> Launchpad bug 373837 in launchpad-foundations "DisconnectionError should log a soft OOPS" [High,Triaged] https://launchpad.net/bugs/373837
74 <Ursinha> flacoste, we had some DisconnectionErrors yesterday and I saw this bug was targeted to an old milestone
75 <flacoste> well, that's unrelated :-)
76 <Ursinha> and it's a high bug
77 <flacoste> well, foundations have a lot of High bugs unfortunately :-(
78 <Ursinha> flacoste, I know :(
79 <bigjools> you need a High High :)
80 <flacoste> it's called Critical
81 <bigjools> no, it's somewhere between!
82 <flacoste> no, no
83 <Ursinha> rockstar, hi :) can you set the importance in that bug, please?
84 <flacoste> bigjools: there is critical, assigned High bugs and unassigned High bugs
85 <Ursinha> I agree with flacoste
86 <flacoste> Ursinha: so the DisconnetionError the 373837 bug are talking about are the ojnes we recover from
87 <flacoste> Ursinha: when you see them on the OOPS report, we didn't recover from it
88 <Ursinha> flacoste, hm, I see
89 <Ursinha> the ones we didn't recover, do we know why?
90 <flacoste> OOPS?
91 <flacoste> (i didn't look)
92 <Ursinha> flacoste, fetching one
93 <Ursinha> flacoste, OOPS-1285J112
94 <ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1285J112
95 * Ursinha pokes the hell out of rockstar
96 <rockstar> Ursinha, sorry.
97 <rockstar> Ursinha, I had done it when you asked.
98 <Ursinha> sinzui, I'll make notes in the bugs then (if you didn't already - you're too fast :))
99 <Ursinha> rockstar, thanks man
100 <flacoste> Ursinha: that disconnection error is weird
101 <flacoste> Ursinha: please file a bug about it
102 <Ursinha> don't go away, I have one critical bug for you
103 <Ursinha> flacoste, I will
104 <Ursinha> [action] Ursinha to file a bug about OOPS-1285J112 and tell flacoste
105 <ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1285J112
106 <MootBot> ACTION received: Ursinha to file a bug about OOPS-1285J112 and tell flacoste
107 <ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1285J112
108 <Ursinha> right
109 <Ursinha> now I have one critical bug, that's code's
110 <rockstar> Ursinha, is it the ACF one?
111 <Ursinha> * Critical bugs
112 <Ursinha> rockstar, bug 390563 is critical but has no activity since 06-29, is it really critical
113 <Ursinha> tried to ask thumper yesterday about it but he was already gone, could you check this one with your team, please?
114 <ubottu> Launchpad bug 390563 in bzr "absent factory exception from smart server when streaming 2a stacked branches" [Critical,In progress] https://launchpad.net/bugs/390563
115 <Ursinha> I guess so
116 * Ursinha looks
117 <Ursinha> after guessing what ACF means :)
118 <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.
119 <rockstar> Ursinha, there have been multiple team discussions about it.
120 <Ursinha> rockstar, is that bug really critical?
121 <sinzui> ^ We should probably add that as an expected exception to let standard error messaging handle the issue
122 * ejat (n=fenris@60.52.34.169) has joined #launchpad-meeting
123 <Ursinha> sinzui, you may want to comment in the bug about it
124 <rockstar> Ursinha, so, yes, it's really critical, but we're dependent on bzr fixing it.
125 * e-jat has quit (Read error: 104 (Connection reset by peer))
126 <rockstar> Ursinha, we may downgrade it for the sake of not misusing Critical. We're still discussing it.
127 <Ursinha> rockstar, I'm going to write this in the bug, so anyone that reads the bug report will know what's going on
128 <Ursinha> rockstar, can you update the bug as soon as you have news, pretty please?
129 <rockstar> Ursinha, will do.
130 <Ursinha> thanks a lot rockstar
131 <Ursinha> sinzui, do you want me to do something in that bug?
132 <Ursinha> or maybe you want to discuss later
133 <sinzui> I just updated it. It is an easy fix that I will make today since I have the file open
134 <Ursinha> sinzui, great, thanks a lot
135 * sinzui just needs to workout where the bug really belongs? launchpad-foundation or lazr.restful
136 <flacoste> leave it in foundations for now
137 <Ursinha> let me just introduce the broken scripts we have, one seems to be yours sinzui
138 <Ursinha> sinzui, productreleasefinder is having issues for quite some time, it's bug 394391
139 <Ursinha> could you take a look at this one? maybe change the importance
140 <ubottu> Launchpad bug 394391 in launchpad-registry "product-release-finder should make sane milestone names" [Low,Triaged] https://launchpad.net/bugs/394391
141 <Ursinha> also, I see that language-pack-exporter also failed to run, herb, henninge, do you know if that was expected?
142 <henninge> I don't.
143 <sinzui> Ursinha: I know how to fix that, and 3 other bugs. I am working on that on my own time
144 <herb> I don't know either.
145 <henninge> Ursinha: but it is a pretty long running script.
146 <henninge> Ursinha: which run was it? when?
147 <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
148 <henninge> It is not uncommon for the script to be interrupted.
149 <Ursinha> henninge, quoting the email: between 2009-07-07 17:00:04 and 2009-07-08 13:00:04
150 <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
151 <Ursinha> sinzui, I see
152 * henninge just realizes he doesn't know the current schedule for that script.
153 <Ursinha> sinzui, well, I think the important is that it's being fixed, not abandoned
154 <Ursinha> that's what I'm trying to achieve mentioning them
155 <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
156 <henninge> Ursinha: But really that script is monitored by the Ubuntu guys and they complain if they miss a language pack ...
157 <Ursinha> gee
158 <henninge> ArneGoetje to be exact.
159 <Ursinha> henninge, monitored or maintained?
160 <herb> l-p-e runs every monday,tuesday,thursday friday
161 <herb> @2200 BST
162 <herb> mon,fri for jaunty
163 <herb> tue for intrepid
164 <henninge> herb: ah, was gonna ask that
165 <herb> thur for hardy
166 <Ursinha> herb, thanks for the info
167 * Ursinha took notes
168 <henninge> Ursinha: so that is that was the intrepid run failing. Not critical.
169 <herb> the monday run finished at 0310 UTC on Tuesday
170 <Ursinha> sinzui, thanks for that
171 <Ursinha> henninge, right. if that keeps happening may I poke you? :)
172 <herb> and it does look like intrepid was the one the failed
173 <henninge> Ursinha: you may :)
174 <herb> but it ran successfully the previous week.
175 * henninge looks forward to being poked by Ursinha because it will definietly happen ...
176 <Ursinha> [action] Ursinha to watch the lang-pack-exporter script and poke henninge if it fails again
177 <MootBot> ACTION received: Ursinha to watch the lang-pack-exporter script and poke henninge if it fails again
178 <Ursinha> well, let's move on
179 <Ursinha> thank you all guys
180 <Ursinha> [TOPIC] * Operations report (mthaddon/herb/spm)
181 <MootBot> New Topic: * Operations report (mthaddon/herb/spm)
182 <herb> 2009-07-02 - Cherry picked r8700 to the scripts server.
183 <herb> 2009-07-07 - Cherry picked r8766 to the scripts server.
184 <herb> 2009-07-07 - Cherry picked r8729 to the importd slaves.
185 <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.
186 <Ursinha> herb, that's good to hear
187 <Ursinha> does anyone have anything for herb?
188 <Ursinha> hmm
189 <Ursinha> moving on then :)
190 <Ursinha> [TOPIC] * DBA report (stub)
191 <MootBot> New Topic: * DBA report (stub)
192 <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.
193 <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.
194 <stub> Not much in the way of db patches this cycle. Should have reviews all sorted and things ready to land tomorrow.
195 <stub> oot.
196 <Ursinha> stub, do you know if all accounts that were reporting problems on feedback@ were fixed?
197 <stub> All that have been forwarded to me have been fixed.
198 <stub> I don't personally monitor feedback@
199 <Ursinha> okay, I'll check if there's any outstanding one
200 <Ursinha> thanks stub
201 <Ursinha> [action] Ursinha to check if all accounts requesting fix on feedback@ were fixed
202 <MootBot> ACTION received: Ursinha to check if all accounts requesting fix on feedback@ were fixed
203 <Ursinha> anything else for stub?
204 <Ursinha> or
205 <Ursinha> anything else at all?
206 <Ursinha> 5
207 <Ursinha> 4
208 <Ursinha> 3
209 <Ursinha> 2
210 <Ursinha> 1
211 <Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs.
212 <Ursinha> #endmeeting