Bug Fix for null pointer exception in case header getFields is null in workflow context replay #889
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abhishekj720
requested review from
Groxx,
dkrotx,
taylanisikdemir and
demirkayaender
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Added a fix for the case when headers's getFields is null while checking for workflowcontext in replay.
Causing null pointer in the code.
Why?
Bug fix
How did you test it?
Need to add test for it. will discuss with the team, now adding this to fix bug and unblock customer.
Potential risks
It should be a safe change, as it is returning empty map in case of empty getFields.
Release notes
Documentation Changes