You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related telemetry for imagery is not being received in realtime mode due to changes made in this PR. This manifests as the Compass Rose not showing up for streaming imagery in realtime mode (either local clock or remote clock).
Expected vs Current Behavior
Related Telemetry for streaming imagery should be received correctly, the compass rose should show up if the appropriate Related Telemetry is present
Steps to Reproduce
Navigate to our testing environment
Switch to either local clock or remote clock mode
View streaming imagery from YAMCS
Wait for an image to stream in
Observe console errors
Observe there is no compass rose
Environment
Open MCT Version: 2.1.5-SNAPSHOT
Deployment Type: openmct-yamcs
OS: MacOS
Browser: Chrome / any
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
The text was updated successfully, but these errors were encountered:
Summary
Originally described in VIPEROMCT-225
Related telemetry for imagery is not being received in realtime mode due to changes made in this PR. This manifests as the Compass Rose not showing up for streaming imagery in realtime mode (either local clock or remote clock).
Expected vs Current Behavior
Related Telemetry for streaming imagery should be received correctly, the compass rose should show up if the appropriate Related Telemetry is present
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: