Skip to content

Conversation

@hazel-bohon
Copy link

@hazel-bohon hazel-bohon commented Oct 1, 2025

No description provided.

@hazel-bohon hazel-bohon changed the title Added IMarshalMessages interface. Add IMarshalMessages interface Oct 1, 2025
@hazel-bohon hazel-bohon changed the title Add IMarshalMessages interface [Spike] Add IMarshalMessages interface Oct 2, 2025
@github-actions

This comment was marked as off-topic.

@github-actions github-actions bot added the stale label Nov 3, 2025
@github-actions github-actions bot closed this Nov 11, 2025
@github-actions github-actions bot deleted the CloudEvents branch November 11, 2025 00:10
@mauroservienti mauroservienti restored the CloudEvents branch November 24, 2025 12:50
@mauroservienti mauroservienti changed the title [Spike] Add IMarshalMessages interface Introduce incoming message support for envelope unwrapping Nov 24, 2025
mauroservienti added a commit to Particular/NServiceBus.Envelope.CloudEvents that referenced this pull request Nov 27, 2025
mauroservienti added a commit to Particular/NServiceBus.Envelope.CloudEvents that referenced this pull request Nov 27, 2025
# Conflicts:
#	src/NServiceBus.Core/Receiving/ReceiveComponent.cs
Comment on lines +259 to +264
if (exception != null)
{
meterTags.Add(new KeyValuePair<string, object?>(MeterTags.ErrorType, exception.GetType().FullName));
}

totalEnvelopeUnwrappingErrors.Add(succeeded ? 0 : 1, meterTags);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the scenario for the exception not null and succeeded true?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't be such a scenario, but I didn't want to decide the metric value based on the exception and wanted to make it explicit.

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.

4 participants