| *** apetrich has quit IRC | 03:15 | |
| *** jtomasek has joined #openstack-mistral | 06:16 | |
| *** quiquell|off is now known as quiquell | 07:08 | |
| *** pgaxatte has joined #openstack-mistral | 07:16 | |
| *** quiquell is now known as quiquell|brb | 07:35 | |
| *** apetrich has joined #openstack-mistral | 07:43 | |
| *** quiquell|brb is now known as quiquell | 08:07 | |
| *** akovi has joined #openstack-mistral | 08:15 | |
| *** jtomasek has quit IRC | 08:20 | |
| *** pgaxatte has quit IRC | 09:10 | |
| *** pgaxatte has joined #openstack-mistral | 09:12 | |
| vgvoleg_ | Hi all | 11:56 |
|---|---|---|
| vgvoleg_ | Can anyone help me? I've got interesting situation, and I have no ideas what's wrong | 11:57 |
| vgvoleg_ | I am using notifier and got situation when notifies was delivered in wrong order | 12:00 |
| vgvoleg_ | `Recieved RPC request` message are in correct order, but `Message delivered` are placed not correct | 12:02 |
| vgvoleg_ | requests.post is sync, isn't it? | 12:03 |
| vgvoleg_ | please any ideas, I am stucked with this behavior :( | 12:03 |
| *** jtomasek has joined #openstack-mistral | 12:05 | |
| *** mmethot has quit IRC | 12:15 | |
| vgvoleg_ | maybe monkey patch changed something inside the requests library | 12:21 |
| vgvoleg_ | I don't understand how it works, but hope any of you do | 12:22 |
| *** apetrich has quit IRC | 12:30 | |
| rakhmerov | vgvoleg_: hi | 12:31 |
| rakhmerov | I don't think that many people use this functionality | 12:31 |
| *** apetrich has joined #openstack-mistral | 12:31 | |
| rakhmerov | we've never recommended to use it in production because it still has gaps | 12:32 |
| vgvoleg_ | could monkey patch make sync requests.post async? | 12:32 |
| rakhmerov | I don't think so | 12:33 |
| rakhmerov | monkey patching aims to do a different thing | 12:34 |
| rakhmerov | well.. theoretically, it can have the same consequence though | 12:35 |
| rakhmerov | monkey patching inserts calls to a green thread dispatcher | 12:36 |
| rakhmerov | so may be when we do requests.post it switches to a different thread immediately after it w/o waiting for a reply in a sync manner | 12:36 |
| rakhmerov | and when it switches to another thread it also does requests.post | 12:37 |
| rakhmerov | so two requests have been sent now | 12:37 |
| rakhmerov | and which comes first to a receiver is not really defined | 12:37 |
| rakhmerov | nobody can guarantee the order here | 12:38 |
| *** apetrich has quit IRC | 12:38 | |
| rakhmerov | vgvoleg_: this is only my guess but IMO sounds like a realistic scenario | 12:38 |
| vgvoleg_ | so the possible WA is not to patch socket? | 12:39 |
| *** apetrich has joined #openstack-mistral | 12:56 | |
| *** quiquell is now known as quiquell|lunch | 13:16 | |
| *** quiquell|lunch is now known as quiquell | 13:39 | |
| *** akovi has quit IRC | 14:00 | |
| *** mmethot has joined #openstack-mistral | 14:05 | |
| *** akovi has joined #openstack-mistral | 14:34 | |
| *** pgaxatte has quit IRC | 15:43 | |
| *** akovi has quit IRC | 15:56 | |
| *** akovi has joined #openstack-mistral | 15:57 | |
| *** akovi has quit IRC | 16:01 | |
| *** akovi has joined #openstack-mistral | 16:07 | |
| *** akovi has quit IRC | 16:10 | |
| *** quiquell is now known as quiquell|off | 16:37 | |
| *** quiquell|off is now known as quiquell | 16:45 | |
| *** quiquell is now known as quiquell|off | 17:00 | |
| *** jistr|sick is now known as jistr | 17:14 | |
| *** vgvoleg_ has quit IRC | 20:10 | |
| *** mmethot has quit IRC | 22:34 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!