[Time Conductor + Imagery] Console error when adjusting start or end bounds for imagery

[khalidadil]

Summary

When I adjust the start or end bounds of the time conductor in realtime mode, using remote clock while viewing imagery, I'm seeing an error in the browser console: t.padStart is not a function. I think this is coming from the format function in the timePopupRealtime.vue component.

[ozyx]

Testing Instructions

• Navigate to imagery telemetry in realtime / remote clock mode
• Activate the ITC
• Adjust the start or end bounds a few times
• Observe no console errors and the ITC continues to function nominally

[ozyx]

Still an issue -- seen in Testathon 07/21/23

[ozyx]

Related / possible dupe: #6821

[shefalijoshi]

Closing to retest

[ozyx]

Verified fixed Testathon 7/27/23

Edit: I'm seeing the same thing as @charlesh88 below

[charlesh88]

Testathon 2023-07-27: NOT fixed. Initially enabling the ITC on an Imagery end point throws this console error now:

Main TC was in RT / Remote Clock with -00:15:00 and +00:00:15.
ITC (at time of enabling) was RT / Remote Clock with -01:15:00 and +00:00:15 - note that this is an additional hour offset into the past than the main TC setting.

[shefalijoshi]

Testing Instructions

1. Ensure imagery is showing up including thumbnails and related telemetry
2. Enable the independent time conductor
3. Set the mode to Fixed timespan and set the start and end dates
4. Ensure that imagery is showing up and that the related telemetry is valid

[ozyx]

Verified Fixed -- Testathon 7/31/23

[khalidadil]

Seems to be fixed, but I'm getting an error in the console:
vue.esm-bundler.js:1708 Error: Attempted to mutate immutable object [image name]

[charlesh88]

Testathon 2023-07-31: verified fixed, although I am seeing console errors ("Error: Attempted to mutate immutable object Navcam_left_image") when enabling the ITC on the Imagery view.

[unlikelyzero]

Keeping this closed and tracking follow up #6889