Thursday, 2014-09-11

*** reed has joined #openstack-zaqar00:04
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-zaqarclient: Updated from global requirements  https://review.openstack.org/11406800:31
openstackgerritOpenStack Proposal Bot proposed a change to openstack/zaqar: Updated from global requirements  https://review.openstack.org/12033000:32
*** kgriffs|afk is now known as kgriffs01:21
*** amitgandhinz has quit IRC01:42
*** amitgandhinz has joined #openstack-zaqar01:43
*** kgriffs is now known as kgriffs|afk01:44
*** amitgandhinz has quit IRC01:49
*** jeffrey4l has joined #openstack-zaqar02:32
*** vkmc has quit IRC02:40
*** jeffrey4l has quit IRC03:17
*** jeffrey4l has joined #openstack-zaqar03:29
*** sgotliv has joined #openstack-zaqar04:10
*** jeffrey4l has quit IRC04:13
*** echevemaster has quit IRC04:22
*** jeffrey4l has joined #openstack-zaqar04:29
*** prashanthr_ has joined #openstack-zaqar05:02
*** prashanthr_ has quit IRC05:22
*** reed has quit IRC05:22
*** jeffrey4l has quit IRC05:35
*** jeffrey4l has joined #openstack-zaqar05:52
*** flaper87|afk is now known as flaper8705:58
flaper87o/06:05
wpfflwang, flaper87 : all, would you please help to check  https://review.openstack.org/#/c/117706/ again.   thanks06:08
flaper87wpf: sure06:08
wpfflaper87:  thanks , :P06:09
*** flwang1 has quit IRC06:11
flaper87wpf: a tiny nit that I think is worth it06:15
jeffrey4lflaper87, pls help to check https://review.openstack.org/#/c/118269/ again. You added -1 due to the pass of j-3.06:18
flaper87jeffrey4l: sure06:18
flaper87:)06:18
jeffrey4lthx06:18
* flaper87 so happy to have more patches coming in in zaqar06:18
wpfflaper87:  I will check it now06:20
*** jeffrey4l has quit IRC06:26
*** jeffrey4l has joined #openstack-zaqar06:37
*** jeffrey4l has quit IRC07:14
openstackgerritPeng Fei Wang proposed a change to openstack/zaqar: Not permitted to delete pools which are used by flavor  https://review.openstack.org/11770607:20
*** jeffrey4l has joined #openstack-zaqar07:27
*** AAzza_afk is now known as AAzza07:51
wpfflaper87:   https://review.openstack.org/#/c/117706/ ,  again ,  :P07:53
*** jeffrey4l has quit IRC08:55
*** jeffrey4l has joined #openstack-zaqar09:11
openstackgerritJeffrey Zhang proposed a change to openstack/python-zaqarclient: Fix the help string for queue in cli  https://review.openstack.org/12073509:34
*** jeffrey4l has quit IRC09:38
*** jeffrey4l has joined #openstack-zaqar09:50
*** jeffrey4l has quit IRC10:08
*** prashanthr_ has joined #openstack-zaqar10:12
*** jeffrey4l has joined #openstack-zaqar10:20
*** flwang1 has joined #openstack-zaqar10:27
*** vkmc has joined #openstack-zaqar10:36
vkmcmorning :)10:38
openstackgerritJeffrey Zhang proposed a change to openstack/python-zaqarclient: Fix the help string for queue in cli  https://review.openstack.org/12073510:51
flaper87vkmc: :)11:03
vkmcflaper87, hi o/11:05
flaper87vkmc: I just sent another email on that thread. Mind reading?11:14
flaper87I'd like to know what you think11:14
vkmcflaper87, sure thing11:15
flaper87vkmc: thank you :)11:16
flaper87vkmc: how are you doing? btw11:16
flaper87(didn't mean to be rude)11:16
vkmcflaper87, haha np11:19
vkmcflaper87, I'm doing ok, bit sleepy though11:20
vkmcI was going to reply to that thread, or the first one... but TBH I didn't know who to reply first11:21
flaper87I'd really prefer the discussion to focus on the second one11:22
vkmcflwang1, around? :)11:22
flaper87The current concern is suppose to be discussed there11:22
vkmcflaper87, yeah me too... the first one is quite confusing right now11:22
flaper87just ignore it11:23
vkmcalready did11:25
flaper87So, since January, SQS has dead letter queue: http://aws.amazon.com/blogs/aws/amazon-sqs-new-dead-letter-queue/11:25
vkmcgreat email flaper8711:26
vkmcI think it shed some light over most of the concerns11:26
* flaper87 is becoming really paranoid about this emailing process11:27
vkmcjust one thing that let me thinking yesterday11:27
vkmcand now I saw you brought it up in your email11:27
vkmcwhat are the Zaqar features that keep us away from being considered queue?11:27
flaper87vkmc: get-message-by-id is one of them11:28
vkmcyeah, that is clear11:28
flaper87TBH, I kinda think it's the only one11:28
flaper87:P11:28
vkmcbut besides of that11:28
vkmclol11:28
flaper87As gordon said, there's no real difference11:28
flaper87messaging is just a bit more generic11:28
vkmcthere is where I wanted to arrive11:28
vkmcthey don't like the fact that Zaqar behave as a queue but we are defending that we are a messages service11:29
flaper87right, which doesn't mean we should remove all the other things11:29
vkmceveryone is like 'oh but you mentioned prod/cons, then you are a queue!'11:29
vkmcabout SQS dead letter queue, good stuff!11:57
*** flwang2 has joined #openstack-zaqar12:01
*** flwang1 has quit IRC12:02
*** cpallares has joined #openstack-zaqar12:02
flaper87vkmc: btw, I responded to your comments in gerrit12:17
vkmcflaper87, thanks12:18
vkmcflaper87, btw could you reproduce https://review.openstack.org/#/c/119900/?12:18
vkmcAAzza couldn't yesterday12:18
vkmcI'm debugging the server12:19
vkmcflaper87, oh and I replied too12:20
flaper87ah, erm...12:20
* flaper87 silently goes away and reads12:20
*** jeffrey4l has quit IRC12:30
*** jeffrey4l has joined #openstack-zaqar12:44
vkmcflaper87, do you know if someone in Glance is interested in mentoring for the next OPW round?12:56
flaper87vkmc: I'm not sure :/13:00
flaper87I'd like to mentor for Zaqar13:00
flaper87I think I've a project idea already13:01
vkmcthat's so great :)13:01
*** flwang2 has quit IRC13:03
vkmcwell, when you have a moment please update the wiki with the project you have in mind13:04
vkmcso applicants start making up their minds13:05
vkmcright now we have two interested applicants, one in Keystone and one in Glance13:05
vkmcand we don't have mentors for those projects :/13:05
vkmcI started reaching out former mentors13:05
flaper87vkmc: what was the link again?13:05
vkmchttps://wiki.openstack.org/wiki/OutreachProgramForWomen13:14
vkmcflaper87, ^13:14
*** sriram has joined #openstack-zaqar13:14
vkmcmore precisely, https://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas13:14
* flaper87 adds something13:20
*** jchai has joined #openstack-zaqar13:21
vkmc:)13:21
vkmcyou rock13:21
vkmciff I get a job13:21
vkmcI'll propose myself as mentor for Zaqar as well13:21
flaper87vkmc: AWESOME!13:22
flaper87vkmc: btw, https://review.openstack.org/#/c/120155/ :D13:22
* flaper87 needs to get kgriffs|afk to review client patches13:22
vkmcflaper87, I'm on it13:22
vkmcfirst I want to debug the claim thing13:23
*** mpanetta has joined #openstack-zaqar13:31
*** earnThis has joined #openstack-zaqar13:52
*** amitgandhinz has joined #openstack-zaqar14:01
*** kgriffs|afk is now known as kgriffs14:08
*** prashanthr_1 has joined #openstack-zaqar14:14
*** prashanthr_ has quit IRC14:14
vkmcflaper87, I'm revisiting the claims_id bug in the client14:22
flaper87vkmc: what's up with that?14:22
flaper87:D14:22
vkmcit's happening because claimed messages has a claim_id14:22
vkmcand that is fine14:22
flaper87it's fine for v1.1 not v114:23
flaper87Are you testing it in your laptop?14:23
vkmcthe odd thing is that the client is trying to create a claimed message as it were a not claimed message14:23
vkmcyeah14:23
vkmccheck line 131 https://review.openstack.org/#/c/119347/3/zaqar/queues/transport/wsgi/v1_0/claims.py14:23
vkmchere we add the claimed_id14:23
vkmcparam14:24
vkmcit's in the URL as well14:24
vkmcso.. we should remove that param in there14:24
vkmcin v1 the claim should be in the URL only14:24
flaper87mmh, but the `message_url` function adds it to the URL14:25
flaper87ah well, yeah14:26
flaper87no wait14:26
flaper87nevermind, you're right14:26
flaper87it needs to be removed manually in the claim code14:26
flaper87as we remove the id14:26
vkmcoh yes, message_url adds it to the url14:27
flaper87to be fair, we could use the _format_message in wsgi/v1/messages.py14:27
flaper87s/use/reuse/14:27
vkmcoh no! I was right in the first time --> path += falcon.to_query_str({'claim_id': claim_id})14:27
vkmcit's adding the field, not changing the url14:27
*** ametts has quit IRC14:27
vkmcpfff14:28
vkmcyeah we could14:28
flaper87cool14:28
vkmcor remove that param14:28
flaper87easy fix, remove the param :)14:28
flaper87re-using _format_message reduces the chance of duplicated bugs14:28
vkmcok, I'll take the red pill and do the second one14:29
AAzzaflaper87: vkmc: i didn't get what is the problem... I want to understand since I was touching the code14:30
vkmcAAzza, hey :)14:32
AAzzathere is no claim_id in the message dict in that file, i checked it. the message-url adds it only to the url, and it was adding before me14:32
AAzzavkmc: hi)14:32
vkmcAAzza, this is the output I got when running the bench mark with one consumer worker http://paste.openstack.org/show/110176/14:32
vkmcAAzza, the first message shows that id has a claim_id param14:32
flaper87AAzza: but the message controller is adding the claim_id14:33
vkmcI guess it's because of line 132 here https://review.openstack.org/#/c/119347/3/zaqar/queues/transport/wsgi/v1_0/claims.py14:33
flaper87and it's returning it through the claim controller back to the API14:33
vkmc^14:33
vkmc:)14:33
AAzzaflaper87: but i tried to delete it in that point. i checked - claim_controller format the messages it returns and do not add the claim_id, let me find that piece of code.14:36
AAzzaorrr... maye some controllers do not format the messages...14:36
AAzzavkmc: do you test on mongo?14:36
*** alcabrera|afk is now known as alcabrera14:36
vkmcAAzza, yep, mongo :)14:37
AAzzavkmc: i do testing on sqla14:37
vkmcoh :o14:37
vkmcprobably it's that14:37
vkmcthis sounds like kgriffs fault14:37
prashanthr_1Good morning all :)14:38
kgriffsvkmc: probably14:38
flaper87mongo's claim driver doesn't format the message14:38
kgriffsprashanthr_1: good evening!14:38
flaper87it gets it right from the message controller14:38
flaper87whereas the sql driver does this https://github.com/openstack/zaqar/blob/master/zaqar/queues/storage/sqlalchemy/claims.py#L4514:38
prashanthr_1Thanks kgriffs.14:38
vkmchuh.. what about redis?14:40
*** jeffrey4l_ has joined #openstack-zaqar14:41
flaper87https://github.com/openstack/zaqar/blob/master/zaqar/queues/storage/redis/models.py#L16514:41
flaper87same thing, it returns the claim_id14:42
openstackgerritJeffrey Zhang proposed a change to openstack/python-zaqarclient: CLI support for queue existence and metadata operations  https://review.openstack.org/12079714:42
flaper87kgriffs: whenever you have time, pleeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeease take a look at the client reviews :D14:42
AAzzaflaper87: i think right fix will be to explicity format message in transport layer, the same we do in messages14:43
AAzzaflaper87: to be sure, that we are not dependent on drivers implementations14:44
vkmc+1 AAzza14:44
flaper87AAzza: +!, that's what I was proposing. We should re-use `_format_message`14:44
vkmcAAzza, want to add this or should I finish it?14:45
*** jeffrey4l has quit IRC14:45
flaper87kgriffs: do we still need that `test_correct_has` test14:47
flaper87?14:47
flaper87I'm kind of tempted to remove it14:47
flaper87if you run tests with changes that have not been commited it normally fails14:47
kgriffsoh.14:47
flaper87and if you run it outside a `git` repo it fails too14:48
flaper87it's probably pbr's fault14:48
flaper87dunno14:48
kgriffsyeah, sometimes I have to recreate when switching branches14:48
kgriffsanyway14:48
kgriffsum14:48
kgriffsconsidering that code is stable and probably won't change for the forseeable future14:48
kgriffsi'm fine with removing the test14:48
flaper87cool14:49
flaper87wait for it14:52
openstackgerritFlavio Percoco proposed a change to openstack/zaqar: Don't import client from the version package  https://review.openstack.org/12080214:52
openstackgerritFlavio Percoco proposed a change to openstack/zaqar: Remove test_correct_has from our test suite  https://review.openstack.org/12080314:52
flaper87BANG!14:52
prashanthr_1kgriffs: I have finished with14:54
prashanthr_1"* Add the ability to configure Sentinel support in zaqar.conf14:54
prashanthr_1* Read that config and use it to construct a Sentinel instance and  discover the master in lieu of instantiating StrictRedis directly."14:54
prashanthr_1can you explain me a bit about "* Test master-slave failover with the above and see if the retry  decorator needs to do anything to find the new slave, or if redis-py  does it automagically."14:55
prashanthr_1I have found out that redis-py does not provide default fallback14:55
prashanthr_1:(14:55
flaper87malini: around?14:56
flaper87ah no, malini is on vacation14:56
flaper87nevermind14:56
flaper87AFAIK14:56
flaper87malini: stay where you are, don't pay attention to me. Trust me, it's better like this14:56
kgriffsprashanthr_1: ok, so what error does redis-py raise when the master fails over to a slave?14:56
prashanthr_1ConnectionError14:56
prashanthr_1as with a default standalone redis14:57
kgriffsand I am assuming the decorator retries?14:57
vkmcAAzza, let me know about the above later :)14:57
prashanthr_1Yes it retries14:57
kgriffsok. TBH I haven't looked at that decorator code very closely yet14:57
kgriffsso, i suppose what it needs to do is rediscover the new master. which means it will need access to the sentinel class instance14:58
kgriffswhat do you think?14:59
prashanthr_1kgriffs: precisely14:59
AAzzavkmc: if you want, you can do it) i would be glad to do it, but I should do many projects for the university - deadlinea are in few weeks although semester is just started :)14:59
prashanthr_1so we need to store a state variable in the driver can say if redis is operating in sentinel or stand alone mode15:00
prashanthr_1if yes we might need to use the sentinel object to retrieve the next slave15:00
vkmcAAzza, ok, no worries! I'm on it :) thanks for helping to debug15:00
prashanthr_1i also had a small question here, in the failover case we need to check for any other slaves and then create a master-slave replication hierarchy in the decorator15:01
prashanthr_1Am i correct here ?15:01
AAzzakgriffs: flaper87: could we discuss later today - probably in few hours -  what are left from api-v1.1-response changes blueprint? So I could finish it tomorrow/on the weekends)15:02
kgriffskk15:02
flaper87AAzza: totally15:05
flaper87thanks :)15:05
prashanthr_1kgriffs: Should we re-establish the master slave hierarchy when we do a failover15:10
prashanthr_1?15:10
prashanthr_1also most slaves operate read-only15:10
prashanthr_1so we must try to change the config in the decorator i guess15:10
*** AAzza is now known as AAzza_afk15:11
*** jeffrey4l_ has quit IRC15:13
kgriffsback15:15
kgriffsprashanthr_1: not sure I understand the question15:16
kgriffslet me pull up sentinel docs15:16
kgriffsok, found this "If a master is not working as expected, Sentinel can start a failover process where a slave is promoted to master, the other additional slaves are reconfigured to use the new master, and the applications using the Redis server informed about the new address to use when connecting."15:17
kgriffsso, if sentinel is enabled15:18
kgriffsisn't it as simple as calling sentinel.discover_master in the decorator before retrying the operation?15:18
kgriffsoops15:19
kgriffsI mean sentinel.master_for15:19
kgriffsbtw, if you aren't already, it would be good log a warning when this happens15:19
kgriffsflaper87: btw, saw your note about epel serving redis 2.415:21
prashanthr_1Ohh okay. I will look into this kgriffs.15:21
kgriffsflaper87: were you going to follow up with the package maintainer?15:21
flaper87kgriffs: look who's the maintainer now: https://admin.fedoraproject.org/pkgdb/15:21
flaper87erm https://admin.fedoraproject.org/pkgdb/package/redis/15:22
* kgriffs looks15:22
kgriffscrap15:22
flaper87;)15:22
kgriffsnow it's *never* going to get done15:22
flaper87that's why I asked someone else to do it :P15:22
flaper87btw, el7 will get 2.815:23
flaper87el6 ain't going to be updated15:23
kgriffsgtk15:23
kgriffsno ZSCAN love for el6 then15:24
flaper87I wouldn't worry much about el, TBH.15:24
flaper87is ZSCAN in 2.6 ?15:25
flaper87el6*15:25
kgriffs2.815:25
flaper87doh, ok15:25
kgriffsnot sure what else landed in 2.8 - that was just first thing I thought of15:26
*** reed has joined #openstack-zaqar15:26
kgriffsI heard it on this radio show. "Random techie trivia to win friends and influence people"15:26
* kgriffs winks15:27
*** prashanthr_1 has quit IRC15:36
*** prashanthr_ has joined #openstack-zaqar15:36
openstackgerritA change was merged to openstack/zaqar: Updated from global requirements  https://review.openstack.org/12033015:41
*** jimhoagland has joined #openstack-zaqar15:42
flaper87LOL15:44
flaper87kgriffs: "Any resemblance to reality is purely a coincidence"15:44
*** jimhoagland has left #openstack-zaqar15:45
prashanthr_kgriffs: We can use discover_master on the sentinel to obtain the next master15:50
prashanthr_:)15:50
kgriffskewl15:52
earnThishey guys, any idea why im getting this error when i switch branches to my previos patch and run tox?  All im going is git review -d "117574" to pick up where i left off then running tox, the branch previously passed the tests http://paste.openstack.org/show/110196/15:57
earnThisim sure im missing somethign obvious15:57
flaper87earnThis: it's not your fault16:00
flaper87earnThis: this fill fix that error: https://review.openstack.org/#/c/120803/16:00
flaper87it's a test we have that requires you to have a clean git workspace16:00
flaper87that thing is used for production environments16:00
vkmcthe problem is that he has tox 1.7.216:01
flaper87?16:02
earnThisvkmc: i have 1.6.1 now16:02
flaper87vkmc: open the paste :P16:02
vkmcand probably in the other branch he has .tox env with that version16:02
vkmcflaper87, yeah Fla, I already look at it16:02
vkmcit's an old bug heh16:02
flaper87mmh, wait because this paste is different from the one I saw the other day16:03
vkmcthis -> File "tests/unit/test_version.py", line 34, in test_correct_hash16:03
flaper87that test that is failing is not because of tox16:03
vkmcis tox fault16:03
flaper87mmh, nope16:04
flaper87I can make that test fail without tos16:04
flaper87tox16:04
flaper87the reason it is failing is because it requires a clean working copy16:04
earnThisthat sounds righ16:05
earnThisright*16:05
vkmcit does yeap16:05
earnThiswhat can i do16:06
flaper87earnThis: review the patch :D16:06
flaper87earnThis: ignore the failure16:06
flaper87earnThis: or commit everything locally and re-run the test16:06
*** prashanthr_ has quit IRC16:08
*** prashanthr_1 has joined #openstack-zaqar16:08
vkmcflaper87, http://paste.openstack.org/show/110201/16:08
flaper87vkmc: ohhhhhhhhhhhhhh now I understand what you meant16:08
flaper87I'm sorry16:09
flaper87although, that bug is not really related to tox, it's pbr version discovery thingy failing misserably :(16:09
vkmcearnThis, I think that rm -rf .tox/ should do the trick16:10
*** prashanthr_ has joined #openstack-zaqar16:10
vkmcflaper87, yeah I didn't asked what it was about that time.. so I blame tox ;p16:10
vkmcso it's pbr messing with us16:10
*** prashanthr_1 has quit IRC16:12
vkmcflaper87, you owe me a gummybear16:12
* vkmc hides16:12
earnThishttp://paste.openstack.org/show/110203/16:15
flaper87vkmc: you should've asked 10 mins ago, I just finished this week's bag :(16:15
flaper87I'm sorry16:15
flaper87and I still have friday ahead16:15
flaper87damnit16:15
flaper87earnThis: you seriously can't blame zaqar for that :P16:15
earnThishahah wasn't at all16:16
*** Guest96101 is now known as sebasmagri16:18
flaper87vkmc: if you review those 2 patches that I submitted like 30mins ago we can get rid of that issue forever16:18
*** sebasmagri has quit IRC16:18
*** sebasmagri has joined #openstack-zaqar16:18
*** sebasmagri has joined #openstack-zaqar16:18
flaper87and I'll bring gummy bears to paris16:18
vkmcok... I'm updating my bet to TWO gummybears16:19
vkmcor I won't review those patches16:19
flaper87vkmc: 1 full bag because you rock16:19
vkmc:D16:20
vkmcreviewed16:20
* kgriffs observes the blatant corruption of the OS community as demonstrated by rampant bribery16:21
flaper87vkmc: you'll have to review https://review.openstack.org/#/c/120802/1 to get the other one merged16:21
flaper871 bag + 1 gummy bear for that16:21
flaper87and don't tell kgriffs16:21
vkmcdone16:21
vkmckgriffs, you didn't see nothing16:21
* kgriffs didn't see nothin'16:22
vkmcyou know nothing John Snow16:22
flaper87kgriffs: client client client16:22
flaper87there's a client release freeze on the 18th16:22
flaper87:D16:22
kgriffsoic16:23
vkmcflaper87, btw, using format_messages in the claim_id bug didn't work16:45
vkmcI'm uploading a possible fix, but it's not fancy16:45
prashanthr_kgriffs: I am almost done with the patch will submit it early tmrw :)16:46
kgriffssounds good, thanks!16:46
*** prashanthr_ has quit IRC16:46
*** alcabrera is now known as alcabrera|afk16:47
flaper87vkmc: mmh, why didn't it work?16:50
flaper87that's weird16:50
openstackgerritA change was merged to openstack/zaqar: Don't import client from the version package  https://review.openstack.org/12080216:50
openstackgerritA change was merged to openstack/zaqar: Remove test_correct_has from our test suite  https://review.openstack.org/12080316:51
flaper87vkmc: I think there are 2 format_messages, 1 in the storage and 1 in the transport16:51
vkmcflaper87, I was using the one in transport16:51
vkmcthe claim_id field is still there because it only formats the style16:51
vkmcnothing else16:51
vkmcso... I had to delete it16:51
flaper87mmmh16:52
vkmcI'll think in another solution though16:52
flaper87what do you mean it it only formats the style?16:52
vkmcforget that phrase haha16:53
vkmcthe format_message only modifies some of the fields, but claim_id is still there16:54
vkmcbrb16:54
vkmcI'll expland better soon16:54
flaper87ok16:54
flaper87I'm not understanding :P16:54
flaper87https://github.com/openstack/zaqar/blob/master/zaqar/queues/transport/wsgi/v1_0/messages.py#L31316:54
flaper87I mean, that should return a dict w/o claim_id16:55
*** jchai is now known as jchai_afk17:01
*** jchai_afk is now known as jchai17:04
vkmcback17:37
vkmcflaper87, yeah sorry for the confusion17:37
vkmcI not sure what happens precisely, I'm trying to understand17:38
*** openstackgerrit has quit IRC17:46
flaper87vkmc: did you change both methods ?17:47
flaper87vkmc: I mean `on_get` for the claim resource and `on_post` for the collection ?17:47
flaper87both methods return messages17:47
*** openstackgerrit has joined #openstack-zaqar17:47
flaper87and both messages need to be normalized17:47
*** alcabrera|afk is now known as alcabrera17:47
vkmcflaper87, yeah17:49
vkmcnow it's failing the client17:49
vkmcbecause apparently there is no href field17:49
vkmcthat is what confused me in the first place17:49
vkmchttp://paste.openstack.org/show/110256/17:50
flaper87that's weird, may I see the changes you did?17:50
flaper87It's not that I don't trust what you're doing, btw. I just want to wrap my head around the problem17:51
flaper87git diff should be enough17:51
vkmck17:53
vkmcI could upload it as WIP17:54
vkmcso it's easier for you17:54
flaper87sure, that works too17:54
vkmchttp://paste.openstack.org/show/110257/17:54
vkmcok :)17:54
flaper87vkmc: question: Shouldn't the claim_id still be in the URL ?17:57
vkmcit should17:58
vkmcbut besides of that, the href field should be there17:59
flaper87right17:59
flaper87sorry, I just happened to notice that17:59
* flaper87 got confused17:59
* flaper87 STFU and keeps reading17:59
vkmcits ok :)17:59
flaper87wait, I know what's going on18:00
flaper87that for loop18:00
flaper87you're not modifying the `msg` dict in `resp_msgs`18:00
flaper87you're just re-assigning `msg`18:00
flaper87you may want to use a generator or a list comprehension there18:01
flaper87or msg.update(..format_message())18:01
flaper87and then del msg['claim_id']18:01
flaper87but that would be silly18:01
flaper87so, I'd probably go with the list comprehension18:02
flaper87vkmc: https://github.com/openstack/zaqar/blob/master/zaqar/queues/transport/wsgi/v1_0/messages.py#L6918:02
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Removes claim_id param in v1.0  https://review.openstack.org/12086718:02
vkmcoh18:02
flaper87that's a python gotcha, FWIW18:03
* flaper87 has been there18:03
vkmclol18:04
vkmcso...18:04
vkmc(recalculando)18:04
flaper87LOL18:05
vkmcwhich for loop were you talking about?18:06
flaper87both, I'll comment on the review18:06
vkmclol k18:06
vkmcI think I know18:06
flaper87vkmc: done18:08
flaper87(and remember the cid :P )18:08
flaper87ok, brb18:09
flaper87hope that helps18:09
vkmc:D18:09
*** kgriffs is now known as kgriffs|afk18:18
*** echevemaster has joined #openstack-zaqar18:19
openstackgerritGriffin Ashe proposed a change to openstack/zaqar: Add _ prefix to local variables  https://review.openstack.org/11757418:20
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Removes claim_id param in v1.0  https://review.openstack.org/12086718:24
vkmcflaper87, yay it worked!18:26
vkmcpython gotchas are new for me :x18:26
vkmcalthough that loops seemed suspicious18:27
*** mpanetta has quit IRC18:34
*** sgotliv has quit IRC18:48
*** mpanetta has joined #openstack-zaqar18:51
*** kgriffs|afk is now known as kgriffs19:06
vkmcbbl19:07
*** kgriffs is now known as kgriffs|afk19:17
*** flwang1 has joined #openstack-zaqar19:23
*** amitgandhinz has quit IRC19:26
*** mpanetta has quit IRC19:26
*** echevemaster has quit IRC19:50
*** earnThis is now known as earnThis|afk19:51
*** yograterol has joined #openstack-zaqar20:03
*** kgriffs|afk is now known as kgriffs20:04
*** echevemaster has joined #openstack-zaqar20:06
*** flwang1 has quit IRC20:08
*** kgriffs is now known as kgriffs|afk20:13
*** echevemaster has quit IRC20:14
*** flaper87 is now known as flaper87|afk20:24
openstackgerritClark Boylan proposed a change to openstack/zaqar: Workaround pypy bug on trusty when running tests  https://review.openstack.org/12090620:40
*** alcabrera is now known as alcabrera|afk21:05
*** kgriffs|afk is now known as kgriffs21:05
*** yograterol has quit IRC21:49
*** alcabrera|afk is now known as alcabrera21:49
*** jchai has quit IRC21:52
*** sriram has quit IRC21:55
*** yograterol has joined #openstack-zaqar22:03
*** earnThis|afk has quit IRC22:08
*** sgotliv has joined #openstack-zaqar22:12
*** openstackgerrit has quit IRC22:38
*** openstackgerrit_ has joined #openstack-zaqar22:38
*** openstackgerrit_ is now known as openstackgerrit22:40
*** cpallares has quit IRC23:04
*** boris-42 has joined #openstack-zaqar23:38
*** sriram1 has joined #openstack-zaqar23:41
*** flwang1 has joined #openstack-zaqar23:43
*** jeffrey4l_ has joined #openstack-zaqar23:55
*** kgriffs is now known as kgriffs|afk23:55
*** yograterol has quit IRC23:57

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