Skip to content

[Parent] Broker ACK/ReasonCode scenario mapping audit and fixes #1733

Description

@robustmq

Background

We need a full broker-side audit to ensure every ACK/ReasonCode path returns the correct code for the actual runtime scenario.

Goal

Create one parent tracking task for protocol reason-code completeness, and execute focused audits in child tasks.

Scope

  • Verify scenario -> reason-code mapping is correct (not only enum completeness)
  • For incorrect mappings: fix broker logic and return code behavior
  • Add/adjust tests for each corrected path

Target Protocol Areas

  • CONNECT/CONNACK
  • DISCONNECT
  • PUBACK/PUBREC/PUBREL/PUBCOMP
  • SUBACK
  • UNSUBACK

Child Tasks

  • Connector path audit and fixes
  • Publish path audit and fixes
  • Subscribe/Unsubscribe path audit and fixes

Done Criteria

  • All identified mismatches are fixed
  • Tests cover corrected mappings
  • Parent task links all child tasks and tracks completion

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions