Tuesday, 2015-05-12

*** bknudson has joined #openstack-oslo00:00
*** dims has joined #openstack-oslo00:00
lifelessharlowja: rich comparison operators00:00
harlowjaah, hmmm00:01
harlowjapossibly00:01
*** rrepaka has quit IRC00:01
harlowjadid that change in 2.700:01
*** sdake has quit IRC00:01
lifelessharlowja: well, you're not really running 2.600:02
lifelessyou're running 2.6++++00:02
harlowjarhel special 2.600:02
harlowjalol00:02
harlowja:)00:02
harlowjaultra-special00:02
harlowja:-/00:02
harlowjaaka http://paste.openstack.org/show/220286/00:03
harlowjaor newer00:03
harlowjahasn't exploded that source rpm in a while, lol00:04
*** achanda has quit IRC00:04
* harlowja doesn't want to look at libvirt++00:12
harlowjathat one scares me00:12
lifelessdo you have software collections in your RHEL?00:12
harlowjaya,00:13
harlowja2.7 is there, some virtualenv work has happened to make that possible00:13
lifelessmaybe you could use that to get 2.700:13
harlowjayup00:13
lifelesscause00:13
lifeless2.6 ain't supported by openstack no more :)00:13
harlowjayup00:13
harlowjaits happening, slowly but surely, lol00:14
* harlowja hasn't been to involved in all that00:14
harlowjacan't be everywhere, ha00:14
*** arnaud____ has joined #openstack-oslo00:16
*** sputnik13 has quit IRC00:19
*** arnaud____ has quit IRC00:20
lifelessok so00:23
lifelessI'm going to context switch this out00:23
lifelessdo you think rrpaka will be back online today ?00:24
harlowjalifeless possibly00:26
harlowjadef in PST office ours though00:26
harlowjausually always around00:26
*** tsekiyama has quit IRC00:27
lifelessk00:28
lifelessjust this sounded panic/urgent00:28
lifelessI have another 4 hours work in me today, more or less00:28
harlowjai have way to fix it, just not ideal, force 'pbr==0.10' in setup.py files00:28
lifelessthen tomorrow is a total mess00:28
harlowjaand it only seems like oslo.config is doing this00:28
harlowjaso get some sleep00:29
harlowjait will be ok :)00:29
harlowjawe'll get this figured out00:29
lifelessif that works; one thing to be aware of is https://github.com/pypa/pip/issues/266600:29
lifelessharlowja: its midday :) - I'm waaaay ahead of you timewise ;)00:30
harlowjalol00:30
lifelesstomorrow my meetings start at 8am00:30
harlowjadamn austrialia00:30
lifelessand go for hours00:30
lifelessharlowja: NZ :) LOL00:30
harlowjaya, that00:30
lifelessharlowja: and I have a doctors appt too00:30
harlowjawhere gandalf is00:30
* lifeless shakes head00:30
harlowjaha00:30
harlowjalifeless these version numbers get sucked into our rpm building via anvil (until the 2.7 stuff happens)00:31
harlowjaso ravi ran to me when something weird going on00:31
lifelessyah00:31
lifelessso if you have pbr 0.11 installed00:31
harlowjaand figured out how to force earlier version of pbr, but then wanted him to make sure he contacted ye pbr master00:31
lifelessand ==0.10 in setup.py00:31
lifelesssetuptools will barf00:31
harlowjakk00:31
lifelessbecause 266600:31
harlowjai think its pulling it down automatically, didn't see pbr in the install00:31
harlowja*when did pip freeze00:31
lifelessk00:32
harlowjabut if that happens00:32
harlowjai'll know :)00:32
lifelessso yeah using pbr 0.10 isn't the end of the world00:32
harlowjaor get asked, ha00:32
harlowjaya, just to figure out --version00:32
harlowjathen most of the rest happens in rpm land00:33
harlowjaanyways, thx lifeless  :)00:36
openstackgerritJames Polley proposed openstack-dev/pbr: WIP: Teach pbr to read extras from setup.cfg  https://review.openstack.org/18179500:36
*** rrepaka has joined #openstack-oslo00:42
*** ozamiatin has joined #openstack-oslo00:42
*** tchaypo has joined #openstack-oslo00:42
tchaypolifeless: oh hai00:42
lifelesshai00:43
lifelessso00:43
lifelesstchaypo: some thoughts put there00:47
lifelesstchaypo: I realise that this is sketching territory00:47
lifelesstchaypo: one thing I think you should aim for in tests when doing sketch/exploratory work is clarity over DRY and pithiness00:49
tchaypoI agree :) It all seemed very clear to me at the time00:50
tchaypore: six.moves - I could, but it’d be the first use of it here that I can see00:52
tchaypoexisting code uses the try: else: pattern. I’d prefer to stick with that for now and do the move to six.moves seperately00:53
*** ChanServ changes topic to "#openstack-oslo"00:56
-openstackstatus- NOTICE: Gerrit has been downgraded to version 2.8 due to the issues observed today. Please report further problems in #openstack-infra.00:56
*** rrepaka has quit IRC00:57
tchaypoI’m not sure what you mean by “this setup is axiomatic”…. although I have realised I’m not actually testing the bit of code I wanted to test. good job james.00:58
*** takedakn has joined #openstack-oslo00:58
lifelesstchaypo: re clariyr01:02
lifelessits very narrow in your tests01:02
lifelessthats great for testing corner cases01:02
lifelessits not great for telling a story01:02
lifelessaxiomatic - tautological might be better01:02
lifelesssix.moves - this is new code, it has nothing to do with the existing code01:02
lifelessthe pbr code can't use six. pbr.tests can.01:02
*** achanda has joined #openstack-oslo01:03
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213201:05
*** prad has quit IRC01:05
*** achanda has quit IRC01:08
*** mtanino has quit IRC01:10
*** achanda has joined #openstack-oslo01:11
openstackgerritJames Polley proposed openstack-dev/pbr: WIP: Teach pbr to read extras from setup.cfg  https://review.openstack.org/18179501:14
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213201:20
*** takedakn1 has joined #openstack-oslo01:20
*** takedakn has quit IRC01:21
tchaypolifeless: I’ve updated the tests so that they’re now calling the code I wanted to test01:24
tchaypoI think that might address your concern - the function that’s being tested is now called a the top of each test01:25
*** redrobot has quit IRC01:25
*** stevemar has joined #openstack-oslo01:25
tchaypoimo that makes it a clear delinieation between the uninteresting setup and the one call that we actually want to exercise01:25
*** redrobot has joined #openstack-oslo01:26
*** redrobot is now known as Guest2030601:26
*** dstanek has quit IRC01:26
*** dstanek has joined #openstack-oslo01:26
lifelesstchaypo: I haven't looked yet, need to run a chore01:27
lifelesstchaypo: but please put the inputs to the test within the test01:27
lifelesstchaypo: so its clear whats being acted on01:28
tchaypokk, talk later. I think the tests are looking for the right data; they might be reformatted for clarity but I don’t think what they’re testing is going to change01:37
tchayposo I’ll go ahead and start on the code to actually put the data in place01:38
openstackgerritJames Polley proposed openstack-dev/pbr: WIP: Teach pbr to read extras from setup.cfg  https://review.openstack.org/18179501:38
*** browne has quit IRC01:39
*** zzzeek has quit IRC01:40
*** ashleighfarnham has joined #openstack-oslo01:44
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213201:44
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213201:47
*** takedakn1 has quit IRC01:47
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213201:49
*** sigmavirus24 is now known as sigmavirus24_awa01:54
*** _amrith_ is now known as amrith01:58
*** arnaud____ has joined #openstack-oslo02:04
tchaypoand I think I’m wrong. The format we came up with yesterday is lovely and clear and completely different to everything else in setup.cfg02:07
*** achanda has quit IRC02:07
tchaypothe code for parsing it is going to be completely disjoint from everything else02:08
lifelesstchaypo: I couldn't tell if they are looking for the right data because I can't tell what the inputs are, not easily02:08
*** bknudson has quit IRC02:08
*** arnaud____ has quit IRC02:09
*** achanda has joined #openstack-oslo02:09
tchaypoI think you couldn’t tell what the inputs are because I’d left out the call to the function I wanted to test02:09
tchaypoI think just adding the line where I call setup_cfg_to_setup_kwargs(self.config) would fix that02:10
*** vilobhmm1 has quit IRC02:10
lifelessok, let me go look02:10
*** browne has joined #openstack-oslo02:13
lifelesstchaypo: ok, not convinced. I've put a few questions on the first test :)02:14
tchaypojust a few :)02:16
*** amrith is now known as _amrith_02:17
openstackgerritMerged openstack/oslotest: Updated from global requirements  https://review.openstack.org/18122802:19
tchaypoTo step back though - I think we need to change the format02:19
tchaypothe parsing code we already have is very geared towards one arg in setup.cfg <-> one kwarg to setup.py02:20
tchaypothis thing we’ve proposed of having all the values in a section get mapped to values inside a dict inside one kwarg to setup.py is very different. It’s doable, but not inside the existing " for arg in D1_D2_SETUP_ARGS” loop in setup_cfg_to_setup_kwargs loop.02:21
lifelesstchaypo: that seems like a very weak reason to change the format02:21
*** sigmavirus24_awa is now known as sigmavirus2402:21
lifelesstchaypo: sure it is02:21
lifelesstchaypo: by which I mean, it needs tweaks, not a wholesale rewrite02:22
tchaypothe existing loop looks for a (section, option) tuple which it can map to an arg. we have the arg (extras_require) and a section (extras) but there’s no single option we’re looking for - we want to iterate over all the options in that section02:24
lifelessI think you'll find you can write some code on line 369 that will work just dandy02:25
lifelessI'm not trying to be obtuse btw02:26
lifelessfeel free to say 'wtf sketch it out'02:26
tchaypono, I agree with you, we’ve both said the same thing02:27
tchaypoassuming you’re looking at http://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/util.py#n36902:27
tchaypowe can certainly put something on line 369, but at that point it’s outside the main "for arg in D1_D2_SETUP_ARGS:” that handles every other argument02:28
tchaypounless I’ve misread where that loop ends *checks*02:28
lifelessits outside the loop02:28
lifelessbut you said we'd have to change the format because the function wouldn't fit it02:28
tchaypowell. Yes, I did.02:29
tchaypoWhat I meant was “inside the main loop"02:30
tchaypoThis function is huge and could really use some refactoring, but I’m not going to tackle that right now.02:30
*** yamahata has quit IRC02:31
lifelessjd__: mordred: https://review.openstack.org/#/c/181785/ +2's please.02:43
*** ashleighfarnham has quit IRC02:44
*** dims has quit IRC02:45
*** sputnik13 has joined #openstack-oslo02:46
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213203:04
openstackgerritMerged openstack/oslo.concurrency: Updated from global requirements  https://review.openstack.org/18190003:14
*** sputnik13 has quit IRC03:14
*** sputnik13 has joined #openstack-oslo03:16
*** dstanek has quit IRC03:16
*** peterstac has quit IRC03:16
openstackgerritMerged openstack/oslo.middleware: Updated from global requirements  https://review.openstack.org/18122303:16
*** dstanek has joined #openstack-oslo03:19
*** peterstac has joined #openstack-oslo03:19
*** sputnik13 has quit IRC03:20
openstackgerritJoshua Harlow proposed openstack/tooz: No longer need kazoo lock custom retry code  https://review.openstack.org/18214603:24
openstackgerritJoshua Harlow proposed openstack/tooz: No longer need kazoo lock custom retry code  https://review.openstack.org/18214603:25
*** amotoki_ has joined #openstack-oslo03:30
*** stevemar has quit IRC03:31
*** jecarey_ has joined #openstack-oslo03:36
lifelesswe gots the lightning03:36
openstackgerritJoshua Harlow proposed openstack/tooz: No longer need kazoo lock custom retry code  https://review.openstack.org/18214603:38
lifelessand the hail03:40
*** yamahata has joined #openstack-oslo03:40
sigmavirus24lifeless: stay safe03:40
sigmavirus24lifeless: in spite of size, do not use the hail to go golfing03:40
*** ozamiatin has quit IRC03:41
lifeless:)03:44
lifelesshttp://www.metservice.com/maps-radar/rain-radar/canterbury03:44
tchaypoI live in canterbury!03:45
lifelessI'm about a mouse pointer up and slightly to the west of the label christchurch03:45
tchaypoThere’s meant to be an archbishop around here somewhere but I haven’t been able to find him03:45
lifelesstchaypo: you do?03:45
*** arnaud____ has joined #openstack-oslo03:50
tchaypoI do!03:52
tchaypohttp://www.bom.gov.au/nsw/forecasts/canterbury.shtml is my local weather. no radar though03:52
lifelesshows the patch?03:52
tchaypohttp://www.weatherzone.com.au/nsw/sydney/canterbury offers a tiny little radar that looks like it can click through to something else03:52
tchaypooh, the patch is very sad right now. I smacked together some code and ran the tests over it and the tests tell me I did something very wrong. I had to take a break to help Andre with something, and now I’m getting lunch before I poke at it again. I think I’ve just used the wrong variable when creating the keys for the dict, so it shouldn’t be hard to03:54
tchaypofix.03:54
*** arnaud____ has quit IRC03:55
tchaypookay, I got distracted and fixed it so the tests pass. Now to get lunch and then tackle the “but what are we even testing” question04:04
*** jamespage has quit IRC04:05
tchaypoin summary, based on your questions, my thinking there is that rather than reading in the whole setup.cfg, I could pass in a simpler dict (constructed in the test) which has specific things I’m testing for04:05
*** sigmavirus24 is now known as sigmavirus24_awa04:05
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove listener stack and replace with exit stack  https://review.openstack.org/18214804:05
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove listener stack and replace with exit stack  https://review.openstack.org/18214804:06
*** jamespage has joined #openstack-oslo04:06
lifelessSafeConfigParser object, yes.04:09
*** dims has joined #openstack-oslo04:33
*** sdake_ has quit IRC04:37
*** dims has quit IRC04:38
*** jaypipes has quit IRC04:40
*** stevemar has joined #openstack-oslo04:54
*** ashleighfarnham has joined #openstack-oslo04:54
*** jaypipes has joined #openstack-oslo04:57
*** dulek has joined #openstack-oslo05:08
*** nkrinner has joined #openstack-oslo05:20
openstackgerritJoshua Harlow proposed openstack/taskflow: Ensure empty paths raise a value error  https://review.openstack.org/18215705:33
tchaypoI don’t think I care about the SafeConfigParser object. I’m trying to test the code I just wrote, I assume SafeConfigParser is going to work correctly.05:35
tchaypodid I mention this method being a tad large? It’s really not possible for me to test just the code I wrote05:35
*** arnaud____ has joined #openstack-oslo05:36
*** arnaud____ has quit IRC05:41
openstackgerritJoshua Harlow proposed openstack/taskflow: Use newer versions of futures that adds exception tracebacks  https://review.openstack.org/17997205:42
*** arnaud____ has joined #openstack-oslo05:57
*** tapesh_ has joined #openstack-oslo05:57
tapesh_hi everyone :)05:57
tapesh_i am a newbie :) plz help me make my first contribution05:58
*** tapesh_ has left #openstack-oslo06:01
openstackgerritJoshua Harlow proposed openstack/taskflow: Executors come in via options config, not keyword arguments  https://review.openstack.org/18215906:01
*** dstanek has quit IRC06:08
*** dstanek has joined #openstack-oslo06:09
*** sdake_ has joined #openstack-oslo06:38
openstackgerritEthan Lynn proposed openstack/oslo.utils: Add mac validate function in netutils  https://review.openstack.org/18216706:39
openstackgerritMerged openstack/taskflow: Just let the future executors handle the max workers  https://review.openstack.org/16435206:40
*** ashleighfarnham has quit IRC06:40
openstackgerritMerged openstack/taskflow: Avoid duplicating exception message  https://review.openstack.org/18081506:40
openstackgerritMerged openstack/taskflow: Avoid re-normalizing paths when following links  https://review.openstack.org/18126506:45
openstackgerritMerged openstack/taskflow: Expose in memory backend split staticmethod  https://review.openstack.org/18158506:45
*** arnaud____ has quit IRC06:47
ttxdhellmann: added to agenda (as well as the oslo release process one06:54
*** stevemar has quit IRC06:57
*** haypo has joined #openstack-oslo07:02
*** browne has quit IRC07:15
*** sdake_ has quit IRC07:23
*** exploreshaifali has joined #openstack-oslo07:28
*** inc0 has joined #openstack-oslo07:29
*** jaosorior has joined #openstack-oslo07:38
*** abhishekk has joined #openstack-oslo07:49
*** shardy_z is now known as shardy07:50
*** openstackstatus has quit IRC07:52
*** openstack has joined #openstack-oslo07:54
*** openstackstatus has joined #openstack-oslo07:54
*** ChanServ sets mode: +v openstackstatus07:54
*** exploreshaifali has quit IRC07:54
*** exploreshaifali has joined #openstack-oslo08:04
*** e0ne has joined #openstack-oslo08:17
*** e0ne is now known as e0ne_08:17
*** achanda has quit IRC08:25
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: rabbit: smarter declaration of the notif. queue  https://review.openstack.org/17927008:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: rabbit: Set timeout on the underlying socket  https://review.openstack.org/17935708:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Bump kombu and amqp requirements  https://review.openstack.org/17935608:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: TEST: enable heartbeat  https://review.openstack.org/17935908:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: rabbit: smart timeout on missing exchange  https://review.openstack.org/18090508:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: rabbit: redeclare consumers when ack/requeue fail  https://review.openstack.org/18005908:27
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: rabbit: remove publisher classes  https://review.openstack.org/18012908:27
*** _amrith_ is now known as amrith08:38
*** e0ne_ is now known as e0ne08:46
*** e0ne is now known as e0ne_08:46
*** e0ne_ is now known as e0ne08:55
*** eezhova has joined #openstack-oslo09:02
openstackgerritOleksii Zamiatin proposed openstack/oslo.messaging: ZeroMQ driver Req/Rep implementation  https://review.openstack.org/18220109:08
*** exploreshaifali has quit IRC09:23
tchaypolifeless: i spent the afternoon working semi-offline, but I’ve simplified the tests down to something closer to what I actually care about, I think - although perhaps I can get them even simpler09:45
*** ihrachyshka has joined #openstack-oslo09:46
tchaypoI’m not at a state where I have one test that shows that configparser parses the data in setup.cfg correctly, and another showing that the code I added to setup_cfg_to_setup_kwargs does what I think it does09:46
lifelesstchaypo: k09:46
lifelesstchaypo: thats excellent09:46
tchaypoonce I have the output from the former the same as the input to the latter we’ll be somewhere useful :p09:46
tchaypoit was when I created the test to make sure configparser was reading in the data I expected that I realised the mismatch.09:47
*** ozamiatin has joined #openstack-oslo09:50
*** cdent has joined #openstack-oslo09:55
*** ozamiatin has quit IRC10:09
*** e0ne is now known as e0ne_10:21
*** dims has joined #openstack-oslo10:33
*** yamahata has quit IRC10:35
*** e0ne_ is now known as e0ne10:39
*** ozamiatin has joined #openstack-oslo10:56
*** links has joined #openstack-oslo11:04
*** amrith is now known as _amrith_11:12
*** _amrith_ is now known as amrith11:15
*** dguitarbite has joined #openstack-oslo11:15
openstackgerritMerged openstack/stevedore: Add pypi download + version badges  https://review.openstack.org/17127511:28
openstackgerritMerged openstack/oslo.messaging: Bump kombu and amqp requirements  https://review.openstack.org/17935611:29
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Remove usage of contentmanager for executors  https://review.openstack.org/14098511:33
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Remove usage of contentmanager for executors  https://review.openstack.org/14098511:38
*** stpierre has joined #openstack-oslo11:43
*** viktors has quit IRC11:44
*** mfedosin has joined #openstack-oslo11:54
*** exploreshaifali has joined #openstack-oslo11:57
*** kgiusti has joined #openstack-oslo11:58
*** e0ne is now known as e0ne_12:00
openstackgerritGrzegorz Grasza (xek) proposed openstack/oslo.versionedobjects: Add field name to error messages in object type checking  https://review.openstack.org/16865012:00
*** dims_ has joined #openstack-oslo12:03
*** dims has quit IRC12:06
*** zul has quit IRC12:06
*** gordc has joined #openstack-oslo12:18
*** zul has joined #openstack-oslo12:18
*** dulek_ has joined #openstack-oslo12:27
*** dulek has quit IRC12:27
*** dulek_ has quit IRC12:28
*** dulek_ has joined #openstack-oslo12:28
*** e0ne_ is now known as e0ne12:34
*** dims_ has quit IRC12:40
haypojd__, do you really want to play with timezones? :)12:42
haypojd__, (i commented https://review.openstack.org/#/c/148500/ & https://review.openstack.org/#/c/166861/)12:42
*** dims has joined #openstack-oslo12:42
jd__haypo: yeah, I replied12:47
*** viktors has joined #openstack-oslo12:48
openstackgerritVictor Sergeyev proposed openstack/oslo.messaging: WIP: use channel pool  https://review.openstack.org/18227212:49
dhellmannttx: added to the agenda?12:49
ttx<dhellmann> 22:14:25> bnemec: we should encourage ttx and sdague to attend your session on optional requirements: https://etherpad.openstack.org/p/YVR-oslo-optional-dependencies12:51
ttxI added it to my agenda12:51
dhellmannttx: ah, right12:51
dhellmannETOOMUCHSCROLLBACK12:51
ihrachyshkadhellmann, any updates on the plan to solve juno failures due to missing juno branches for some oslo libraries?12:51
haypojd__, IMO you should replace strtime(t) with t.isoformat() to reduce the risk of backward compatibility issue12:52
haypojd__, oh, strtime() simply ignores the timezone, too bad12:52
jd__haypo: that's not what I'm trying to do12:52
jd__I'm trying to fix openstack12:52
dhellmannihrachyshka: do you have a list?12:52
jd__:-D12:52
ihrachyshkadhellmann, well, pycadf and oslo.utils for the start?12:53
dhellmannihrachyshka: we're mostly waiting to sort that out at the summit12:53
haypojd__, in this case, you should start by creating datetime objects with the timezone information12:53
ihrachyshkadhellmann, ok, so we leave it broken for time being? if that's the plan, I will just ignore those failures. I'm lazy and fine with it. :)12:53
jd__haypo: what's the point since strtime() does not output the timezone?12:53
dhellmannihrachyshka: ok, I'll make sure those are in my notes12:53
haypojd__, isotime(datetime.datetime.now()) returns '2015-05-12T14:53:32Z', it's wrong: it's not 14:53 but 12:53 in UTC12:53
ihrachyshkadhellmann, btw should I now ping dims instead? :)12:54
dhellmannihrachyshka: yeah, it's just another week or two, and we all want time to focus on the problem to stop playing whack-a-mole12:54
dhellmannihrachyshka: yes :-)12:54
ihrachyshkait will take time before I become used to it!12:54
haypojd__, i agree to deprecate strtime(), but i don't like isotime() (it's wrong for unaware datetime objects)12:54
ihrachyshkaok, I then relax on those failures12:54
haypojd__, announcing a wrong datetime may be worse than omitting the timezone12:55
haypooops12:55
jd__haypo: we can fix isotime()12:55
haypojd__, announcing a wrong timezone may be worse than omitting the timezone12:55
jd__haypo: agreed let's fix isotime() then12:55
*** pasquier-s has quit IRC12:55
haypojd__, hum, we should first fix utcnow() to use datetime.datetime.now(tz=datetime.timezone.utc)12:59
*** zul has quit IRC12:59
dhellmannihrachyshka: are you talking about the periodic jobs failing? (I want to grab a link to a failure log)12:59
jd__haypo: does that work with Py2?13:00
haypojd__, nope, python2 sucks13:00
haypojd__, let's drop py2 too!13:00
jd__:(13:00
jd__haypo: you sound as unhelpful as me sometimes13:01
haypojd__, lol13:01
jd__:)13:01
ihrachyshkadhellmann, yes. like http://logs.openstack.org/periodic-stable/periodic-glance-python27-juno/9057881/13:01
haypojd__, well, it's possible to hack a UTC timezone on python 213:01
haypojd__, i did that in the paste13:01
haypopast13:01
jd__haypo: tell me how :-)13:01
*** sdake has joined #openstack-oslo13:01
*** dulek_ has quit IRC13:01
dhellmannihrachyshka: cool, thanks13:02
*** dulek_ has joined #openstack-oslo13:02
*** kgiusti has quit IRC13:02
haypojd__, https://bitbucket.org/haypo/hachoir/src/f9c997b6fcd3abcd0b265f1307d7aea572827667/hachoir-metadata/hachoir_metadata/timezone.py?at=default#cl-313:02
*** sdake_ has joined #openstack-oslo13:03
*** zul has joined #openstack-oslo13:03
jd__haypo: lol this is so going to break OpenStack13:04
jd__this all code is completely broken and everything relies on it13:04
haypojd__, why?13:04
jd__haypo: because of things like TypeError: can't compare offset-naive and offset-aware datetimes13:04
jd__but let's try :)13:04
haypojd__, yeah, it's a problem very close to bytes versus unicode13:05
jd__agreed13:05
haypobytes is "unaware" of the encoding :)13:05
jd__I'm working on that right now13:05
haypojd__, "now" in which timezone?13:05
jd__haypo: CEST13:06
haypojd__, if you don't want to break the world at once, maybe we can start by only changing the behaviour on Python 3?13:06
jd__haypo: brrr13:06
jd__haypo: I'll write the patch and we'll discuss after13:06
jd__haypo: we can also create a new library :p13:06
jd__oslo.utilsnotbroken13:06
haypojd__, i suggest that because python 3 has a better support for aware datetime objects (as python 3 has a better support of unicode in general)13:06
*** sdake has quit IRC13:06
haypodhellmann will love the idea of a new library13:07
haypojd__, unit tests are fun: "self.skynet_self_aware_time = datetime.datetime(1997, 8, 29, 6, 14, 0)", this object is *not* aware13:08
jd__haypo: that the line I'm changing13:08
jd__haypo: are you reading my screen?13:08
haypoonly JCVD is aware13:08
haypojd__, i'm probably hacking the same code13:08
jd__it's pretty messy and ugly13:11
jd__no timezone can mean UTC or local time zone13:11
*** BrianShang has quit IRC13:14
haypojd__, hum, it looks like you understood the issue13:15
jd__I'm smart, right?13:16
haypojd__, with encoding, at least it's possible to check if a string is encoded to UTF-813:16
haypojd__, with a timestamp, well, good luck :) it depends on the context13:16
*** sdake_ is now known as sdake13:18
*** jecarey_ has quit IRC13:22
dhellmannhaypo, jd__ : we could just make a new function with the new behavior, and then deprecate the old one13:27
dhellmannETOOMANYLIBS13:27
jd__dhellmann: lol I don't know13:28
jd__I'll write a patch and we'll discuss I guess13:28
haypodhellmann, something like timetime.reallyisotime() ?13:28
dhellmannjd__: doing something that lets the app developer decide when to make a potentially breaking change gives them the flexibility and control they want13:28
dhellmannhaypo: I'm bad at naming things, but we can probably do better than that :-)13:29
haypo"almostnow()"13:29
dhellmannhaha13:29
*** prad has joined #openstack-oslo13:29
*** samueldmq has joined #openstack-oslo13:30
dhellmannsamueldmq: hi!13:30
samueldmqdhellmann, hi, I'd like to talk about graduating oslo-quota :)13:30
dhellmannyes, we've had a couple of discussions about that in the past13:31
dhellmannsalv-orlando brought it up for kilo, and we had a summit session in paris13:31
dhellmannduring that discussion I think we mostly agreed that because the quota thing will have a database, and therefore database migrations, we probably want it to be a service rather than just a library13:31
dhellmannand there is just such a service, but it hasn't seen much development work lately13:32
dhellmannlet me find the etherpad from that session...13:32
dhellmannhttps://etherpad.openstack.org/p/kilo-oslo-common-quota-library13:32
*** amuller has joined #openstack-oslo13:32
salv-orlandothat was my understanding as well, also I and dhellmann verified that oslo-quota was not used by any project, how could we graduate that in this conditions?13:32
dhellmannand the current spec is https://review.openstack.org/#/c/132127/13:33
samueldmqdhellmann, cool ... I would be able to work on that front for L if you want ...13:33
salv-orlandomind me, I do not no understand anything about oslo processes, but  I expect a library to be widely adopted before graduating it13:33
samueldmqdhellmann, I am also working on the cross-project policy changes as well13:33
dhellmannsalv-orlando: oh, thanks, I'd forgotten about the fact that the existing quota code isn't used13:33
samueldmqdhellmann, looking at those links13:33
amullersileht: I have a question about oslo messaging 'cast' if you're up for it :)13:33
silehtamuller, sure13:34
samueldmqsalv-orlando, ++ I agree with you13:34
dhellmannsamueldmq: as a service, that work would be done outside of oslo, so we'll have to hook you up with the other folks interested in it13:34
salv-orlandosamueldmq: you're more than welcome to take ownership of that specification for oslo. My impression however was that the consensus was to reject it, indeed I moved on looking at a github project called boson as a basis for a quota service.13:34
dhellmannsalv-orlando: it depends, but in most cases with incubated code, yes, we want it to be used before graduation13:35
amullersileht: call blocks until the other side finishes processing and you get a return value or an exception. Does cast wait for anything at all? Does it block until you get a confirmation from the messaging server (Assuming rabbit backend?)13:35
amullerDoes it block until the intended recipient gets the message? (If direct or topic)13:35
amullerOr is it just fire and forget?13:35
samueldmqdhellmann, salv-orlando great .. I will take a look at that spec13:36
samueldmqbut at a glance it looks like it is just proposing the oslo library , and not the quota service13:36
silehtamuller, it blocks until rabbit take the msg13:37
amullersileht: ok that confirms my assumption13:37
silehtamuller, it does wait for reply or anything else13:37
sileht*doesn't*13:37
amullersileht: do you think there is value in another kind of message, that waits until the other side picks up the message? (But doesn't block until it finishes processing)13:38
amullerdoes the rabbit backend even support that functionality?13:38
amullersileht: and do you know what does oslo notify do in this context?13:38
silehtamuller, no application have got a use-case that need this13:39
dhellmannsamueldmq: yes, the spec is for the old library idea, I was just sharing history with you13:39
salv-orlandosamueldmq: yes, the spec proposes a library. You can look at the etherpad for the bits that were deemed "awkward" at the Paris summit concerning the approach.13:39
samueldmqdhellmann, great .. the first question coming is, what would be the overhead on having all the quotas in a separate service ?13:40
amullersileht: What makes you determine that? I'd love that for Neutron in several places, unless I'm way off base?13:40
silehtamuller, sending notification is like a cast except we create we enforce default queue13:40
samueldmqdhellmann, I am asking because you guys possible already have thought about htis13:40
silehtamuller, you means retrieves all replies from all workers that got the cast ?13:41
dhellmannsamueldmq: rest calls are more expensive than database lookups, I would think, but I don't know13:41
amullersileht: let's start with direct I suppose13:41
amullersileht: I'd like something like cast, but that blocks until the other side got the message, not just the messaging server13:41
amullersileht: this would be used as a (more) reliabe means of notifications13:42
amullerreliable*13:42
samueldmqdhellmann, salv-orlando k got it .. I will take a deeper look and come back later13:42
samueldmqdstanek, salv-orlando you guys will be at the summit ?13:42
silehtamuller, how will you known how many replies you should wait ?13:42
samueldmqdstanek, not you ... I meant dhellmann  :)13:42
amullersileht: in a direct queue it's just 1 right13:42
amullersileht: and in topic 1 as well13:43
amullerthis wouldn't be relevant for fanout13:43
*** links has quit IRC13:44
dhellmannsamueldmq: yes13:44
samueldmqdhellmann, great we can talk a bit more about this there, thanks13:45
*** mriedem_away is now known as mriedem13:46
*** stpierre has quit IRC13:47
*** exploreshaifali has quit IRC13:49
*** browne has joined #openstack-oslo13:50
*** xek is now known as x3k13:52
dimsdansmith: looks like we have 3 reviews in flight in o.vo - can you please +W if appropriate? https://review.openstack.org/#/q/project:openstack/oslo.versionedobjects+status:open,n,z13:53
*** e0ne is now known as e0ne_13:53
silehtamuller, I don't understand what the different with a rpc.call if you want to wait a return from the server13:54
sileht(even you don't care of the value returned)13:54
*** stpierre has joined #openstack-oslo13:54
amullersileht: I want to wait until the other *receives* the message but not until it finishes processing the message13:54
silehtamuller, got it13:54
dansmithdims: two of them were co-authored by me, or already +2 by me.. you okay with me slamming those in?13:55
*** e0ne_ is now known as e0ne13:55
dimsdansmith: yep13:55
silehtamuller, you can just do eventlet.spawn() in the application that will return directly13:56
dansmithokay done13:56
dimsthanks dansmith13:56
amullersileht: you mean eventlet.spawn with a call inside?13:56
silehtamuller, in the rpc.endpoint that receive the call13:57
*** bknudson has joined #openstack-oslo13:57
silehtamuller, nova already does this kind of thing13:57
amullerhmm13:57
* amuller is thinking13:57
*** abhishekk has quit IRC13:57
*** jecarey has joined #openstack-oslo13:59
silehtamuller, for the performance of replies itself, we have two idea to improve it https://bugs.launchpad.net/oslo.messaging/+bug/1437951 and https://bugs.launchpad.net/oslo.messaging/+bug/143795114:04
openstackLaunchpad bug 1437951 in oslo.messaging "rpc call leads to unnecerry exchange declaration" [Wishlist,In progress] - Assigned to Mehdi Abaakouk (sileht)14:04
silehtoups seconds:https://review.openstack.org/#/c/181010/14:05
silehtthe first looks tricky to not break rolling upgrade14:05
silehtfor the second one, we should have the enhancement soon14:06
*** inc0 has quit IRC14:11
amullersileht: about the receipient processing in an eventlet thread. I think it would help in a lot of cases, but, while I'm far from an eventlet expert... A receipient might have dozens+ of green threads already up and running when it receives the message. If I'm not mistaken, it might take a non-trivial amount of time to return back to the code that returns the RPC call14:13
silehtamuller, oslo.messaging limits the number of messages handled in parallel with rpc_thread_pool_size14:15
silehtamuller, if you use eventlet.spawn, that will return a oslo.msg threads in the pool14:15
*** zzzeek has joined #openstack-oslo14:15
dhellmannihrachyshka: can you lend me a hand with getting the neutron team to prioritize work on the namespace patch in the client lib? https://review.openstack.org/#/c/180700/ I just asked in #openstack-neutron, too, fwiw14:15
amullersileht: I'm thinking of a server, it would have green threads running unrelated to oslo messaging14:16
jd__haypo: did you just start an entire new thread to troll on the same mysql subject lol?14:16
haypojd__, zigo suggested me to open a new thread14:17
*** zul has quit IRC14:17
haypojd__, the previous one ends with discussing rust and go, i don't understand how it's related to python 314:17
silehtamuller, yes I don't see a problem14:17
jd__haypo + zigo = #trollteam ;)14:17
ihrachyshkadhellmann, ack. we may need a hacking check similar to what is in neutron14:17
*** stevemar has joined #openstack-oslo14:17
amullersileht: if the server has tons of green threads going, it might take a while to get back to the code that calls eventlet.spawn when it receives the RPC call14:17
jd__haypo: but I admit the last thread kinda died weirdly14:18
silehtamuller, you perhaps need to have a greenpool in your app14:18
haypojd__, the discussion doesn't produce anything concrete14:18
jd__haypo: that's the point of most discussions you know14:18
silehtamuller, to define how many times you want this processing in parallel14:18
jd__that's why I write more patches than email :)14:18
haypojd__, except that monty voted -1 on my patch because of it :-p14:18
dhellmannihrachyshka: if you like. I would prefer to just move ahead with deleting things, but that's up to the neutron team14:18
sileht"eventlet.spawn_n" returns imediality and the greenthread in scheduled later14:19
silehtamuller, ^14:19
amullersileht: ok14:19
amullersileht: I can probably work with that14:19
silehtamuller, note the '_n'14:19
amullersileht: yeah14:19
*** zul has joined #openstack-oslo14:19
ihrachyshkadhellmann, W+114:19
amullersileht: It's a useful pattern, do you think it belongs in oslo messaging, or in the different apps?14:19
amullersileht: in neutron I could just define a decorator for RPC endpoints that processes the RPC message in eventlet.spawn_n14:20
silehtamuller, for example, nova do some processing sync, then spawn a thread and reply14:21
silehtamuller, but oslo.messaging can provide the helper to do that14:21
amullersileht: you can look at this from the recipient's point of view or the sender14:23
amullerso for example oslo messaging (Or the different apps) could define a decorator that you'd put around an RPC endpoint, and it'd just call eventlet.spawn_n(f, args)14:24
amullersileht: or, if you see it from the client's point of view, it'd be a flag to call, or a new type of message14:24
silehtamuller, yeah all works14:25
*** sigmavirus24_awa is now known as sigmavirus2414:25
*** dulek_ has quit IRC14:25
silehtbut I think that the application should create a thread pool to do that, to not exhaute resources14:26
silehtamuller, if oslo.messaging do that we have to implement that for all executors14:27
amullersileht: yeah I see your point14:27
silehtfor me how the application want to handle sync and async thing is its business, oslo.messaging just dipatcher message in a sync way with the select executor14:28
silehtamuller, I still wonder from the caller POV, why is it need to have a special handling between 'the message haven't been delivred' and 'it have been delivred but the processing failed and I don't care to known how/why'14:30
amullersileht: I just see the distinction between getting an ACK from the messaging server (cast) and getting an ACK from the intended recipient14:30
amullerit's one step more reliable14:31
silehtyeah but why is usefull if the caller doesn't care if the processing succeed14:31
amullerso you're saying why not use cast in these cases14:32
silehtyes :p14:32
dhellmanndims, gordc: can we do an oslo.middleware release today or tomorrow? I need to get a version that doesn't use the oslo namespace package when importing other libs14:34
dimsdhellmann: i am good pulling trigger, gordc, can you confirm it's ok?14:35
dhellmanndims: I can run the script, if you both confirm it's ok to do so14:35
amullersileht: the one distinction is if the recipient is not up at all14:36
amullersileht: with cast the client wouldn't know14:36
amullersileht: so the client can handle that type of error14:37
silehtamuller, ok so you care of the return :)14:37
dimsdhellmann: +2W from me :)14:37
silehtamuller, clearly rpc.call + spawn_n, should fit your use-case14:37
amullersileht: I don't think it's ideal but I can work with it14:37
*** Guest20306 is now known as redrobot14:39
dhellmanndims: ok, I'll track down gordc14:39
jd__dhellmann: can we remove old tests directory quickly? Just lost 30 mins not understanding why my tests change were not passsing locally because I was modifying only one of the file /me crying14:40
dhellmannjd__: https://review.openstack.org/#/q/topic:bp/remove-namespace-packages,n,z14:40
dhellmannjd__: I have wip patches up to remove all of that14:41
jd__dhellmann: thanks!14:41
dhellmannI have about 24 libraries that need patches landed and new releases14:41
silehtamuller, we can try to add the feature to oslo.msg, but I need to dig how14:41
dhellmannthen we can make progress on the patches in our libs and the applications14:41
dhellmannjd__: you could look at the patches related to ceilometer, ceilometermiddleware, and ceilometerclient :-)14:42
silehtamuller, I'm thinking to something like 'a post dispatcher callback' or 'a post reply callback'14:42
openstackgerritMerged openstack/oslo.versionedobjects: Add enum fieldtype field  https://review.openstack.org/16864914:42
openstackgerritMerged openstack/oslo.versionedobjects: Add field name to error messages in object type checking  https://review.openstack.org/16865014:42
amullersileht: ack14:42
silehtamuller, that could be a good idea, that will still hold the oslo.msg thread from the pool, and avoid resource exhauted14:43
silehtamuller, application can do some processing before the reply and some other after14:44
amullersileht: sounds good14:44
*** mtanino has joined #openstack-oslo14:45
dhellmanndims: I thought https://review.openstack.org/#/c/182090/1 had landed, but hasn't, so I need that approved before we release14:45
silehtthat should be just some changes into the rpc dispatcher14:45
dhellmannETOOMANYPATCHES14:45
silehtdhellmann, done14:46
dhellmannsileht: thanks!14:46
*** ashleighfarnham has joined #openstack-oslo14:46
*** sdake_ has joined #openstack-oslo14:49
*** e0ne is now known as e0ne_14:51
*** achanda has joined #openstack-oslo14:52
*** sdake has quit IRC14:52
dimssileht: thanks!14:53
*** jaypipes has quit IRC14:54
openstackgerritVictor Sergeyev proposed openstack/oslo.messaging: WIP: use channel pool  https://review.openstack.org/18227214:55
*** nkrinner has quit IRC14:55
*** e0ne_ is now known as e0ne14:58
*** browne has quit IRC15:00
*** achanda has quit IRC15:01
*** alexpilotti has joined #openstack-oslo15:01
*** sputnik13 has joined #openstack-oslo15:03
*** zz_jgrimm is now known as jgrimm15:06
*** ozamiatin has quit IRC15:11
*** cdent has quit IRC15:12
*** mfedosin has quit IRC15:16
*** shakamunyi has joined #openstack-oslo15:22
*** barra204 has joined #openstack-oslo15:22
ihrachyshkadhellmann, https://review.openstack.org/#/c/176333/ neutron would like to see it15:24
dhellmannihrachyshka: are names unique? I'm not sure we want the default to be to log non-unique values15:29
ihrachyshkadhellmann, as per http://docs.openstack.org/cli-reference/content/keystoneclient_commands.html , yes15:31
*** dguitarbite has quit IRC15:31
ihrachyshkasee user-create and tenant-create15:31
dhellmannihrachyshka: ok. it's also a backwards-incompatible change for anyone currently parsing the logs we generate, so we need to think about that15:32
*** sputnik13 has quit IRC15:32
dhellmannihrachyshka: I'm not opposed to the change, per se, but we need to take care. I'll leave some comments on the review15:32
*** sputnik1_ has joined #openstack-oslo15:32
*** yamahata has joined #openstack-oslo15:34
*** yamahata has quit IRC15:36
*** yamahata has joined #openstack-oslo15:37
openstackgerritJoshua Harlow proposed openstack/tooz: Use a lua script(s) instead of transactions (WIP)  https://review.openstack.org/18080015:40
*** ccrouch has quit IRC15:42
openstackgerritIhar Hrachyshka proposed openstack/oslo.policy: Expose base check classes as part of public API  https://review.openstack.org/17668315:45
*** jaypipes has joined #openstack-oslo15:45
*** links has joined #openstack-oslo15:50
*** arnaud____ has joined #openstack-oslo15:51
*** haypo has quit IRC15:52
*** mtreinish has quit IRC15:58
*** mtreinish has joined #openstack-oslo16:00
*** kgiusti has joined #openstack-oslo16:05
*** ozamiatin has joined #openstack-oslo16:08
openstackgerritMerged openstack/oslo.middleware: Drop use of 'oslo' namespace package  https://review.openstack.org/18209016:08
*** exploreshaifali has joined #openstack-oslo16:11
*** openstackgerrit_ has quit IRC16:11
bknudsondoes anyone know off the top of their head what changed to fix the doubling-up of [cors] section in keystone.conf?16:16
*** ozamiatin has quit IRC16:28
*** sputnik13 has joined #openstack-oslo16:33
*** browne has joined #openstack-oslo16:33
*** yamahata has quit IRC16:35
dhellmanndims, bnemec, jd__ : do any of you know about "hidden" configuration options? I'm not seeing anything in oslo.config about hiding option definitions16:36
*** sputnik1_ has quit IRC16:36
*** ashleighfarnham has left #openstack-oslo16:36
bnemecdhellmann: I'm not aware of anything.  What would be the purpose?16:37
silehtdhellmann, perhaps oslo.config ConfigFilter ?16:37
dhellmannsileht: the filter doesn't hide them from deployers16:37
dhellmannsileht: I'm reviewing https://review.openstack.org/#/c/181010/3/specs/liberty/oslo.messaging-remove-double-reply.rst,cm16:37
dhellmannbnemec: ^^16:37
silehtdhellmann, oh, the bp need to be corrected so16:38
*** arnaud____ has quit IRC16:44
*** amuller has left #openstack-oslo16:52
openstackgerritElena Ezhova proposed openstack/oslo-incubator: Add documentation for launcher classes in service.py  https://review.openstack.org/18238616:56
openstackgerritJoshua Harlow proposed openstack/taskflow: Use hash path lookup vs path finding  https://review.openstack.org/18213216:59
*** mtreinish has quit IRC17:02
*** tteggel has quit IRC17:02
*** AAzza has quit IRC17:02
*** mtreinish_ has joined #openstack-oslo17:02
*** ashleighfarnham has joined #openstack-oslo17:02
*** mtreinish_ is now known as mtreinish17:02
*** yamahata has joined #openstack-oslo17:03
*** tteggel has joined #openstack-oslo17:03
*** flaper87 has quit IRC17:03
*** flaper87 has joined #openstack-oslo17:05
*** flaper87 has quit IRC17:06
*** flaper87 has joined #openstack-oslo17:06
*** AAzza_afk has joined #openstack-oslo17:06
*** AAzza_afk is now known as AAzza17:06
*** sdake has joined #openstack-oslo17:11
*** links has quit IRC17:14
*** sdake_ has quit IRC17:14
*** harlowja has quit IRC17:22
*** harlowja has joined #openstack-oslo17:22
*** achanda has joined #openstack-oslo17:30
*** exploreshaifali has quit IRC17:41
harlowjadims ^ that might interest u also17:42
*** vilobhmm11 has joined #openstack-oslo17:46
*** e0ne is now known as e0ne_17:47
*** ihrachyshka has quit IRC17:51
*** amuller has joined #openstack-oslo17:51
*** e0ne_ is now known as e0ne17:56
harlowjadamn, seems like my links never showed up17:56
harlowjalol17:56
harlowjareposting17:57
harlowjasamueldmq poke me on quota stuff to17:57
harlowjai've been working on https://etherpad.openstack.org/p/fix-the-quota-please which hopefully has some of the history /archalogy and ideas and ...17:57
harlowjasalv-orlando dims  ^17:57
harlowjaok, hopefully thats not broken this time (for some reason not showing up in eavesdrop)17:57
dimsharlowja: ack. wrapping something up17:57
harlowjathx17:57
harlowjamaybe eavesdrop broken, idk17:57
harlowjahaha17:57
harlowjaanyway, double posted, oh ya17:58
samueldmqharlowja, hi17:58
harlowjahi there17:58
harlowjahttps://etherpad.openstack.org/p/fix-the-quota-please  might interest u17:58
harlowjabeen working on that semi-internally, gathering some kind of basis for something to be fixed17:58
samueldmqdhellmann, salv-orlando so the biggest cons against quota as a separate service ...17:58
samueldmqa service needs to get involved for every action17:58
samueldmqso another single point of failure/bottleneck17:58
samueldmq .... that's the point people don't like I think17:59
samueldmqharlowja, yeah I will take a look17:59
harlowjacool17:59
harlowjasamueldmq i would agree, this has to be done carefully :)17:59
*** e0ne has quit IRC17:59
harlowjaand without trying to take over other projects stuff (to much)17:59
harlowjaat least not initially17:59
samueldmqharlowja, oh, your first point on that pad says that, great17:59
harlowja;)17:59
openstackgerritgaryk proposed openstack/oslo.vmware: Add support for dynamicProperty  https://review.openstack.org/18239817:59
*** mfedosin has joined #openstack-oslo17:59
harlowjasamueldmq hopefully some other useful stuff on that etherpad also18:00
samueldmqharlowja, great ... my team is developing the hierarchical multitenancy stuff in keystone18:00
harlowjaya, i and others have tried to capture something that hopefully will succed this time :)18:01
samueldmqharlowja, also we are grabbing some work on the hierarchical quotas implementation18:01
samueldmqharlowja, so it will be great to come up with all this together18:01
harlowjaya, there is some info about that there to18:01
harlowjaagreed18:01
harlowjavilobhmm11 and others are involved from y! and pretty kin on getting something to happen18:01
*** ericksonsantos has joined #openstack-oslo18:01
harlowja*and me*18:01
samueldmqericksonsantos, cc ^ read up :)18:02
harlowjafeel free to tweak that etherpad with any ideas u have18:02
samueldmqericksonsantos is working on the hierarchical driver on nova side18:02
samueldmqharlowja, k thanks18:02
harlowjacool18:02
harlowjanp, let's get something to happen18:03
harlowjathe 20th time around is the one that makes it right, lol18:03
harlowja:)18:03
harlowjasamueldmq as  soon as we have some decent etherpad, either at the summit we need to figure out the strategy to make something happen18:05
harlowjaand ensure we are very very much in touch with the various projects18:05
harlowja^ so that this plan doesn't fail again ....18:05
samueldmqharlowja, great ! I'll be at the summit, we can talk more about all this there :)18:07
harlowjacools18:07
samueldmqharlowja, however I still don't have  a great knowledge on the quota system :p18:07
samueldmqharlowja, your initial plan is to get soemthing similar to oslo.quota right ?18:08
samueldmqharlowja, since each service would still own its resources and use that common library18:08
*** tsekiyama has joined #openstack-oslo18:10
harlowjasamueldmq did u see my braindump @ bottom of https://review.openstack.org/#/c/132127/ :-P18:10
harlowjasamueldmq ya, we need to be careful here, i'm not 100% on the right approach yet either18:10
harlowjasomething simple to make starting integration easy18:10
ericksonsantosharlowja, nice to know that you're working with quota management. :)18:11
harlowjavs a service, which seems harder to start18:11
harlowjaericksonsantos trying to wrangle it a little :-P18:11
harlowjaits failed to many times, and its a pain point for yahoo18:11
harlowja*failed getting centralized/addressed/other alot18:12
harlowja*well like 4+ times i think, lol18:12
harlowjawith 'Known hacks:' (other that etherpad) also make me sad18:12
harlowja*on that etherpad18:12
samueldmqharlowja, nice .. I think a library containing only the duplicated enforcement code is the first step18:13
ericksonsantosharlowja, I see. I'll read the etherpad.18:13
samueldmqfor sure, since we will be changing nothing than putting common code together (oh I said common, it's oslo :))18:13
harlowjacool, let's see how this goes18:13
samueldmqk18:14
harlowjasamueldmq well we do need to think how to handle schema, eventually18:14
harlowjaif we want to go there18:14
harlowjabut thats imho sorta far off, there's enough work to get to that stage to keep people busy for a while18:14
harlowja*and u have to imho have a better foundation before that's even a concern...18:15
harlowjadon't try to fly before u can walk...18:15
*** amotoki_ has quit IRC18:15
samueldmqharlowja, hehe yep :p I neeed to deeply understand how different services implement their quota management18:15
harlowjaya18:15
harlowjawe seem to have some of the people that know this (not neutron though, anyone know that)18:16
samueldmqand see what's common/being duplicated18:16
harlowjavilobhmm11 i think understands the cinder quota, some nova folks18:16
harlowjadocumenting and understanding that as much as can be, would be a great first step (to writeup and understand that)18:16
harlowjai have some level of knowledge of nova, but not alot18:16
harlowjadims u da man for that right :-P18:17
samueldmqharlowja, great, do you have another etherpad ? (in which you write info on how quota works for different services)18:17
harlowjadon't18:17
harlowjamaybe a new section on that one?18:17
harlowjaor a linked one?18:17
dimsharlowja: i can help find things, yes. nova is vast :)18:17
harlowja;)18:18
harlowjacaptain dims sailing the nova sea18:18
harlowjalol18:18
samueldmqharlowja, we can put in a section, and if we see it gets huge, we split and link to another18:18
samueldmqharlowja, we change as we go :)18:18
harlowjasamueldmq on that etherpad there is some info scattered about how its done, maybe move that around also?18:18
harlowjasome links and such, probably should/could reorganize that18:18
harlowjaunder 'See:' (at top)18:19
samueldmqyeah, I will be taking a deeper look on that with ericksonsantos :)18:19
harlowjakk18:19
harlowjasounds good18:19
ericksonsantossure18:19
ericksonsantos:)18:19
dims:)18:19
vilobhmm11harlowja, dims : started working on https://review.openstack.org/#/c/173141/ ..will update finding on cinder-quota as and when i find more here https://etherpad.openstack.org/p/fix-the-quota-please…more than happy to help18:20
harlowjacool18:20
harlowjathx vilobhmm1118:20
dimsvilobhmm11: nice18:21
*** cdent has joined #openstack-oslo18:29
*** exploreshaifali has joined #openstack-oslo18:29
lifelessmordred: where's my +2+A? https://review.openstack.org/#/c/181785/18:32
lifelessmordred: I'd like that in 1.0.0 if we can (to salve the rpm heads)18:32
lifelessharlowja: hows rrepete?s issue18:32
harlowjalet me find him18:33
mordredlifeless: done18:33
harlowjalifeless poked him on YIM (will see if he gets on)18:34
harlowjaand then he can tell u, ha18:34
harlowja:-P18:34
harlowjahe's our main CI guy, so might be busy though, let's see18:35
lifelessharlowja: kk18:36
lifelessharlowja: no skin of my nose :)18:36
harlowja:)18:36
openstackgerritMerged openstack/oslo.vmware: Remove run_cross_tests.sh  https://review.openstack.org/18028218:41
openstackgerritMerged openstack/oslosphinx: Advertise support for Python3.4 / Remove support for Python 3.3  https://review.openstack.org/18152718:42
openstackgerritMerged openstack/oslotest: Advertise support for Python3.4 / Remove support for Python 3.3  https://review.openstack.org/18169818:42
*** rrepaka has joined #openstack-oslo18:43
rrepakalifeless: Hi18:44
harlowjarrepaka has arrived!18:44
harlowja:)18:44
rrepakalifeless: Yesterday i tried the patch http://paste.ubuntu.com/11086963/18:44
lifelessrrepaka: and what did it output?18:46
rrepakalifeless: i was unable to see the log output18:46
rrepakalifeless: How to i configure the log file for pbr ?18:46
lifelessrrepaka: the stdout is the log18:47
lifelessrrepaka: how did you test it?18:47
rrepakalifeless: I checked out the pbr code from git hub, applied your patch18:48
rrepakalifeless: did "python setup.py install" in pbr module18:48
lifelessrrepaka: then went to the olso.config dir and checked the version?18:49
rrepakalifeless: after that i went to oslo-config modle and ran "python setup.py --version18:49
lifelessrrepaka: ok, try http://paste.ubuntu.com/11100035/ instead18:49
lifelessthat should drop you into a debugger18:49
lifelesshave you used pdb before?18:49
rrepakalifeless: sure18:49
harlowjadhellmann added comment on https://review.openstack.org/#/c/181688/ for why not removing just yet, soon is the answer to that one :)18:51
*** e0ne has joined #openstack-oslo18:51
harlowjasoon like probably in next few days (hopefully)18:51
*** Rockyg has joined #openstack-oslo18:53
lifelessrrepaka: I put the breakpoint right before the routine used to calculate versions18:54
lifelessrrepaka: you'll want to print out the parameters18:54
lifelessand then step in18:54
lifelessand at each call within that routine print the function inputs and outputs18:55
lifelesse.g. the first one is18:55
lifelessprint tag, distance, git_dir18:55
lifelessyou'll drop into pdb when installing pbr too, just continue out of it there18:55
lifelesssince its oslo.config we care about18:55
rrepakalifeless: no i didnt use pdb18:57
lifelessrrepaka: ok, quick primer18:57
rrepakalifeless: I now have latest pbr code patched18:58
lifelessc<ENTER> to continue18:58
lifelessprint to print stuff, just like in python18:58
lifelesss<enter> to step into a function18:58
lifelessn<enter> to step over it18:58
rrepakalifeless: how to i configure the python to pick the code from source18:58
lifelessrrepaka: I'd use a virtualenv for testing18:58
lifelessinside the virtualenv do18:59
lifelesspip install -U pip setuptools18:59
lifelessthen pip install -e <path-to-pbr>18:59
rrepakarrepaka: ok18:59
harlowjano talking to yourself18:59
rrepakalifeless: ok got it let me do pip install -e first19:00
*** exploreshaifali has quit IRC19:01
rrepakalifeless: i am able to start the debug run, i see the following "/home/rrepaka/community/pbr/pbr/packaging.py(582)_get_version_from_git()->'1.4.0.0a5.dev5'"19:02
lifelessrrepaka: ok so that indicates you're at the end of the function we want to dig through19:02
lifelessrrepaka: continue then run it again19:03
rrepakalifeless: i will run and send you pastebin output19:03
lifelessthis time step into the _get_version_from_git_target call19:03
rrepakalifeless: sure doing it19:04
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove hack + fix for issue no longer needed  https://review.openstack.org/18241619:07
sdagueso... question - https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/notify/notifier.py#L18819:07
sdagueis audit in the notification path supposed to be deprecated now in the same way as for logging?19:07
openstackgerritDavanum Srinivas (dims) proposed openstack/stevedore: Fix Python versions supported  https://review.openstack.org/18152419:08
rrepakalifeless: http://paste.ubuntu.com/11100215/19:08
rrepakalifeless:http://paste.ubuntu.com/11100333/19:14
*** ccrouch has joined #openstack-oslo19:15
*** openstackgerrit_ has joined #openstack-oslo19:16
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove custom py26/py27 and py33 environment + fix requirements  https://review.openstack.org/18242319:24
harlowjadhellmann ^ should be that final thing that goes in19:24
*** openstackgerrit_ has quit IRC19:25
openstackgerritSean McGinnis proposed openstack/oslo-incubator: Clean up logging to conform to guidelines  https://review.openstack.org/18242419:28
*** jaosorior has quit IRC19:32
rrepakalifeless: more depth of debug run  http://paste.ubuntu.com/11100657/19:32
*** achanda has quit IRC19:33
*** shakamunyi has quit IRC19:35
dhellmannharlowja: +219:35
harlowjathx19:35
*** barra204 has quit IRC19:36
harlowjalet me just merge https://review.openstack.org/#/c/181688/ into that19:37
harlowjaand all will be merry19:37
openstackgerritDoug Hellmann proposed openstack/oslo-incubator: Remove versionutils  https://review.openstack.org/18242819:37
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove custom py26/py27 and py33 environment + fix requirements  https://review.openstack.org/18242319:40
harlowjaok dokie, all now merry19:41
openstackgerritMerged openstack/oslo.context: Remove support for Python 3.3  https://review.openstack.org/18176419:43
openstackgerritMerged openstack/oslo.db: Remove support for Python 3.3  https://review.openstack.org/18176519:43
openstackgerritMerged openstack/oslo.log: Advertise support for Python3.4 / Remove support for Python 3.3  https://review.openstack.org/18153519:43
openstackgerritMerged openstack/oslo.messaging: Remove support for Python 3.3  https://review.openstack.org/18176619:43
openstackgerritMerged openstack/oslo.policy: Remove support for Python 3.3  https://review.openstack.org/18176719:44
openstackgerritMerged openstack/oslo.serialization: Advertise support for Python3.4 / Remove support for Python 3.3  https://review.openstack.org/18153219:44
openstackgerritMerged openstack/oslo.utils: Advertise support for Python3.4 / Remove support for Python 3.3  https://review.openstack.org/18153119:44
openstackgerritMerged openstack/oslo.vmware: Remove support for Python 3.3  https://review.openstack.org/18152919:44
openstackgerritMerged openstack/taskflow: Remove tox py33 environment no longer used  https://review.openstack.org/18168619:44
harlowjadeath to py3.319:45
harlowjamay u rest in peace19:45
*** shakamunyi has joined #openstack-oslo19:49
*** barra204 has joined #openstack-oslo19:49
openstackgerritDoug Hellmann proposed openstack/oslo.log: Remove is_compatible from versionutils  https://review.openstack.org/17047119:50
openstackgerritDoug Hellmann proposed openstack/oslo.log: Add versionutils options to list_opts  https://review.openstack.org/16776919:50
openstackgerritDoug Hellmann proposed openstack/oslo.log: Add versionutils to API documentation  https://review.openstack.org/16776819:50
lifelessrrepaka: thanks, looking19:55
openstackgerritMerged openstack/debtcollector: Ensure that the incoming 'new_class' is actually a class  https://review.openstack.org/17261319:57
openstackgerritMerged openstack/oslo.config: Fix logging of deprecated opts with dest override  https://review.openstack.org/16939219:57
openstackgerritMerged openstack/oslo.rootwrap: Generate a oslo-rootwrap console script  https://review.openstack.org/17434919:57
openstackgerritMerged openstack/oslo.config: Allow loading custom config files into Config Fixture.  https://review.openstack.org/17256620:02
*** achanda has joined #openstack-oslo20:04
*** ashleighfarnham has quit IRC20:11
openstackgerritMerged openstack/oslo-incubator: Remove timeutils.strtime() usage  https://review.openstack.org/16534020:12
openstackgerritMerged openstack/oslo-incubator: Add gerrit dashboard files  https://review.openstack.org/16727220:12
openstackgerritMerged openstack/oslosphinx: Remove the unneeded horizontal scrollbar  https://review.openstack.org/17207320:12
*** flaper87 has quit IRC20:20
*** flaper87 has joined #openstack-oslo20:20
*** achanda has quit IRC20:21
*** ashleighfarnham has joined #openstack-oslo20:26
openstackgerritJames Polley proposed openstack-dev/pbr: WIP: Teach pbr to read extras from setup.cfg  https://review.openstack.org/18179520:26
tchaypolifeless: ^^20:27
lifelesstchaypo: https://review.openstack.org/182433 <- a sample use case20:32
tchaypowhich should be on master, according to the comments20:35
amullersileht: there?20:35
tchaypoIs there somewhere we should be documenting this?20:35
*** vilobhmm11 has quit IRC20:35
*** achanda has joined #openstack-oslo20:36
dimstchaypo: etherpads for oslo are open, there's a session on optional dependencies...20:36
*** vilobhmm1 has joined #openstack-oslo20:37
*** openstackgerrit has quit IRC20:37
*** openstackgerrit has joined #openstack-oslo20:37
tchaypodims: do you have a link handy?20:37
dimshttps://etherpad.openstack.org/p/YVR-oslo-optional-dependencies20:38
dimstchaypo: ^^20:38
tchaypowhich is probably linked from https://etherpad.openstack.org/p/liberty-oslo-summit-planning, which I just found in my email..20:38
*** vilobhmm1 has quit IRC20:38
tchaypoactually it doesn’t seem to be20:40
*** ashleighfarnham has quit IRC20:41
dimstchaypo: https://wiki.openstack.org/wiki/Summit/Liberty/Etherpads is the main landing page, oslo etherpads are listed there by time/date20:42
*** mriedem has quit IRC20:44
tchaypothanks20:45
dimsharlowja: just saw this float by - https://review.openstack.org/#/c/182445/1/specs/liberty/approved/quotas-reimagined.rst,cm20:47
*** vilobhmm1 has joined #openstack-oslo20:49
*** vilobhmm1 has quit IRC20:50
*** vilobhmm1 has joined #openstack-oslo20:50
tchaypoI’ve added that to my sched20:51
tchaypolifeless: Is there anything we can do for 182433 right now? Maybe clone it to master, put the extra in setup.cfg, and add a dependency link to the pbr review?20:52
*** mdbooth has quit IRC20:52
*** e0ne has quit IRC20:52
*** e0ne has joined #openstack-oslo20:53
*** kgiusti has left #openstack-oslo20:54
lifelesstchaypo: we need to unbreak neutron immediately20:57
lifelesstchaypo: so no. Once we've got markers in requirements.txt working in a pbr release we can circle back and cleanup neutron.20:58
*** mdbooth has joined #openstack-oslo20:58
*** ozamiatin has joined #openstack-oslo21:00
tchaypomarkers in requirements.txt? I’ve been aiming for markers in setup.cfg21:00
*** vilobhmm1 has quit IRC21:01
*** vilobhmm1 has joined #openstack-oslo21:02
*** shardy is now known as shardy_z21:02
*** e0ne has quit IRC21:03
tchaypoIn that case, I’m going to go have breakfast and coffee21:03
*** vilobhmm1 has quit IRC21:03
tchaypoand then come back and document pbr’s new support for extras and env markers21:04
*** vilobhmm1 has joined #openstack-oslo21:04
*** mriedem has joined #openstack-oslo21:07
*** stevemar has quit IRC21:08
*** amuller is now known as amuller_afk21:11
*** ashleighfarnham has joined #openstack-oslo21:12
lifelesstchaypo: ok so21:19
lifelesstchaypo: same same, one big arc :)21:19
lifelesstchaypo: what you're doing is v closely related, and may even fit in the same patch21:19
lifelesstchaypo: I'm going to look at your current stuff soon21:20
*** rrepaka has quit IRC21:22
*** ashleighfarnham has quit IRC21:26
*** ozamiatin has quit IRC21:35
*** salv-orlando has quit IRC21:42
*** cdent has quit IRC21:47
dimssigmavirus24: i am seeing lots of hits for "Connection pool is full, discarding connection" in logstash, seems to be from connectionpool.py. am i reading this right?21:54
sigmavirus24dims: in urllib3, correct, but I'm curious where it's coming from21:58
sigmavirus24I had gone around attempting to squash the cause of that21:58
*** vilobhmm1 has quit IRC22:00
*** stpierre has quit IRC22:03
*** vilobhmm1 has joined #openstack-oslo22:04
*** vilobhmm1 has quit IRC22:05
*** vilobhmm1 has joined #openstack-oslo22:05
*** vilobhmm1 has quit IRC22:07
*** vilobhmm11 has joined #openstack-oslo22:10
*** bogdando has quit IRC22:10
harlowjadims thx22:10
harlowjaintersting22:10
*** jecarey has quit IRC22:13
*** jaypipes has quit IRC22:13
lifelesstchaypo: ok pop() back to you22:13
tchaypohuh22:13
tchaypohow did you manage to do that seconds after i sat down and opened the window?22:14
openstackgerritVictor Stinner proposed openstack/oslo.versionedobjects: VersionedObjectDictCompat inherits MutableMapping  https://review.openstack.org/18247722:16
lifelesstchaypo: its a skill22:17
*** bknudson has quit IRC22:18
tchaypohow far is canterbury from you?22:18
tchaypo*looks at maps* Oh, you’re *in* canterbury.22:18
lifelessI'm in waimakariri22:19
tchaypoaccording to google maps, waimakariri has some interesting across-the-river bits22:20
lifelessyup22:20
tchaypoit looks like someone was coloring in “this area is waimakariri” but their pen was a bit too wide and accidentally coloured in little bits on the other side of the river22:21
tchaypoI’m sure the real historical reason is different22:21
openstackgerritVictor Stinner proposed openstack/oslo.versionedobjects: VersionedObjectDictCompat inherits MutableMapping  https://review.openstack.org/18247722:23
tchayposo anyway, back to my patch22:23
*** Rockyg has quit IRC22:24
tchaypohttp://logs.openstack.org/95/181795/8/check/check-pbr-installation-dsvm/bfc99a8/console.html#_2015-05-12_20_53_57_833 Is that related to the neutron issue you mentioned earlier?22:26
*** dims_ has joined #openstack-oslo22:28
lifelesswell22:28
lifelessthe river didn't stay will22:28
lifelessstill22:28
*** sdake_ has joined #openstack-oslo22:29
*** dims has quit IRC22:30
dims_sigmavirus24: http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkNvbm5lY3Rpb24gcG9vbCBpcyBmdWxsLCBkaXNjYXJkaW5nIGNvbm5lY3Rpb25cIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNDMyMDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDMxNDY5ODI5MTYwfQ==22:30
*** sdake has quit IRC22:33
sigmavirus24dims_: so previously glanceclient and swiftclient were the two big offenders22:35
sigmavirus24Now all of these are coming out of devstack gates from screen-n-api22:35
sigmavirus24(or at least the first bunch that I've looked at)22:35
sigmavirus24Found one from glance and one other from n-cpu22:36
dims_sigmavirus24: i feel i saw one where nova api was calling glance client22:36
*** ashleighfarnham has joined #openstack-oslo22:36
sigmavirus24It looks like Nova is streaming responses and not properly handling them if they're not completely consumed22:37
sigmavirus24dims_: see https://review.openstack.org/#/c/147678/ for an idea of how I squashed it in glanceclient (there's a similar patch in swiftclient)22:38
lifelesstchaypo: doing a detailed review now22:41
tchaypoThanks22:41
*** salv-orlando has joined #openstack-oslo22:43
*** sdake has joined #openstack-oslo22:43
*** ihrachyshka has joined #openstack-oslo22:44
*** salv-orlando has quit IRC22:46
*** sdake_ has quit IRC22:46
*** vilobhmm11 has quit IRC22:49
*** vilobhmm1 has joined #openstack-oslo22:49
dims_sigmavirus24: don't see any iter_content in nova23:03
*** amuller_afk is now known as amuller23:05
lifelesstchaypo: thats looking good23:07
lifelesstchaypo: thoughts and the next bit included23:07
lifelessnow to write a blog post about this and stuff and stuff23:07
sigmavirus24dims_: must be in something nova's using with stream=True then23:09
sigmavirus24dims_: in general it's not a serious message, it's a debug level message from urllib323:09
sigmavirus24It /may/ hint towards a potential socket leak23:10
sigmavirus24But that's not necessarily the case23:10
*** ozamiatin has joined #openstack-oslo23:19
lifelesstchaypo: crickets?23:25
tchaypoI’m breathing deeply and trying to let go of the gas bill thing23:26
harlowjalifeless added comment on https://review.openstack.org/#/c/182423/23:31
harlowjamaybe i should just totally drop Mysql-python blah blah23:31
harlowja*thats the only test-requirements differnce, lol23:31
harlowjaseems like that would be ok (and is the general direction of all the things happening anway)23:31
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove custom py26/py27 and py33 environment + fix requirements  https://review.openstack.org/18242323:33
openstackgerritJoshua Harlow proposed openstack/taskflow: Remove custom py26/py27 and tweak requirements  https://review.openstack.org/18242323:34
tchaypookay. Calm has been restored, approximately.23:34
harlowjavilobhmm1 u might be interested in https://review.openstack.org/#/c/182445 to23:38
harlowjaintersting to see what will happen there23:38
openstackgerritMorgan Fainberg proposed openstack/oslo.log: Make remove_in=0 (no removal) use a better syntax  https://review.openstack.org/16818623:40
morganfainberg^^ that is a simple rebase, just needs someone to press +A again23:41
vilobhmm1sure…thanks harlowja for the link23:44
harlowjanp23:44
*** ericksonfgds has joined #openstack-oslo23:45
dhellmannmorganfainberg: +W23:46
morganfainbergdhellmann: tyvm sir23:46
dhellmannmorganfainberg: think nothing of it23:47
lifelessharlowja: do you depend on oslo.db ?23:48
harlowjanope, not right now, maybe someday23:48
* harlowja trying to keep the additions of oslo.* deps to a minmum if i can23:50
harlowjaand only things like oslo.utils or oslo.serialization which are dinky23:50
harlowjaalthough i should be able to easily switch to https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/session.py#L712 (and use that, vs just use sqlalchemy engine calls via the standard sqlalchemy stuffs...)23:51
openstackgerritDan Smith proposed openstack/oslo.versionedobjects: VersionedObjectDictCompat inherits MutableMapping  https://review.openstack.org/18247723:51
openstackgerritDan Smith proposed openstack/oslo.versionedobjects: Add delattr support  https://review.openstack.org/18250123:51
harlowjabut i've always had this tension of making taskflow just that much more only openstack useable23:52
harlowja^ which i don't really like :-/23:52
harlowjalifeless whats a project that uses the environment markers in setup.py like u said23:55
harlowjacan just do that until https://review.openstack.org/#/c/181795/ happens23:56

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