Possible TC scheduler bugfix #738
This is included in #735 so maybe not necessary.
As far as the logic goes, it is intended behavior that commands that are scheduled too close in the future are rejected.
This is an operational requirement as one should not upload scheduled TCs so close to execution time.
Thinking about it, I am not sure if it really belongs into the flight software, but I think the operational impact is minimal and would keep it to be backward compatible.
Also, agree on #735 fixing the integer underflow (unintentionally. While I recognized that line as suboptimal I actually did not realize the underflow).
Pull request closed
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?