Skip to content

Fix #45 - #46

Merged
antoineatstariongroup merged 3 commits into
developmentfrom
45-bug-impossible-to-be-notified-when-an-invalid-message-is-received-hosted-case
Sep 2, 2026
Merged

antoineatstariongroup merged 3 commits into
developmentfrom
45-bug-impossible-to-be-notified-when-an-invalid-message-is-received-hosted-case

Conversation

@antoineatstariongroup

Copy link
Copy Markdown
Contributor

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the Mercurio code style guidelines
  • I have provided test coverage for my change (where applicable)

Description

Fix #45

Resolves silent deserialization failure

@sonarqubecloud

sonarqubecloud Bot commented Sep 2, 2026

Copy link
Copy Markdown

@antoineatstariongroup
antoineatstariongroup merged commit e02b6b6 into development Sep 2, 2026
3 of 4 checks passed
@antoineatstariongroup
antoineatstariongroup deleted the 45-bug-impossible-to-be-notified-when-an-invalid-message-is-received-hosted-case branch September 2, 2026 08:41
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.

[Bug]: Impossible to be notified when an invalid message is received (Hosted case)

1 participant