-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
Fix mistral callback failure when result contains unicode #3721
Conversation
bbbaeb7
to
946c68a
Compare
action_executions.ActionExecutionManager, 'update', | ||
mock.MagicMock(return_value=None)) | ||
def test_callback_handler_with_result_as_dict_with_unicode_type(self): | ||
self.callback_class.callback('http://127.0.0.1:8989/v2/action_executions/12345', {}, |
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.
It would be good to test unicode for all the various type (string, list, dict) and also add a test case with actual unicode string (💩
) in addition to existing tests with the unicode escape sequences.
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.
Besides that, LGTM 👍
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.
@Kami added more unit tests as requested
Added v2.4.1 milestone since I assume this will / should go into v2.4.1. |
👍 There are also some Unit tests failing in Travis. |
When result of action execution contains unicode, Mistral callback fails and leads to orphaned workflow execution.
757f53f
to
eb3c5c1
Compare
When result of action execution contains unicode, Mistral callback fails and leads to orphaned workflow execution.