txamqp.protocol.AMQClient does not use the clock passed as an arg as the LoopingCall clock
Bug #996614 reported by
cyli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
txAMQP |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm not entirely sure if this is a bug or if this was intended, but it seems like the clock that is passed in and used as the clock to check the heartbeat should be the same clock used to make the heartbeat.
clock.callLater is used, but LoopingCall is also used, without setting the clock of the looping call.
Also, this is not in the patch, but time.time() is used for the last heartbeat received and last heartbeat sent - if the actual seconds since the epoch don't need to be used, reactor/
Changed in txamqp: | |
status: | New → Fix Released |
To post a comment you must log in.