Activity log for bug #1531148

Date Who What changed Old value New value Message
2016-01-05 12:36:28 javeme bug added bug
2016-01-05 12:37:12 javeme description When sending a basic.publish, as the doc says[1]: "The value of the expiration field describes the TTL period in milliseconds", but kombu has already made a conversion from seconds to milliseconds[2], so we do not need to do it again in oslo_messaging/_drivers/impl_rabbit.py[3]. [1]: http://www.rabbitmq.com/ttl.html#per-message-ttl [2]: https://github.com/celery/kombu/blob/master/kombu/messaging.py#L152 https://github.com/celery/kombu/blob/master/kombu/messaging.py#L169 [3]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/ _drivers/impl_rabbit.py#L983 When sending a basic.publish, as the doc says[1]: "The value of the expiration field describes the TTL period in milliseconds", but kombu has already made a conversion from seconds to milliseconds[2], so we do not need to do it again in oslo_messaging/_drivers/impl_rabbit.py[3]. [1]: http://www.rabbitmq.com/ttl.html#per-message-ttl [2]: https://github.com/celery/kombu/blob/master/kombu/messaging.py#L152      https://github.com/celery/kombu/blob/master/kombu/messaging.py#L169 [3]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/      _drivers/impl_rabbit.py#L983
2016-01-05 12:39:09 javeme description When sending a basic.publish, as the doc says[1]: "The value of the expiration field describes the TTL period in milliseconds", but kombu has already made a conversion from seconds to milliseconds[2], so we do not need to do it again in oslo_messaging/_drivers/impl_rabbit.py[3]. [1]: http://www.rabbitmq.com/ttl.html#per-message-ttl [2]: https://github.com/celery/kombu/blob/master/kombu/messaging.py#L152      https://github.com/celery/kombu/blob/master/kombu/messaging.py#L169 [3]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/      _drivers/impl_rabbit.py#L983 When sending a basic.publish, as the doc says[1]: "The value of the expiration field describes the TTL period in milliseconds", but kombu has already made a conversion from seconds to milliseconds[2], so we do not need to do it again in oslo_messaging/_drivers/impl_rabbit.py[3]. [1]: http://www.rabbitmq.com/ttl.html#per-message-ttl [2]: https://github.com/celery/kombu/blob/master/kombu/messaging.py#L152      https://github.com/celery/kombu/blob/master/kombu/messaging.py#L169 [3]: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/_drivers/impl_rabbit.py#L983
2016-01-05 12:39:55 OpenStack Infra oslo.messaging: status New In Progress
2016-01-05 12:39:55 OpenStack Infra oslo.messaging: assignee javeme (javaloveme)
2016-01-07 10:28:24 OpenStack Infra oslo.messaging: status In Progress Fix Released
2016-01-14 18:41:51 OpenStack Infra tags in-stable-liberty