Skip to content

Consumer channel replacement fixes - #433

Closed
michaelklishin wants to merge 1 commit into
mainfrom
fix-cancelled-consumer-recovery
Closed

michaelklishin wants to merge 1 commit into
mainfrom
fix-cancelled-consumer-recovery

Conversation

@michaelklishin

Copy link
Copy Markdown
Member
  • Publishing no longer breaks after a replacement: the publisher held on to the old channel and exchange, now it is redeclared with them
  • Closing a channel the server has already closed is now idempotent
  • Give running handlers a graceul timeout before the work pool is killed
  • Acknowledgements go to the channel the deliveryy has arrived on
  • Handle stale delivery tags better
  • The cancellation callback captures the channel the consumer subscribed on

In addition, this ports a few eventual matchers (such as await_condition/2) from RabbitMQ's CT helpers and adopts them to reduce test flakiness.

Plus fixes timeouts that are at risk of being too short.

 * Publishing no longer breaks after a replacement: the publisher held on
   to the old channel and exchange, now it is redeclared with them
 * Closing a channel the server has already closed is now idempotent
 * Give running handlers a graceul timeout before the work pool is killed
 * Acknowledgements go to the channel the deliveryy has arrived on
 * Handle stale delivery tags better
 * The cancellation callback captures the channel the consumer subscribed on

In addition, this ports a few eventual matchers (such as `await_condition/2`)
from RabbitMQ's CT helpers and adopts them to reduce test flakiness.

Plus fixes timeouts that are at risk of being too short.
@michaelklishin michaelklishin added this to the 2.0.0 milestone Aug 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant