The utils.cut_dict() method returns a string representation of the provided dict, truncated to some number of characters that may or may not be close to the length parameter, depending on the structure and contents of the dict provided.
This can lead to hung workflows when the Execution.state_info field is not truncated properly due to the context variables involved:
2018-03-29T10:44:01.288362-05:00 mistral-server mistral-server: 2018-03-29 10:44:01,280 ERROR [-] Delayed call failed, method: <function _check_and_complete at 0x7fbf3d3c3d08>, exception: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (_mysql_exceptions.DataError) (1406, "Data too long for column 'state_info' at row 1") [SQL: 'UPDATE task_executions_v2 SET updated_at=%s, state_info=%s WHERE task_executions_v2.id = %s'] [parameters: (datetime.datetime(2018, 3, 29, 15, 44, 1),
The cut_dict() method needs to return a string no longer than what the length parameter specifies to ensure that the state_info field is truncated properly and does not cause hung workflows.
Fix proposed to branch: master
Review: https:/