Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Nov 29, 2023

This is an automatic backport of pull request #9996 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

of a certain structure reported in #9803.

Closes #9991.

(cherry picked from commit f14bd15)
(cherry picked from commit 0c742bb)
@michaelklishin michaelklishin added this to the 3.11.27 milestone Nov 29, 2023
@michaelklishin michaelklishin merged commit 380fda1 into v3.11.x Nov 29, 2023
@michaelklishin michaelklishin deleted the mergify/bp/v3.11.x/pr-9996 branch November 29, 2023 04:06
@mohanrajanna15
Copy link

I want to make sure, that the fix to this will ignore closing connection TCP socket whatever and prints what the message was?

@mohanrajanna15
Copy link

[process question] Helloo Team,

How can we speed up the fix and have it delivered quickly cause this is us causing a tremendous business impact to our customers?
we do not have an official professional services contract with RabbitMQ. Will that make a difference
any information on this will be very helpful.. TIA.

@michaelklishin
Copy link
Collaborator

@mohanrajanna15 I find it ironic that a non-paying user is pushing us to produce a release urgently because your customers are affected

@michaelklishin
Copy link
Collaborator

@mohanrajanna15
Copy link

@michaelklishin Apologies, we will work on how to engage you all on a professional contract very soon. Along that line do you know if this fix will be part of 3.12.x and 3.13.x as well and any ETA on when those versions will be released?

@michaelklishin
Copy link
Collaborator

Take a look at the milestone and the backport labels on a pull request of interest. Everything that's in v3.11.x is almost always also in v3.12.x and in main.

@michaelklishin
Copy link
Collaborator

In this PR specifically, there is a link to #9996 which has a milestone set and a link to another PR for main.

Our team does not make ETA promises.

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.

3 participants