Result truncated to 500 bytes when saved to cron_job table about cron HOT 6 CLOSED

Thanks for using Cron. Yes, I cut the return String after 500 characters.

} else if ($returnType === 'integer' || $returnType === 'double' || $returnType === 'string') {
    // We cut the string at 500 characters to not overcharge the database
    $jobEntry->return = substr((string) $job['return'], 0, 500);
}

I understand why you want to save more than 500 characters to the database and I want to change Crons behaviour. But maybe it would be better to remove the substr function call because you should know what you are doing with the return value ;)

} else if ($returnType === 'integer' || $returnType === 'double' || $returnType === 'string') {
    $jobEntry->return = (string) $job['return'];
}

One more config value would be overhead in my opinion. What do you thing? At the moment I am on a journey and I am not able to change the code. But I will return on 11.09 and then I can fix this. Of course I have an open mind about PRs ;)

from cron.

I changed the code and removed the truncating. Please update to head and test.

from cron.

Thanks for that, really appreciated.... I've updated the test system, and the existing schedules will click in sometime in the early hours of the morning, I'll be able to check the logs when I get to work tomorrow

from cron.

4 days have passed. Was the test successfully?

from cron.

So far, all successful (no scheduled tasks over the weekend), but Friday and Monday logged their result without any problems.... aside from this mornings run, which failed, for a totally different reason, but logged the fail reason successfully.... now I can modify my log viewer to display the result cleanly

from cron.

Perfect, thank you for your response.

from cron.