Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix #387, Update minor out-of-family naming/consistency issues in CF #388
Fix #387, Update minor out-of-family naming/consistency issues in CF #388
Changes from all commits
f928452
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check notice
Code scanning / CodeQL
Long function without assertion Note
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thnkslprpt Would you please expand on why the status init is removed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes correct - of the 10 main apps only HK and CF currently check the return of the
CFE_EVS_SendEvent()
reporting successful initialization. MD assigns it to theResult
variable but does not report on failure. In cFE, only the SB module checks the return of this call toCFE_EVS_SendEvent()
, all of the other modules do not do so.In general, out of several thousand invocations of
CFE_EVS_SendEvent()
across cFS, its return value is only checked a handful of times. In CF specifically, there are 141 calls toCFE_EVS_SendEvent()
(just in flight code) and this is the only place that the return value is assigned/checked.If an app is already confirmed to be successfully registered with EVS (as is the case here), it's almost inconceivable that the call to
CFE_EVS_SendEvent()
will fail.It seems undesirable for an app to exit (through failure of the init routine, and then setting
RunStatus
toCFE_ES_RunStatus_APP_ERROR
) just because the event/notification of successful initialization failed for some reason (again, highly improbable if already confirmed registered with EVS).This change is not essential (it can be left as it is) it's more just for the sake of consistency (almost all apps and cFE modules just call
CFE_EVS_SendEvent()
to report successful initialization, without checking its return value or assigning it to theirStatus
/Result
variables).Check warning
Code scanning / CodeQL
Side effect in a Boolean expression Warning
Check warning
Code scanning / CodeQL
Unbounded loop Warning
Check notice
Code scanning / CodeQL
Function too long Note
Check notice
Code scanning / CodeQL
Long function without assertion Note
Check warning
Code scanning / CodeQL-coding-standard
Side effect in a Boolean expression
Check warning
Code scanning / CodeQL
Side effect in a Boolean expression Warning
Check warning
Code scanning / CodeQL-coding-standard
Side effect in a Boolean expression
Check warning
Code scanning / CodeQL
Side effect in a Boolean expression Warning