Skip to content

fix: properly cancel token passed to AsyncEventingBasicConsumer receiver - #1789

Closed
Andersso wants to merge 1 commit into
rabbitmq:mainfrom
Andersso:fix-consumer-token-cancel-on-close
Closed

fix: properly cancel token passed to AsyncEventingBasicConsumer receiver#1789
Andersso wants to merge 1 commit into
rabbitmq:mainfrom
Andersso:fix-consumer-token-cancel-on-close

Conversation

@Andersso

Copy link
Copy Markdown

@lukebakken
lukebakken self-requested a review February 21, 2025 15:44
@lukebakken lukebakken self-assigned this Feb 21, 2025
@lukebakken lukebakken added this to the 7.1.1 milestone Feb 21, 2025
Comment thread projects/RabbitMQ.Client/Impl/AutorecoveringChannel.cs Outdated
@lukebakken lukebakken modified the milestones: 7.1.1, 7.2.0 Feb 24, 2025
@danielmarbach

Copy link
Copy Markdown
Collaborator

I started something similar a while ago https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/1740/files but never got the chance to fully follow through yet

@lukebakken
lukebakken force-pushed the fix-consumer-token-cancel-on-close branch from 73064d2 to 3565e17 Compare August 19, 2025 01:27
@lukebakken

Copy link
Copy Markdown
Collaborator

Thanks everyone. I've made some changes if you'd like to look at this again. I'm hoping to get 7.2.0 out this week.

@danielmarbach

Copy link
Copy Markdown
Collaborator

@lukebakken did you have a chance to look at the PR I started? By floating through the token into the args I think it wouldn't be necessary to expose the channel token on the interface

Comment thread projects/RabbitMQ.Client/Impl/Channel.cs
@lukebakken

Copy link
Copy Markdown
Collaborator

Closing in favor of #1740

@lukebakken lukebakken closed this Aug 19, 2025
@lukebakken lukebakken removed this from the 7.2.0 milestone Aug 19, 2025
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.

5 participants