Closed akhenry closed 7 months ago
I'm having trouble reproducing this locally w/ quickstart and also on Testathon.
Not sure if this is related: https://github.com/akhenry/openmct-yamcs/issues/384
Cannot reproduce, marking as retest for 4.0.0
Tested this again, cannot reproduce. This is fixed
Originally reported as VIPERGC-320
Summary
An issue was reported with the command history capability in Open MCT whereby a new command would only appear once a subsequent command was received.
For context, the handling of Commands in Open MCT is different to other types of telemetry. A single command in Yamcs goes through multiple states, each of which is separately emitted to Open MCT. Open MCT collates all of these state changes into a single row.
Expected vs Current Behavior
Command history rows should appear in the command history table immediately upon receipt.
Impact Check List
Environment