Gauge displays NaN when telemetry not available

[charlesh88]

Summary

When a Gauge has a telemetry source, but that source isn't providing any data, the Gauge is displaying NaN.

Expected vs Current Behavior

The Gauge should display "---" and should not display the "out of range" indication.

Steps to Reproduce

1. Add a telem source that doesn't have any data currently to a Gauge.

Environment

• Open MCT Version: R 2.0.5
• Deployment Type: /testathon
• OS:
• Browser:

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?
• [x] Does this impact a critical component?
• [x] 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

[charlesh88]

Testing Instructions

1. Find a numeric telemetry source that is not emitting data, or set the Time Conductor such that the source won't retrieve any data.
2. Alternately, create a Sine Wave Generator as a data source and set its Loading Delay to 5000 ms or more.
3. Add your data source to a Gauge. Make sure that "Display current value" is enabled in the Gauge's properties.
4. Verify that you don't see "NaN" in the Gauge numeric display, but instead see "--" as shown below.

[unlikelyzero]

Verified fixed

[charlesh88]

Still broken in 3.3.0-next.