fix: converting workflow results datetime objects (#1255) #1382
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.
Describe the bug
When the result of a workflow execution might include datetime object, we're unable to save it in to the database because of a serialization problem.
Solution:
So now, according to mock testing data:
e.g.
mock_action1 = Mock(name="action1")
mock_action1.name = "action1"
mock_action 1.provider.results = {"result": "value1"}
results dict's fields will be iterated and datetime objects will be converted to be properly saved in DB
Needs to be double checked with relevant workflowexecution data