Closed unlikelyzero closed 5 months ago
At the moment, our mdb override limit logic is not clearing the limit values as intended:
https://github.com/akhenry/openmct-yamcs/blob/master/tests/e2e/yamcs/limits.e2e.spec.js#L115-L117
The fix is to use https://docs.yamcs.org/python-yamcs-client/tmtc/client/#yamcs.tmtc.client.ProcessorClient.clear_alarm_ranges
To clear alarm ranges on the given parameter
@unlikelyzero Is this still a valid issue?
I haven't had time to test the fix yet
solved, this was actually catching a bug
At the moment, our mdb override limit logic is not clearing the limit values as intended:
https://github.com/akhenry/openmct-yamcs/blob/master/tests/e2e/yamcs/limits.e2e.spec.js#L115-L117
The fix is to use https://docs.yamcs.org/python-yamcs-client/tmtc/client/#yamcs.tmtc.client.ProcessorClient.clear_alarm_ranges
To clear alarm ranges on the given parameter