02a3a39814
It appears the the callback variable that was being called on future done was not the right one, due to the lambda capture mechanism referring to a lazy variable which would potentially be a different callback by the time the future would finish so make sure we capture the right one and ensure the future has access to it. This adds a helper method that submission will go through to ensure that the callback variable is correctly captured in the created lambda and also ensures that the incomplete futures list is cleaned up (when the future is done). The notification listener tests use now eventlet to show up this issue that doesn't occur with blocking executor. Closes-bug: #1474943 Closes-bug: #1475307 Change-Id: I23e393d504662532572b5b344b87387be6d7bcb1
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: http://docs.openstack.org/developer/oslo.messaging
- Source: http://git.openstack.org/cgit/openstack/oslo.messaging
- Bugs: http://bugs.launchpad.net/oslo.messaging