I'm not against making status_reason longtext in the long term, but at this stage in the Kilo development cycle I'd rather just make sure status_reason is truncated where necessary
I'm not against making status_reason longtext in the long term, but at this stage in the Kilo development cycle I'd rather just make sure status_reason is truncated where necessary