Skip to content

[Feature]: PushMessage ACK #47

Closed

Description

@antoineatstariongroup

What type of issue is this?

  • Bug report
  • Feature request

Prerequisites

  • I have written a descriptive issue title
  • I have verified that I am running the latest version of the Mercurio
  • I have searched open and closed issues to ensure it has not already been reported

Description

For resilient system, having the ACK that the RabbitMQ received the message is crucial.
Currently, PushMessage is fire&Forget design.
We shall provide clear distinction between the 2 options.

This involve changes on the channel creation and pushMessage shall return a boolean. If the fire&forget is used, the return value will always be true

Steps to Reproduce

System Configuration

  • Mercurio version:
    • Mercurio:
    • Other:
  • Environment (Operating system, version and so on):
  • .NET Framework version:
  • Additional information:

Activity

  1. added a commit that references this issue on Sep 2, 2026
    de56f5c
  2. linked a pull request that will close this issueFix #47: publish with ACK #48on Sep 2, 2026
  3. added a commit that references this issue on Sep 4, 2026
    8dd5992
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions