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
But the default time system is fixed and bounds are provided for the fixed time system they are overridden.
Expected vs Current Behavior
When bounds are provided for the fixed time system and that system is the default time system, those bounds should be applied at load.
Currently the bounds of the realtime clock are applied instead.
Steps to Reproduce
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
The text was updated successfully, but these errors were encountered:
Summary
If OMM is configured to
allowRealtime: true,
or
allowLAD: true,
But the default time system is fixed and bounds are provided for the fixed time system they are overridden.
Expected vs Current Behavior
When bounds are provided for the fixed time system and that system is the default time system, those bounds should be applied at load.
Currently the bounds of the realtime clock are applied instead.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: