-
Notifications
You must be signed in to change notification settings - Fork 48
Refine test to show minimal metadata needed for errors to be imported successfully #4943
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
Conversation
...Tests/Recoverability/MessageFailures/When_processing_message_with_missing_metadata_failed.cs
Show resolved
Hide resolved
...Tests/Recoverability/MessageFailures/When_processing_message_with_missing_metadata_failed.cs
Show resolved
Hide resolved
Indeed, that should be optional but requires SP/SC changes.
The header might be auto generated based on the transport message ID in some transports. Where are you referring to? It isn't obvious in the diff from this PR. |
… for UX experience
|
@ramonsmits I've created separate tests for what is needed for ingestion to work vs what is needed for the UI to render reasonably. See if you like it |
...ceTests/Recoverability/MessageFailures/When_ingesting_failed_message_with_missing_headers.cs
Outdated
Show resolved
Hide resolved
...ceTests/Recoverability/MessageFailures/When_ingesting_failed_message_with_missing_headers.cs
Outdated
Show resolved
Hide resolved
...ceTests/Recoverability/MessageFailures/When_ingesting_failed_message_with_missing_headers.cs
Outdated
Show resolved
Hide resolved
ramonsmits
left a comment
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.
LGTM except for the string values
|
Good catch, replaced with constants now |
I did some testing to figure out which minimal set of metadata is needed for error imports to work.
Notes:
ProcessingMachinefeels off, I think we should default it to null or unknown to be more flexible when importingI will raise follow-up PRs to address the above