Skip to content

Conversation

@thnkslprpt
Copy link
Contributor

Checklist

Describe the contribution

Testing performed
GitHub CI actions all passing successfully (incl. Build + Run, Unit/Functional Tests etc.).

Expected behavior changes
Event types are standardized as per the issue description.

System(s) tested on
Debian GNU/Linux 11 (bullseye)
Current main branch of cFS bundle.

Contributor Info
Avi Weiss   @thnkslprpt

@dzbaker
Copy link
Contributor

dzbaker commented Nov 27, 2024

Thanks @thnkslprpt for these contributions! I'd like to get our team to review this one next week; would you be able to resolve the conflicts?

@thnkslprpt thnkslprpt force-pushed the fix-95-standardize-command-responses branch from 4442ca6 to 3860201 Compare November 28, 2024 07:53
@thnkslprpt
Copy link
Contributor Author

Thanks @thnkslprpt for these contributions! I'd like to get our team to review this one next week; would you be able to resolve the conflicts?

All done @dzbaker

* the definitions table to be set to #CS_STATE_EMPTY.
*/
#define CS_DISABLE_MEMORY_DEF_EMPTY_DBG_EID 133
#define CS_DISABLE_MEMORY_DEF_EMPTY_ERR_EID 133
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this changed to error, as opposed to info? There were a good handful of others that were also changed to error and I'm not sure why?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's been a while mate, but I think it was just based on the issue description which specifically listed those as not complying with the current standard as debug and should be considered an ERROR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Standardization of Command Responses

2 participants