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

[Condition Sets] Breaking when no telemetry is returned #7996

Open
7 tasks
jvigliotta opened this issue Feb 1, 2025 · 1 comment · May be fixed by #7997
Open
7 tasks

[Condition Sets] Breaking when no telemetry is returned #7996

jvigliotta opened this issue Feb 1, 2025 · 1 comment · May be fixed by #7997
Assignees
Labels

Comments

@jvigliotta
Copy link
Contributor

jvigliotta commented Feb 1, 2025

Summary

If no telemetry is ever returned to a condition set, it will throw errors. This was causing the Default Display in openmct-yamcs examples to break if the user forgot to run the simulator. akhenry/openmct-yamcs#490 (comment)

Expected vs Current Behavior

Steps to Reproduce

  1. Follow the steps on https://github.com/akhenry/openmct-yamcs to get up and running with quickstart (must be a fresh version, remove any existing openmct-yamcs repo)
  2. Do not run the simulator simulator.py
  3. View the example at localhost:9000
  4. Screen covering errors... many of them

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@jvigliotta jvigliotta self-assigned this Feb 1, 2025
@jvigliotta jvigliotta linked a pull request Feb 1, 2025 that will close this issue
14 tasks
@jvigliotta
Copy link
Contributor Author

Testing

  • above repro steps

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.

1 participant