Checksum errors after restarting app
Open
Nobody has claimed this yet.
bug
- Dominant language
- C
- Stars
- 36
- Forks
- 41
- Avg merge
- 11d 19h
- Merged PRs (30d)
- 2
Description
Summary scenario
- Application gets an exception
- ES restarts the application
- There is a high probability that the application checksum has changed due to the restart.
- Checksum is not notified to recompute the application checksum. When it finds the checksum has changed, it puts out an event message to that effect.
- HS is monitoring for application checksum messages, and does a processor reset as a consequence.
Imported from GSFCCFS-952
Contributor guide
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 tracing the application restart path described in the issue, then inspect how checksum recomputation and checksum event messages are handled between ES and HS. Done means a restart reliably triggers the checksum notification and the resulting processor reset behavior is verified; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100