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

[Object API] Use of structuredClone causes errors with related telemetry in imagery #6236

Closed
3 of 7 tasks
akhenry opened this issue Jan 31, 2023 · 1 comment · Fixed by #6237
Closed
3 of 7 tasks

Comments

@akhenry
Copy link
Contributor

akhenry commented Jan 31, 2023

Summary

A recent change to the object API results in objects being cloned in order to provide the pre-mutation model in observer callback functions. This change was using the builtin structuredClone which is intended for this purposes, however structuredClone will bork on functions. In Open MCT for VIPER we are defining functions on imagery metadata in order to determine staleness tolerances.

Steps to Reproduce

  1. Attempt to navigate to an image in the telemetry dictionary
  2. Observe the presence of a spinner

Environment

  • Open MCT Version: 7917f09
  • Deployment Type: VIPER Test

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

@shefalijoshi
Copy link
Contributor

Verified Fixed. Able to view imagery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants