1 2011-06-19T00:00:26 <ThomasWaldmann> http://hg.moinmo.in/moin/2.0/file/37c117ad8f7e/MoinMoin/themes/__init__.py#l361
2 2011-06-19T00:01:57 <ThomasWaldmann> ok, i have to go to bed now. tomorrow travelling to europython (not online at all), Monday..Sunday sporadically online, Monday offline again for travelling back.
3 2011-06-19T00:02:40 <sinha> yeah got it
4 2011-06-19T00:22:53 *** m4k3r
5 2011-06-19T00:25:52 *** pkumar
6 2011-06-19T00:26:43 <dreimark> sinha: i would prefer to store it in the user object. the bookmark time is also stored there
7 2011-06-19T00:27:05 <dreimark> i have time tom. morning to review and mail
8 2011-06-19T00:27:42 <sinha> dreimark: okay, so we wont show the input box for non logged in user to enter count, just assume default for them
9 2011-06-19T00:28:51 <dreimark> yes
10 2011-06-19T00:29:30 <dreimark> because we want them to login - they need something it is useful to do it
11 2011-06-19T00:40:29 <dreimark> gn
12 2011-06-19T00:46:18 <sinha> gn
13 2011-06-19T00:46:20 *** sinha
14 2011-06-19T01:27:41 *** grzywacz
15 2011-06-19T07:14:22 *** m4k3r
16 2011-06-19T08:01:36 *** m4k3r
17 2011-06-19T08:02:01 *** m4k3r
18 2011-06-19T09:10:27 *** Marchael
19 2011-06-19T09:10:40 <Marchael> moin
20 2011-06-19T09:39:52 <Marchael> ThomasWaldmann: ping
21 2011-06-19T10:20:40 <CIA-70> Michael Mayorov <marchael@kb.csu.ru> * 98cbec45cffb r268 moin-2.0/MoinMoin/ (3 files in 3 dirs): Fiexes in flask-script for rebuilding indexes. Python2.6 compatibility. Make changes in schema for better integration with Moin.
22 2011-06-19T10:36:05 *** greg_f
23 2011-06-19T11:19:57 *** greg_f
24 2011-06-19T11:26:41 *** greg_f
25 2011-06-19T11:58:55 *** greg_f
26 2011-06-19T12:02:55 <dreimark> moin
27 2011-06-19T12:03:15 <dreimark> Marchael: thomas is travelling since 5h
28 2011-06-19T12:03:43 <dreimark> next time please check syntax errors in commit strings
29 2011-06-19T12:06:02 *** greg_f
30 2011-06-19T12:30:42 *** greg_f
31 2011-06-19T12:37:21 *** greg_f
32 2011-06-19T12:45:32 <Marchael> sorry for my english
33 2011-06-19T13:13:08 *** grzywacz
34 2011-06-19T13:13:08 *** grzywacz
35 2011-06-19T13:18:24 <Marchael> dreimark: mtime field in backend stores only year-month-date?
36 2011-06-19T13:33:39 *** grzywacz
37 2011-06-19T13:36:32 *** grzywacz
38 2011-06-19T15:11:20 * dreimark greets from Frankfurt
39 2011-06-19T15:12:01 <dreimark> Marchael: I don't think so it should have ms granualarity
40 2011-06-19T15:16:21 <dreimark> bbl
41 2011-06-19T15:17:16 *** hardy89
42 2011-06-19T15:43:18 *** m4k3r
43 2011-06-19T15:48:50 *** m4k3r
44 2011-06-19T16:07:33 *** Marchael
45 2011-06-19T16:09:02 *** m4k3r
46 2011-06-19T16:11:20 *** m4k3r
47 2011-06-19T16:30:38 <hardy89> hi waldi
48 2011-06-19T16:31:40 <hardy89> waldi: whenever i use gc module in conftest.py, the test session does not complete
49 2011-06-19T16:31:48 <hardy89> rather, this is what i get -->http://www.pastie.org/2091686
50 2011-06-19T16:44:49 *** pkumar
51 2011-06-19T16:58:15 *** Marchael
52 2011-06-19T17:12:48 <pkumar> hardy89 : hey
53 2011-06-19T17:13:01 <hardy89> hi pkumar
54 2011-06-19T17:13:01 <pkumar> hardy89 : how's it goinn?
55 2011-06-19T17:13:17 <hardy89> pkumar: going fine now. things seem to be working a bit now.
56 2011-06-19T17:13:25 <hardy89> memory issue wasn't that simple afterall
57 2011-06-19T17:14:05 <pkumar> yeah, I know it. But the problem is we have a schedule to follow.
58 2011-06-19T17:14:12 <hardy89> few changes have brought down the memory u
59 sage by 200 mb
60 2011-06-19T17:14:41 <pkumar> link?
61 2011-06-19T17:14:54 <hardy89> pkumar: of?
62 2011-06-19T17:15:00 <hardy89> pkumar: and schedule yes
63 2011-06-19T17:15:07 <hardy89> pkumar: i have that in mind
64 2011-06-19T17:15:13 <pkumar> your changes you made
65 2011-06-19T17:15:35 <hardy89> pkumar: will do it in a while
66 2011-06-19T17:15:39 <hardy89> in my repo
67 2011-06-19T17:15:51 <pkumar> ok, so what about the schedule?
68 2011-06-19T17:16:10 *** Marchael
69 2011-06-19T17:16:26 <hardy89> pkumar: we have it on EP. lets discuss the grey area here
70 2011-06-19T17:16:31 <hardy89> whats next?
71 2011-06-19T17:16:34 <pkumar> any suggestions?
72 2011-06-19T17:17:04 * hardy89 goes to have a look at EP
73 2011-06-19T17:17:22 <pkumar> 18th - 25th June has its own task and today is 19th
74 2011-06-19T17:17:49 <hardy89> pkumar: i do remember that
75 2011-06-19T17:18:03 <hardy89> pkumar: you talk like a mentor ;)
76 2011-06-19T17:18:31 <hardy89> pkumar: you suggested to discard few things in this time bracket last time.
77 2011-06-19T17:18:37 <hardy89> pkumar: pls to repeat
78 2011-06-19T17:18:40 <pkumar> haha.. ;)
79 2011-06-19T17:18:44 <pkumar> no, I'm not saying you don't remember. I was asking suggestions about how to handle it
80 2011-06-19T17:18:54 <hardy89> pkumar: i understand m8 :)
81 2011-06-19T17:20:19 <pkumar> so, have you got any? suggestions..
82 2011-06-19T17:20:23 <hardy89> member:pkumar: you suggested to discard few things in this time bracket last time.
83 2011-06-19T17:20:31 <hardy89> pls2repeat
84 2011-06-19T17:20:52 <pkumar> what things?
85 2011-06-19T17:21:39 <hardy89> pkumar: few issues which are there in 18-25 june time bracket
86 2011-06-19T17:22:29 <pkumar> I can see 5 tasks. which did I suggest to discard?
87 2011-06-19T17:22:47 <hardy89> pkumar: that is exactly what i don't remember
88 2011-06-19T17:22:48 <hardy89> :)
89 2011-06-19T17:22:55 <hardy89> nevamind
90 2011-06-19T17:23:00 <hardy89> discuss..
91 2011-06-19T17:23:14 <hardy89> line 201 and 206 are like...similar
92 2011-06-19T17:23:22 <hardy89> and on-going
93 2011-06-19T17:23:49 <hardy89> line 209 IS a important issue
94 2011-06-19T17:24:02 <hardy89> cos we have almost 59 failures in one test session
95 2011-06-19T17:24:12 <pkumar> hehe me too. I don't remember which ones I suggested to discard :)
96 2011-06-19T17:24:15 <hardy89> and many E, X etc
97 2011-06-19T17:26:20 <pkumar> what about line 293?
98 2011-06-19T17:26:47 <hardy89> 293 :/
99 2011-06-19T17:27:04 <hardy89> last line here is 230
100 2011-06-19T17:27:04 <pkumar> 203*
101 2011-06-19T17:27:45 <pkumar> hardy89 : 203
102 2011-06-19T17:28:02 <hardy89> hmm...rewriting
103 2011-06-19T17:28:15 <hardy89> lets consult our mentor on this
104 2011-06-19T17:29:03 <xorAxAx> on what? :-P
105 2011-06-19T17:29:23 <pkumar> xorAxAx : hi :)
106 2011-06-19T17:29:28 <hardy89> hi xorAxAx
107 2011-06-19T17:29:31 <xorAxAx> hi my student
108 2011-06-19T17:29:33 <xorAxAx> hi the other student
109 2011-06-19T17:29:35 <xorAxAx> ;-)
110 2011-06-19T17:29:40 <hardy89> xorAxAx: ah :(
111 2011-06-19T17:30:04 <hardy89> ok...we are confused regarding line 203
112 2011-06-19T17:30:07 <hardy89> on EP
113 2011-06-19T17:31:45 * xorAxAx has visitors, brb
114 2011-06-19T17:32:44 <hardy89> pkumar: what bout tutorial thing
115 2011-06-19T17:33:02 <pkumar> hardy89 : yeah, need to take care of that too.
116 2011-06-19T17:33:22 <hardy89> pkumar: isn't this too early to launch a tutorial
117 2011-06-19T17:35:23 <pkumar> actually, tutorial is like it should have gone with the task.
118 2011-06-19T17:36:24 <pkumar> that's not of much concern right now. can be taken care an week
119 2011-06-19T17:36:37 <hardy89> pkumar: what is there to be feeded in tut right now
120 2011-06-19T17:36:38 <hardy89> ?
121 2011-06-19T17:37:20 <pkumar> well, for you the things you have done till now
122 2011-06-19T17:37:44 <hardy89> pkumar: tutorial is for others. why do they want to know what we did :)
123 2011-06-19T17:38:52 <pkumar> you need to take care that it looks like a tutorial. Work just gives you content what to write
124 2011-06-19T17:39:30 <hardy89> hmm
125 2011-06-19T17:39:50 <hardy89> like, tut has to be for Devs or just users?
126 2011-06-19T17:40:07 <pkumar> somewhere in the middle
127 2011-06-19T17:40:10 <pkumar> ;)
128 2011-06-19T17:40:39 <hardy89> thats again something grey :P
129 2011-06-19T17:41:18 <pkumar> I meant, like a new developer, may not be that experienced.
130 2011-06-19T17:41:18 <hardy89> pkumar: btw, we are giving too less time too many things and tighting our schedule, except porting
131 2011-06-19T17:41:42 <hardy89> what this might do, is pile up work etc
132 2011-06-19T17:41:44 <pkumar> like?
133 2011-06-19T17:41:48 <hardy89> pkumar: hmm...i see
134 2011-06-19T17:42:24 <hardy89> pkumar: like memory leak and fs2 were
135 2011-06-19T17:42:52 <hardy89> which although somehow turned out to be not so troublesome
136 2011-06-19T17:43:42 <hardy89> pkumar: cos we're already sanitising and improving the condition, and i do not want to see the same project in 2012 SoC cos it was left undone etc in 2011 :)
137 2011-06-19T17:43:58 <hardy89> ah..sorry...We :)
138 2011-06-19T17:44:05 <pkumar> fixing issues is sure the tough part of the project, though we had 2 weeks for fixing issues.
139 2011-06-19T17:44:20 <pkumar> we won't
140 2011-06-19T17:44:23 <pkumar> :)
141 2011-06-19T17:44:38 <hardy89> had? :/
142 2011-06-19T17:45:32 <hardy89> pkumar: ^
143 2011-06-19T17:45:42 <hardy89> had 2 weeks?
144 2011-06-19T17:46:18 <pkumar> yeah.
145 2011-06-19T17:46:46 <hardy89> pkumar: oh the bug week
146 2011-06-19T17:46:48 <hardy89> hmm
147 2011-06-19T17:46:55 <pkumar> I think we move with the schedule.
148 2011-06-19T17:47:02 <hardy89> yes
149 2011-06-19T17:47:30 <hardy89> i wonder why Bug Week reloaded ended up to be more troublesome than the actual Bug Week ;)
150 2011-06-19T17:47:37 <pkumar> may be you can continue your memory leakage along with the scheduled task if feasible.
151 2011-06-19T17:48:33 <hardy89> i have to... that is a major issue and needs to be corrected.
152 2011-06-19T17:48:45 <hardy89> although it has finally showed some signs of life
153 2011-06-19T17:48:46 <hardy89> :)
154 2011-06-19T17:48:49 <hardy89> pkumar: yeah
155 2011-06-19T17:48:54 <hardy89> lets schedule now
156 2011-06-19T17:49:10 <pkumar> its already scheduled.
157 2011-06-19T17:49:17 <pkumar> we have to work on it
158 2011-06-19T17:49:19 <hardy89> pkumar: lets discuss then
159 2011-06-19T17:49:51 <hardy89> pkumar: we can postpone the tut part to sometime later, and lets specifically start working on some other issue
160 2011-06-19T17:51:01 <hardy89> thats my opinion, which can be altered ofc by you :)
161 2011-06-19T17:51:28 <pkumar> basically, its more important to do pytest2 related changes.
162 2011-06-19T17:51:35 <hardy89> exactly
163 2011-06-19T17:52:05 <pkumar> so tasks are here:
164 2011-06-19T17:52:26 <pkumar> 1. fix all the pytest2 related errors, skips and failures
165 2011-06-19T17:53:27 <pkumar> 2. mostly MoinMoin tests have assert statements so not much to change in those
166 2011-06-19T17:53:57 <pkumar> which is the same in pytest2 I guess
167 2011-06-19T17:54:06 <pkumar> what else?
168 2011-06-19T17:54:33 <hardy89> yes
169 2011-06-19T17:55:09 <hardy89> the comes the complexity , behavior part
170 2011-06-19T17:55:12 <hardy89> pkumar: ^
171 2011-06-19T17:55:30 <pkumar> behavior of what?
172 2011-06-19T17:55:51 <hardy89> of tests
173 2011-06-19T17:56:04 <hardy89> line 201 and 206
174 2011-06-19T17:59:01 <pkumar> well, as I said it is mostly assert statements, and it is similar in both the pytest modules and their behavior too.
175 2011-06-19T17:59:12 <hardy89> hmm
176 2011-06-19T17:59:24 <hardy89> so nothing else then as of now
177 2011-06-19T17:59:36 <hardy89> if we fix the tests...its job done
178 2011-06-19T17:59:43 <hardy89> foe the next two weeks
179 2011-06-19T17:59:53 <hardy89> before we start working on coverage
180 2011-06-19T18:01:19 <pkumar> I 'm not sure of that. It may take more than fixing tests to improve the tests
181 2011-06-19T18:01:39 <pkumar> as the title of the week suggest :)
182 2011-06-19T18:02:13 <hardy89> pkumar: the major part of that is healthy running tests
183 2011-06-19T18:02:49 <pkumar> for that the way may be to go trough all the rests and see if they have better options.
184 2011-06-19T18:03:17 <hardy89> after we fix them?
185 2011-06-19T18:04:02 <pkumar> sequence may depend on the tests
186 2011-06-19T18:04:07 <hardy89> all right
187 2011-06-19T18:04:37 <hardy89> so we have the sequence with us
188 2011-06-19T18:04:39 <hardy89> cool
189 2011-06-19T18:05:21 <pkumar> seems so.
190 2011-06-19T18:05:48 <hardy89> then we start working on them and try to meetup here everyday :)
191 2011-06-19T18:06:10 <pkumar> not try. we will ;)
192 2011-06-19T18:07:06 <hardy89> thats what we said in our meetup
193 2011-06-19T18:07:11 <hardy89> oh that reminds
194 2011-06-19T18:07:22 <hardy89> have we decided the timings of meetup?
195 2011-06-19T18:09:13 <pkumar> what was the doodle link again?
196 2011-06-19T18:09:28 <hardy89> pkumar: that was the actual link
197 2011-06-19T18:09:33 <hardy89> my link lacked few things
198 2011-06-19T18:09:47 <hardy89> ThomasWaldmann corrected it and reposted
199 2011-06-19T18:09:58 <pkumar> not your's te other one
200 2011-06-19T18:10:04 <pkumar> the*
201 2011-06-19T18:10:20 <hardy89> ThomasWaldmann: have we zeroed down on to the weekly meetup day and time?
202 2011-06-19T18:10:49 <hardy89> pkumar: http://www.doodle.com/srhzaz7h56fmb5nh
203 2011-06-19T18:10:55 <hardy89> this is the one
204 2011-06-19T18:10:57 <pkumar> thanks
205 2011-06-19T18:11:11 <hardy89> and you've filled it up alreday, so no issues :)
206 2011-06-19T18:11:42 <hardy89> pkumar: k..food. bbl
207 2011-06-19T18:11:50 <hardy89> pkumar: cya
208 2011-06-19T18:13:24 <pkumar> cya
209 2011-06-19T18:42:36 *** hardy89
210 2011-06-19T18:50:23 *** greg_f
211 2011-06-19T19:38:22 <xorAxAx> re
212 2011-06-19T19:52:22 <pkumar> xorAxAx : as you had suggested for cleanup the tests, I tried that but nothing worked out. Also, we are getting getting a little off the schedule. I had an opinion to go with the schedule and put this clean up stuff in some TODO list
213 2011-06-19T19:52:31 <pkumar> in EP
214 2011-06-19T19:52:50 <xorAxAx> pkumar: what did you try and didnt work out?
215 2011-06-19T19:53:42 <pkumar> I tried to add some funcargs which may work at the end of the tests.
216 2011-06-19T19:54:20 <pkumar> also, traced the code execution to get a lead.
217 2011-06-19T19:55:45 <pkumar> but seems like it need a little more time and this week is already scheduled for other tasks.
218 2011-06-19T19:56:23 <pkumar> so temporarily, calling init_test_app may work for those 4/5 files I guess. What do you suggest?
219 2011-06-19T19:57:56 <pkumar> xorAxAx : ^
220 2011-06-19T19:58:33 <xorAxAx> pkumar: the problem is test A and test B is affected by it. when do you want to call init_test_app?
221 2011-06-19T19:58:39 <xorAxAx> after A or before B?
222 2011-06-19T20:01:19 <pkumar> I don't think test B is effected by the problem of test A. though calling before B should be fine I think.
223 2011-06-19T20:01:41 <pkumar> in the above case
224 2011-06-19T20:02:16 <pkumar> xorAxAx : ^
225 2011-06-19T20:02:50 <pkumar> it's fine right?
226 2011-06-19T20:02:58 <xorAxAx> if it is not effected by A, by what is it disturbed then`?
227 2011-06-19T20:04:23 <pkumar> actually test B needs a refreshed backend which is done by calling new app i.e init_test_app
228 2011-06-19T20:05:02 <xorAxAx> i know
229 2011-06-19T20:06:04 <pkumar> xorAxAx : so, just calling init_test_app before B should be fine right?
230 2011-06-19T20:08:41 <pkumar> because it's B which has the problem. there may be case we add a new test in between which don't need refreshed backend
231 2011-06-19T20:08:55 <pkumar> xorAxAx : ^
232 2011-06-19T20:09:30 <xorAxAx> pkumar: the problem is A, but yet you want to call it before B, ok
233 2011-06-19T20:10:03 <xorAxAx> thats no final solution but a workaround
234 2011-06-19T20:10:24 <xorAxAx> you should put the real cleanup onto your todolist for a later week
235 2011-06-19T20:10:45 <pkumar> yes. I need to work on it. I'll update the EP just now
236 2011-06-19T20:10:49 <pkumar> xorAxAx : ^
237 2011-06-19T20:11:16 <xorAxAx> ok
238 2011-06-19T20:11:19 <pkumar> and will schedule this task in some week.
239 2011-06-19T20:11:37 <pkumar> *recent week
240 2011-06-19T20:11:45 <pkumar> xorAxAx : ^
241 2011-06-19T20:11:58 <xorAxAx> ok
242 2011-06-19T20:12:21 *** grzywacz
243 2011-06-19T20:15:30 <pkumar> xorAxAx : done. line 202
244 2011-06-19T20:15:33 <pkumar> on EP
245 2011-06-19T20:16:10 <xorAxAx> ok
246 2011-06-19T22:41:01 <pkumar> bbl
247 2011-06-19T22:41:16 *** pkumar
248
