-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apps should not pend forever on software bus #55
Comments
Update - I did test this and confirm that the ES will actually forcibly delete the task via an As a best-practice example, it should use a time-limited pend on the software bus, so it can also poll the |
Calling this an "enhancement" rather than a "bug" because it is also saved by the fact that SCH_LAB by default sends a message every few seconds, so while less than ideal, its not fully broken. |
Added milestone, feel free to fix if you want |
Apps should not pend forever on software bus receive, because they should also periodically check CFE_ES_RunLoop even if no commands were received.
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:
sample_app/fsw/src/sample_app.c
Lines 85 to 87 in b956292
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.The text was updated successfully, but these errors were encountered: