`getClock` is being called non-stop

[davetsay]

Summary

In realtime mode, getClock is being called repeatedly, on every tick.
Following the call stack,
On new bounds, ConductorInputsRealtime.vue calls handleNewBounds , which calls updateCurrentValue, which calls timeContext.getClock().currentValue().

Expected vs Current Behavior

Should know the current clock for the context and should get currentValue from tick event.

Steps to Reproduce

1. open the console and search in openmct.js for getClock.
2. find a place in minimized code which calls getClock and put a break point on it.
3. when it breaks, use the console tools to nav into the getClock function
4. put a breakpoint or logpoint inside the getClock function
5. Observe that getClock can't stop and won't stop

Environment

• Open MCT Version:
• Deployment Type:
• 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?
• 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

getClock.cant.stop.wont.stop.mov