Try to catch / workaround 5215 (#5216)
Fixes #5215 It's not really clear how the error can be obtained, but this PR adds a workaround for the problem. There are 2 possible ways to get the `message` parameter - from an error and from the operation status. - Our status messages are always represented by a string, no any other values is assigned. - rq is trickier here - it receives rq data and [decodes it](https://github.com/rq/rq/blob/master/rq/job.py#L603-L609) if there is an error, but the operations can leave None as the `exc_info` value. Maybe [this issue](https://github.com/rq/rq/issues/1633) is relevant here.
Showing
想要评论请 注册 或 登录