Skip to content
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

CFE_ES_OneAppTlm_Payload_t telemetry struct contains non mission-scoped-sized array #705

Closed
johnphamngc opened this issue May 14, 2020 · 1 comment · Fixed by #899 or #936
Closed
Labels
Milestone

Comments

@johnphamngc
Copy link

johnphamngc commented May 14, 2020

Is your feature request related to a problem? Please describe.
Unsure if this is intentional, but
CFE_ES_AppInfo_t is directly used by CFE_ES_OneAppTlm_Payload_t which is ground visible. CFE_ES_AppInfo_t uses OS_MAX_*, whereas all other ground-visible telemetry uses the mission-scoped CFE_MISSION_MAX_*.

Describe the solution you'd like
CFE_ES_OneAppTlm_Payload_t should be structured such that the size is dependent solely on mission-scoped constants and consistent amongst all CPUs.

This is an enhancement as opposed to a bug report since in practice both constants are likely to be same.

Describe alternatives you've considered
None

Additional context
None

Requester Info
John N Pham, Northrop Grumman

@johnphamngc johnphamngc changed the title CFE_ES_OneAppTlm_Payload_t contains non mission-scoped-sized array CFE_ES_OneAppTlm_Payload_t telemetry struct contains non mission-scoped-sized array May 14, 2020
@jphickey
Copy link
Contributor

Yes, this is an issue! Not intended.

I would call it a bug because it creates an unintended/invalid dependency on osconfig.h header file in the code. The CFE message definitions shouldn't depend on osconfig.h or anything else that might change from platform to platform. It's (probably) not an operational bug because as you note they are likely to be the same value, but it is a code bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants