Including a # at the beginning of a cronspec causes it to break.

[leehambley]

A customer changed a cronspec to begin with a # (they wanted to comment it out) and the platform started raising 418 unhandled internal errors.

The issue is that the parser has validated the cronspec at the time of the change, but has not been able to re-read it at a later date.

The broken cronspec prevents the associated task being editable.

A log excerpt:

Jun 20 17:16:59 api.app.harrow.io api[3688]: Internal server error: Unknown error type encountered: syntax error in minute field: '#*/2': &errors.errorString{s:"syntax error in minute field: '#*/2'"}