Issue 1161 - creates various ways to trigger the exception #1168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is demonstrating the issue #1161 by adding a Minimal Reproductible Example.
This creates three ways to trigger the issue, unfortunately with 3 different results, and I'm not sure whether they are the result of unit tests misconfiguration or other underlying problems:
MessageHeadersTestsfails the comparison because theHeaderis not filledIntegrationTeststhrows a weird exception wherein it mentions different property namesThe third way to trigger the exception is as follows:
This should put you in the place that throws the exception
