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

[Stacked Plot] Removing a plot from the elements pool is removing the wrong one #6178

Closed
2 of 7 tasks
rukmini-bose opened this issue Jan 25, 2023 · 4 comments · Fixed by #6206
Closed
2 of 7 tasks

Comments

@rukmini-bose
Copy link
Contributor

rukmini-bose commented Jan 25, 2023

Summary

Faulty.Stacked.Plot.mov

When removing a plot from a stacked plot using the Elements Pool, the wrong one is being removed.

In the video, I have added 2 plots to the Stacked Plot: (1) Overlay Plot with 4 elements (2) Sine Wave Generator.
I am attempting to remove the Sine Wave Generator from the Stacked Plot. Upon clicking the delete confirmation button, notice that the Overlay Plot has disappeared from the canvas. Instead, the Sine Wave Generator still stands.

Expected vs Current Behavior

When there are multiple plots in a stacked plot and we want to remove one, we expect the plot we select to remove to successfully disappear. Instead, we are seeing another element from the stacked plot being removed. However, if we refresh the page, the changes are applied successfully– the correct element is removed from the Stacked Plot

Steps to Reproduce

  1. Create a Stacked Plot and add 2 or more plots to it.
  2. Delete one of the plots from the Elements Pool (make a note of which one you are deleting).
  3. After hitting the delete confirmation button, notice that while the elements pool has removed the correct plot, the canvas has not.

Environment

  • Open MCT Version: 2.1.6
  • Deployment Type: Testathon
  • OS:
  • Browser: Chrome

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

@ozyx ozyx added this to the Target:2.1.6 milestone Jan 25, 2023
@akhenry
Copy link
Contributor

akhenry commented Jan 25, 2023

Yikes. Good catch.

@akhenry
Copy link
Contributor

akhenry commented Jan 31, 2023

Testing notes

  1. Follow reproduction steps in original issue and confirm that the correct plot trace is being removed
  2. Repeat reproduction steps for an overlay plot and confirm that the correct plot trace is being removed
  3. Repeat reproduction steps for some non-plot objects, like tables, LAD tables, etc. and confirm that the correct child is being removed.

@ozyx
Copy link
Member

ozyx commented Jan 31, 2023

Verified Testathon 1-31-2023

Removal from stacked plots, telemetry tables, overlay plots, and LAD tables were tested, all looks good

@michaelrogers
Copy link
Contributor

Fix verified during testathon 01/31/2023.

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.

5 participants