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

Not all invalid commands send an error event message #118

Closed
semaldona opened this issue Dec 13, 2021 · 1 comment · Fixed by #282
Closed

Not all invalid commands send an error event message #118

semaldona opened this issue Dec 13, 2021 · 1 comment · Fixed by #282
Assignees
Milestone

Comments

@semaldona
Copy link

Per requirement CF1004, all invalid commands should issue an error event message. For example, the TX_FILE command does not send the event message when certain parameters in the command are invalid. There are several other commands that need to be dispositioned for compliance.

@astrogeco astrogeco added this to the Draco milestone May 11, 2022
@skliper skliper added bug and removed requirements labels May 20, 2022
@skliper
Copy link
Contributor

skliper commented May 20, 2022

Switched to bug since this is really just not implemented so it's a requirements failure, not a requirements issue.

@havencarlson havencarlson self-assigned this Jul 14, 2022
havencarlson added a commit to havencarlson/CF that referenced this issue Jul 14, 2022
havencarlson added a commit to havencarlson/CF that referenced this issue Jul 14, 2022
dzbaker added a commit that referenced this issue Jul 20, 2022
Fix #118, failed commands send error event message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants