[chillfig]

---

name: FSW Code Change
about: Flight Software code changes
labels: fsw

Description of Change

Resolve application and library identity and code range before each checksum chunk. On a new ES resource ID, discard partial progress and the old baseline, then report the reset through an informational event. Preserve corruption detection for unchanged instances and update results-table schemas, regression tests, and documentation.

Linked Issue

Closes #20

Requirements Impact

• Requirement ID(s):
• Requirements updated as necessary
• Existing requirements are still satisfied by this change

Testing Evidence

Unit Tests (UT Assert)

Unit test result:

New tests:

• CS_ComputeApp_Test_RelocatedAppRebaseline()

• CS_ComputeApp_Test_RelocatedMidPassRestarts()

• CS_ComputeApp_Test_SameAddressReloadRestarts()

• CS_ComputeApp_Test_UnchangedInstanceCorruption()

• CS_ComputeApp_Test_UnchangedInstanceResumes()

• CS_ComputeApp_Test_LookupFailureThenReload()

• CS_ComputeApp_Test_InvalidAddressThenRecovery()

• CS_ComputeApp_Test_SameInstanceMappingChange()

• CS_ComputeApp_Test_LibraryReload()

• CS_RecomputeAppChildTask_Test_ReloadDuringRecompute()

COSMOS Test Suite

N/A

Areas of Expertise Touched

• ASTRO
• CI/CD
• COSMOS
• Cybersecurity
• Docker
• EDS
• Git
• PSPs
• SBN
• SMP
• Tables
• TSN
• Unit Tests
• Other

---

Author Checklist

• Linked GitHub issue is referenced above
• Code has been formatted with .clang-format
• Static analysis workflows ran and passed
• Unit tests (UT Assert) updated/added to cover code changes
• Unit test workflows ran and passed
• COSMOS test suite was run; tests updated/added if relevant changes were made
• Requirements have been reviewed; updated or confirmed still satisfied (see above)
• Testing evidence is included above
• Self-review of the diff completed

---

Reviewer Checklist

• Code logic is correct and matches the stated intent
• Code is readable, maintainable, and follows project conventions (ask your lead if you are unsure of where to find these conventions)
• .clang-format has been applied
• Static analysis results reviewed and acceptable
• The change has been exercised by the unit tests (not just that tests pass — the new/changed code paths are actually covered)
• COSMOS test suite was executed against this change and results reviewed (or confirmed N/A with justification)
• Reviewer has independently verified the change behaves as described (e.g., by running the tests locally, reviewing CI output in detail, or performing additional ad-hoc testing as warranted)
• Memory safety reviewed (allocation, bounds, lifetime, stack usage)
• Requirements impact reviewed and appropriate
• Error handling is appropriate
• Appropriate Expert areas have been reviewed

Reviewer Testing Notes

• Code logic is straightforward and makes sense
• Code is very readable
• Everything is formatted properly with clang
• Analyzed https://github.com/nasa/CS/actions/runs/40563234455, and the cppcheck artifact reports 0 errors
• I reviewed all the added unit tests and couldn't find a scenario that wasn't covered
• COSMOS test not available
• Local unit tests were reviewed and CI output was vetted
• TBD
• Requirements update was reviewed and approved
• Error handling is good

[LuntCayden]

The code looks solid. Once you address Cameron's feedback on test maintainability (extracting the magic numbers into variables and macros), this should be ready. The reload detection logic looks comprehensive and the test coverage is good.

[Cameron-Sykes]

The code looks solid. Once you address Cameron's feedback on test maintainability (extracting the magic numbers into variables and macros), this should be ready. The reload detection logic looks comprehensive and the test coverage is good.

Hi @LuntCayden, I approved and feel that my issues were addressed. Can you resolve your requested change?