Apps should not pend forever on software bus
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 67
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
The SAMPLE_APP, which is supposed to exemplify the current best practices, shouldn't be pending forever on a software bus message as it does here:
The problem with pending forever is that the app also needs to perform an orderly exit if a restart/reload/delete command is sent to ES, which is checked by CFE_ES_RunLoop(). If an app is pending forever for software bus messages but none are sent, then the shutdown request will remain pending indefinitely.
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 in fsw/src/sample_app.c at lines 85-87, then inspect how CFE_ES_RunLoop() interacts with the software bus wait. Confirm how the app can stop waiting long enough to handle restart, reload, or delete commands. Done means the SAMPLE_APP no longer remains pending indefinitely when no bus messages arrive and can exit orderly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100