Wednesday, 2015-03-11

*** amalagon has quit IRC00:01
*** kgriffs is now known as kgriffs|afk00:05
*** achanda has quit IRC00:18
*** achanda has joined #openstack-zaqar00:18
*** achanda has quit IRC00:23
*** amalagon has joined #openstack-zaqar01:11
*** amalagon has quit IRC01:17
*** akanksha has quit IRC02:47
*** achanda has joined #openstack-zaqar02:58
*** achanda has quit IRC03:10
*** chandankumar has joined #openstack-zaqar03:11
*** flwang has quit IRC03:54
*** achanda has joined #openstack-zaqar04:07
*** miqui has quit IRC04:14
*** chandankumar has quit IRC05:17
*** chandankumar has joined #openstack-zaqar05:20
*** chandankumar has quit IRC05:20
*** achanda has quit IRC05:31
*** achanda has joined #openstack-zaqar05:34
*** achanda has quit IRC05:48
*** achanda has joined #openstack-zaqar05:52
*** achanda has quit IRC05:58
*** achanda has joined #openstack-zaqar06:01
*** achanda has quit IRC06:14
*** chandankumar has joined #openstack-zaqar06:41
*** exploreshaifali has joined #openstack-zaqar07:14
exploreshaifalimorning!!!07:17
*** flwang has joined #openstack-zaqar08:05
*** exploreshaifali has quit IRC08:05
*** exploreshaifali has joined #openstack-zaqar08:07
flwangflaper87: ping08:31
*** flwang has quit IRC09:21
*** flwang has joined #openstack-zaqar09:32
*** chandankumar has quit IRC09:32
*** chandankumar has joined #openstack-zaqar09:45
flwangflaper87: around?10:06
*** exploreshaifali has quit IRC10:38
*** chandankumar has quit IRC10:40
flwangflaper87: just update the notification service status10:58
flwangi'm working on the redis driver, will submit a patch on next Mon or Tue10:59
flwangmeanwhile, I'm reviewing Shaifali's patch11:07
rsFFbtw, https://review.openstack.org/#/c/163223/ how can see what is the offending code?11:07
*** akanksha has joined #openstack-zaqar11:30
vkmcmorning!12:05
vkmcrsFF, hi there! you can check what went wrong by looking at the gates logs12:06
vkmcrsFF, http://logs.openstack.org/23/163223/1/check/gate-zaqar-pep8/ab8f2ba/console.html#_2015-03-10_23_28_05_90512:06
vkmcrsFF, I highlighted the problem12:06
vkmcrsFF, the fix looks great btw12:07
rsFFhaaaaaa12:07
rsFFlol12:07
rsFFso now should i do a ammend?12:08
vkmcrsFF, exactly12:08
rsFFoki as soon as i get to the build box...12:09
rsFFany more remarks?12:09
vkmcrsFF, nothing else, everything else looks fine12:09
rsFFkk12:09
vkmcrsFF, thanks!12:09
*** exploreshaifali has joined #openstack-zaqar12:28
*** chandankumar has joined #openstack-zaqar12:43
openstackgerritZhi Yan Liu proposed openstack/zaqar: Integrate OSprofiler with Zaqar  https://review.openstack.org/14135612:52
*** sriram has joined #openstack-zaqar13:08
*** dynarro has joined #openstack-zaqar13:10
*** mpanetta has joined #openstack-zaqar13:27
*** dynarro has quit IRC13:28
*** chandankumar has quit IRC13:30
*** dynarro has joined #openstack-zaqar13:43
akankshavkmc, I am trying to work on this bug https://bugs.launchpad.net/zaqar/+bug/1367024. Can you help me a little as to how to approach this ?13:51
openstackLaunchpad bug 1367024 in zaqar "Redis driver doesn't explicitly validate UUIDs" [Low,Confirmed] - Assigned to Akanksha Srivastava (akanksha-dlf)13:52
*** ametts has joined #openstack-zaqar13:52
vkmcakanksha, so, first thing, you should ask first before taking a bug that is assigned to somebody else13:58
akankshaUmm okay13:58
akankshaI didnt know that sorry13:58
vkmcakanksha, no worries, something for future reference13:58
akankshaI'll unassign myself for now then?13:58
vkmcakanksha, oh no, let's ask dynarro13:59
akankshaAnd ma'am for bugs which are unassigned?13:59
vkmcdynarro, hey there, you were working on https://bugs.launchpad.net/zaqar/+bug/1367024?13:59
openstackLaunchpad bug 1367024 in zaqar "Redis driver doesn't explicitly validate UUIDs" [Low,Confirmed]13:59
flaper87flwang: ping ?14:00
flaper87gosh, you must be sleeping :(14:00
*** exploreshaifali has quit IRC14:02
dynarrovkmc: hey! yes I was :)14:03
* flaper87 wonder where his manners are14:03
flaper87GOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOD MORNING PPL14:03
flaper87or whatever it is wherever you are14:04
* vkmc wonders the same14:04
flaper87vkmc: shut up14:04
flaper87>.>14:04
vkmcflaper87, bring coffee, at least14:04
* flaper87 gives vkmc coffee \_/?14:04
flaper87speaking of which, lemme get some14:04
vkmc:D14:04
vkmcdynarro, oh ok14:04
vkmcakanksha, so, let's find another bug for you14:05
vkmcakanksha, is that ok?14:05
akankshavkmc, this was an unassigned bug. So I assigned it to myself is that okay? https://bugs.launchpad.net/zaqar/+bug/122293214:05
openstackLaunchpad bug 1222932 in zaqar "perf: Functions defined inline" [Low,Triaged] - Assigned to Akanksha Srivastava (akanksha-dlf)14:05
vkmcakanksha, sure thing!14:05
flaper87akanksha: hey there, how are you doing?14:06
flaper87welcome14:06
akankshaThanks flaper8714:06
akankshaI am good14:06
*** cpallares has joined #openstack-zaqar14:06
akankshaflaper87, can you give me more details on how to go about solving this bug?14:06
akankshahttps://bugs.launchpad.net/zaqar/+bug/122293214:06
openstackLaunchpad bug 1222932 in zaqar "perf: Functions defined inline" [Low,Triaged] - Assigned to Akanksha Srivastava (akanksha-dlf)14:07
akankshaflaper87, Can you tell me which places I need to check for inline function definitions?14:10
flaper87akanksha: nested functions aren't any different than other funcions, they just appear in local contexts and are considered closures14:14
*** dynarro has quit IRC14:14
*** dynarro has joined #openstack-zaqar14:15
akankshaflaper87, as I understand that defining a function inside another function affects the performance. So if they are unnecessarily defined inside another function what we can do is define it outside and call it wherever they are needed?14:17
flaper87akanksha: correct, unless you need to capture the environment of the caller function, in that case you may want to use a nested function.14:19
flaper87The impact on performance is not HUGE but it may be if the function is called many many times14:19
*** dynarro has quit IRC14:19
akankshaSince the bug was reported, I am guessing there would be such places where the environment of the caller function can be passed as args to a function?14:21
flaper87akanksha: right14:21
akankshaflaper87, so should I look for such places in the codebase or is there a list or something handy which I can refer to?14:22
akankshaflaper87, I am new to zaqar and am still familiarising myself with the workflow so forgive me if I am not talking sense.14:23
vkmcakanksha, you are making complete sense14:24
vkmcakanksha, you should locate those places in the codebase14:24
vkmcakanksha, unfortunately, the reporter didn't mention where those functions are defined14:25
akankshavkmc, I was thinking maybe I'll go through all files and make a not of places where I find nested functions and then tackle them one-by-one?14:27
akankshavkmc, does that seem like a good approach?14:27
akankshathat was even if I am unable to resolve all such occurences, someone else will atleast have a list of places to check in case they want to solve the bug later?14:29
akanksha*that way14:29
vkmcakanksha, it sounds good to me14:29
vkmcakanksha, but it will be a lot of work for you14:29
vkmcakanksha, maybe we can find another low hanging fruit14:30
vkmcand ask the reporter if he can submit more information14:30
akankshaHmm14:32
vkmcunless you want to work on that, I'm ok with it14:33
akankshaAlright, lets search for another bug meanwhile. We can ask for more information and wait for a reply on that. If we get a reply I'll work on it or whenever I have extra time14:33
vkmcakanksha, that sounds great14:34
vkmcakanksha, the other day I filed one you might find interesting14:34
akankshaOkay.14:34
vkmchttps://bugs.launchpad.net/zaqar/+bug/142939314:34
openstackLaunchpad bug 1429393 in zaqar "Move debug option to common options" [Medium,New]14:34
vkmclet me know what do you think14:35
akankshavkmc, This sounds interesting and doable. Can you give me some more information on common options though. I dont understand what that means14:36
vkmcakanksha, sure thing14:37
akankshavkmc, where is the debug option located in the code?14:41
*** chandankumar has joined #openstack-zaqar15:00
*** kgriffs|afk is now known as kgriffs15:18
*** exploreshaifali has joined #openstack-zaqar15:34
*** exploreshaifali has quit IRC15:42
*** kgriffs has quit IRC16:13
*** flwang1 has quit IRC16:14
*** kgriffs has joined #openstack-zaqar16:15
*** flwang1 has joined #openstack-zaqar16:17
*** mpanetta has quit IRC16:25
*** mpanetta_ has joined #openstack-zaqar16:25
*** dynarro has joined #openstack-zaqar16:28
*** exploreshaifali has joined #openstack-zaqar16:44
*** openstack has joined #openstack-zaqar16:55
*** mpanetta_ has quit IRC17:15
dynarroakanksha: sorry, I was working on https://bugs.launchpad.net/zaqar/+bug/1367024 but I'm not really working on it at the moment...that's what I meant earlier. So there's not problem if you want to work on it ;)17:16
openstackLaunchpad bug 1367024 in zaqar "Redis driver doesn't explicitly validate UUIDs" [Low,Confirmed] - Assigned to Doraly Navarro (doralynavarro)17:16
*** mpanetta has joined #openstack-zaqar17:22
*** exploreshaifali has quit IRC17:29
*** chandankumar has quit IRC17:36
*** chandankumar has joined #openstack-zaqar17:44
*** chandankumar has quit IRC17:47
*** achanda has joined #openstack-zaqar17:54
*** exploreshaifali has joined #openstack-zaqar18:01
*** reed has joined #openstack-zaqar18:03
*** reed has quit IRC18:03
*** reed has joined #openstack-zaqar18:03
*** dynarro has quit IRC18:11
*** chandankumar has joined #openstack-zaqar18:11
*** flwang has quit IRC18:39
*** chandankumar has quit IRC18:57
*** exploreshaifali has quit IRC19:03
akankshavkmc,ping?19:09
*** achanda has quit IRC19:27
*** achanda has joined #openstack-zaqar19:38
*** chandankumar has joined #openstack-zaqar19:41
*** kgriffs is now known as kgriffs|afk19:48
*** flwang has joined #openstack-zaqar19:52
*** PrincessRiikka has quit IRC19:54
openstackgerritRicardo Ferreira proposed openstack/zaqar: Syntax enhancements  https://review.openstack.org/16322320:01
openstackgerritVictoria Martínez de la Cruz proposed openstack/zaqar: Adds websockets driver to Zaqar server  https://review.openstack.org/14015520:02
*** kgriffs|afk is now known as kgriffs20:02
*** exploreshaifali has joined #openstack-zaqar20:03
vkmcakanksha, sorry, I had to rush20:05
vkmcakanksha, could you check out the code_20:05
akankshakgriffs,flaper87, I want to solve this bug and I am just getting started. Could you point me in the right direction https://bugs.launchpad.net/zaqar/+bug/136702420:21
openstackLaunchpad bug 1367024 in zaqar "Redis driver doesn't explicitly validate UUIDs" [Low,Confirmed] - Assigned to Doraly Navarro (doralynavarro)20:21
*** chandankumar has quit IRC20:24
kgriffsakanksha: from what I recall, we aren't checking that the IDs passed into the driver are valid UUIDs (input validation - security). We just pass through the string.20:30
kgriffsakanksha: so, I'd say the approach would be to validate every ID passed into a driver method, before ever sending it to redis.20:31
akankshavalid uuids means existing in the database or just following the general uuid scheme?20:33
akankshaKgriffs: If its the latter (or even the former) I guess we could just write a method which would validate the UUID and then call the driver method. We could pass the driver method as an argument into our validator and call it inside our validator or just call the method after validation(before every instance of passing the UUID into a driver method we could20:38
akankshacall that method and flag it as an invalid UUID and check the flag before calling our driver)20:38
akankshakgriffs: can you point me to the specific drivers?20:39
akankshaSo I can have a look?20:39
*** achanda has quit IRC20:55
*** mpanetta has quit IRC21:01
kgriffsakanksha: https://github.com/openstack/zaqar/tree/master/zaqar/storage/redis21:04
akankshakgriffs: where do you think I should implement the UUID validation?21:05
kgriffsyou could start by looking at the messages controller21:06
kgriffshttps://github.com/openstack/zaqar/blob/master/zaqar/storage/redis/messages.py21:06
akankshaI was reading up on general UUID validation and all that has to done is apparently pass it to the python UUID() method and it will raise a value error if its not a valid UUID.21:07
kgriffsakanksha: that's the easiest way. I wonder how expensive that call is?21:08
akankshaHmm okay lemme look at more ways.21:08
kgriffsI just ran a quick test on my MBP and got 3.55 microseconds. It's probably OK.21:09
akankshaOh cool21:12
akankshaThen we can do that21:12
kgriffsinteresting, I found this: https://pypi.python.org/pypi/pyvalid/0.921:12
kgriffsnot sure on how much overhead it adds, but may be a way to DRY up validation logic21:13
kgriffsalso, not sure if it is in requirements.txt or oslo has it's own way of doing this.21:13
kgriffs(global requirements)21:14
kgriffshtmmm21:14
kgriffshttps://github.com/openstack/requirements/blob/master/global-requirements.txt21:14
kgriffsno pyvalid21:15
kgriffsflaper87 should know about oslo21:15
akankshaWe could use it21:16
akanksha@accepts(object, Validator.password_checker)21:16
akankshaThis is an example usage21:17
akankshawhere it uses a validation function21:17
akankshaWe could just use the accepts wrapper before every function21:17
akankshawhich uses uuids21:17
akankshaAdd pyvalid to requirements maybe?21:18
kgriffsakanksha: maybe, but I think we'd have to get it added to global-requirements.txt - might be a challenge.21:25
* kgriffs still thinks global-requirements.txt hurts more than it helps.21:26
*** achanda has joined #openstack-zaqar21:28
akankshaHehe XD21:30
akankshaGlobal requirements gave me a very hard time when i tried installing zaqar behind a proxy21:30
*** boris-42 has quit IRC21:32
akankshaSo for now should I go for pyvalid or do a normal implementation of calling the validator before every function call?21:33
akankshaIf we do get pyvalid added later in requirements we will just need to change the validator call to the accepts decorator right?21:34
akankshakgriffs: what do you think? Also please tell me where to write my validator function since I am new and have no clue. Still need to orients myself around the code21:36
akanksha*orient21:36
kgriffsakanksha: hmmm... I kind of like the decorator approach, so that may be the way to go even if we have to create our own in lieu of using pyvalid. We could model it after pyvalid, although at some point it gets pretty silly (why not just use pyvalid?)21:38
kgriffsYou would apply the decorator to controller methods that take a message ID. For example - https://github.com/openstack/zaqar/blob/master/zaqar/storage/redis/messages.py#L37221:38
akankshaYeah21:39
akankshaDecorator follows DRY.21:40
akankshaWriting the decorator may not be hard. Should I look into it?21:41
*** sriram has quit IRC22:01
*** exploreshaifali has quit IRC22:04
*** csoukup has joined #openstack-zaqar22:09
*** exploreshaifali has joined #openstack-zaqar22:31
flaper87flwang1: ping22:50
flwang1flaper87: pong22:50
flaper87kgriffs: jeeeeeeeeeeeeeeeeeeeeeeesus, you're alive!22:50
flaper87flwang1: hey, so, notifications. How's it going?22:50
flwang1i'm working on the redis driver, will submit a patch next Mon22:51
flwang1and meanwhile, i'm reviewing the patch from Shaifali22:51
flaper87flwang1: ok, count on it! :)22:51
flaper87as in, I'm counting on it22:51
flwang1flaper87: I hope we can close this in m-322:52
flwang1really busy recently, lots of internal stuff22:53
*** echevemaster has joined #openstack-zaqar22:56
flaper87flwang1: np :)22:57
flaper87kgriffs: say hi to me22:57
flaper87>.>22:57
* flaper87 says hi to kgriffs22:57
*** exploreshaifali has quit IRC23:10
openstackgerritMerged openstack/zaqar: Adds websockets driver to Zaqar server  https://review.openstack.org/14015523:20
* kgriffs says hi to flaper8723:39
*** sriram has joined #openstack-zaqar23:49
*** sriram has quit IRC23:51
*** sriram has joined #openstack-zaqar23:52
openstackgerritMerged openstack/zaqar: Updated from global requirements  https://review.openstack.org/16159323:56

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