-
Notifications
You must be signed in to change notification settings - Fork 649
Introduce incoming message support for envelope unwrapping #7422
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
base: master
Are you sure you want to change the base?
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
883a7a4 to
9f82a75
Compare
9b71ba2 to
a8b908e
Compare
# Conflicts: # src/NServiceBus.Core/Receiving/ReceiveComponent.cs
a62cd95 to
a48da28
Compare
Removing CanUnwrap API
| if (exception != null) | ||
| { | ||
| meterTags.Add(new KeyValuePair<string, object?>(MeterTags.ErrorType, exception.GetType().FullName)); | ||
| } | ||
|
|
||
| totalEnvelopeUnwrappingErrors.Add(succeeded ? 0 : 1, meterTags); |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
No description provided.