Check for integer & float rollover detection & handling
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Theoretically, if a mission were to use certain epochs/parameters, it'd be possible to force MMTC into an overflow/rollover on both integer and floating-point types. Check any aspect of MMTC that might count seconds from an epoch in a 31/32-bit field, such as:
- SCLK fields
- TDT fields
..and ensure our documentation specifies under what conditions they'd overflow, and possibly also:
- Change datatypes to extend their range of usefulness
- Change mathematical behavior to detect and fail on overflow/underflow scenarios
ref: 2038 problem
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing MMTC's SCLK and TDT fields and any seconds-from-epoch values stored in 31- or 32-bit integer or floating-point types. Document the conditions for rollover or overflow, then determine whether datatype changes or explicit overflow/underflow handling are needed; done means the relevant behavior and limits are documented and addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100