Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Telemetry Table] in place updates are not being rendered #7938

Closed
3 of 7 tasks
davetsay opened this issue Dec 2, 2024 · 0 comments · Fixed by #7940
Closed
3 of 7 tasks

[Telemetry Table] in place updates are not being rendered #7938

davetsay opened this issue Dec 2, 2024 · 0 comments · Fixed by #7940
Assignees
Labels
bug:regression It used to work. Now it doesn't :( type:bug

Comments

@davetsay
Copy link
Contributor

davetsay commented Dec 2, 2024

Summary

VIPERGC-692
In place datum updates to existing rows are not being rendered in tables
Regression of #6694

Expected vs Current Behavior

If new row data comes in, and the row exists, the new data should be displayed in the row.
Currently this does not happen

Steps to Reproduce

See VIPERGC-692

Testing Instructions

For full production testing, see VIPERGC-692.
Local reproduction steps

  1. Create an Event Message Generator with Acknowledge object
  2. if you don't see this option, open the browser console and enter openmct.install(openmct.plugins.example.EventGeneratorPlugin())
  3. Change the time conductor to realtime mode
  4. Observe after 5 seconds an unacknowledged row will come in and be added to the table
  5. Observe after 5 seconds the row's Acknowledge column will be updated with OK.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:regression It used to work. Now it doesn't :( type:bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant