You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
CFE_MSG_GetMsgId returns a status value to indicate success or failure of the call, but neither of the usages in the sample app check if it is successful nor do they state that the return value is ignored by design.
To Reproduce
N/A
Expected behavior
Sample app should either make use of the return value to verify success or should note the reason why this is not being done.
I don't know if any change is necessary here. Most uses of CFE_MSG_GetMsgId ignore the return value, and purely use it for its functionality.
Nevertheless, if it's considered desirable to illustrate consideration of the return value, given that this is the sample app, a minimalistic solution (for the first case) might be:
Describe the bug
CFE_MSG_GetMsgId returns a status value to indicate success or failure of the call, but neither of the usages in the sample app check if it is successful nor do they state that the return value is ignored by design.
To Reproduce
N/A
Expected behavior
Sample app should either make use of the return value to verify success or should note the reason why this is not being done.
Code snips
sample_app/fsw/src/sample_app.c
Line 235 in d009197
sample_app/fsw/src/sample_app.c
Line 442 in d009197
System observed on:
N/A
Reporter Info
Alan Gibson NASA/GSFC 587
The text was updated successfully, but these errors were encountered: