Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track requeue history (backport #12506) #12507

Merged
merged 4 commits into from
Oct 11, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Oct 11, 2024

Track requeue history

Support tracking the requeue history as described in rabbitmq/rabbitmq-website#2095

This commit:

  1. adds a test case tracing the requeue history via AMQP 1.0 using the modified outcome and
  2. fixes bugs in the broker which crashed if a modified message annotation value is an AMQP 1.0 list, map, or array.

Complex modified annotation values (list, map, array) are stored as tagged values from now on.
This means AMQP 0.9.1 consumers will not receive modified annotations of
type list, map, or array (which is okay).


This is an automatic backport of pull request #12506 done by [Mergify](https://mergify.com).

ansd added 4 commits October 11, 2024 13:51
Support tracking the requeue history as described in
rabbitmq/rabbitmq-website#2095

This commit:
1. adds a test case tracing the requeue history via AMQP 1.0
   using the modified outcome and
2. fixes bugs in the broker which crashed if a modified message
   annotation value is an AMQP 1.0 list, map, or array.

Complex modified annotation values (list, map, array) are stored as tagged values from now on.
This means AMQP 0.9.1 consumers will not receive modified annotations of
type list, map, or array (which is okay).

(cherry picked from commit e6818f0)
Test the use case described in
rabbitmq/rabbitmq-website#2095

(cherry picked from commit 855a32a)
Test the use case described in rabbitmq/rabbitmq-website#2095:

> Rather than relying solely on RabbitMQ's built-in dead lettering tracking via x-opt-deaths,
consumers can customise dead lettering event tracking.

(cherry picked from commit 2e90619)
@mergify mergify bot assigned ansd Oct 11, 2024
@ansd ansd added this to the 4.0.3 milestone Oct 11, 2024
@michaelklishin michaelklishin merged commit 2292638 into v4.0.x Oct 11, 2024
290 of 291 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.0.x/pr-12506 branch October 11, 2024 15:30
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.

2 participants