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

imported objects are not persisting #4470

Closed
3 of 5 tasks
nikhilmandlik opened this issue Nov 16, 2021 · 2 comments · Fixed by #4477
Closed
3 of 5 tasks

imported objects are not persisting #4470

nikhilmandlik opened this issue Nov 16, 2021 · 2 comments · Fixed by #4477
Assignees
Labels
bug:regression It used to work. Now it doesn't :( severity:critical type:bug
Projects
Milestone

Comments

@nikhilmandlik
Copy link
Contributor

nikhilmandlik commented Nov 16, 2021

Summary

Expected vs Current Behavior

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?

Steps to Reproduce

  1. import any existing objects
  2. refresh page and observe newly imported objects disappear from tree

Environment

  • Open MCT Version:
  • Deployment Type:
  • OS:
  • Browser:

Additional Information

@nikhilmandlik nikhilmandlik self-assigned this Nov 16, 2021
@unlikelyzero unlikelyzero added the bug:regression It used to work. Now it doesn't :( label Nov 16, 2021
@unlikelyzero unlikelyzero added this to Needs triage in Bug Tracker via automation Nov 16, 2021
@unlikelyzero unlikelyzero moved this from Needs triage to Will Do in Bug Tracker Nov 16, 2021
@unlikelyzero unlikelyzero added this to the Target: 1.8.1 milestone Dec 8, 2021
akhenry pushed a commit that referenced this issue Dec 8, 2021
* imported objects are not persisting #4470
* disabled karma spec reporter suppressErrorSummary
@akhenry
Copy link
Contributor

akhenry commented Dec 8, 2021

Closed by #4477

@unlikelyzero
Copy link
Collaborator

Verified but there is an open issue filed here: #4561

unlikelyzero pushed a commit that referenced this issue Dec 13, 2021
* Transaction fix (#4421) (#4461)
* When transaction is active, objects.get should search in dirty object first.
* Bugfix/create tree node (#4472)
* Transaction fix (#4421)
* When transaction is active, objects.get should search in dirty object first.
* find insert location prior to adding item to tree
* no need to resort
* add item should only add to direct descendants
* remove unused function
* copy composition before sorting
* remove unused var
* remove master pollution
* Revert "remove master pollution"
* add item to correct location
* Changed descending to ascending in sort order method (#4480)
* adding RAF to display layout alphanumerics (#4486)
* [Tabs] Sizing of offscreen tabs causing issues (#4444)
* [LAD Tables] Use RAF for updating template (#4500)
* Fixes LAD rows for string telemetry (#4508)
* Fixes LAD rows for string telemetry
* saving the object if it was missing (#4471)
* 4328 - Maintain reference to a focusedImage if the bounds change (#4545)
* WIP: adding assertions to catch negative index state
* just testing the flow
* SUpdate the image history index to previous selected image
* Cleaning up spacing and log statements
* Converted focusedImageIndex assignment to ternary and general cleanup
* imported objects are not persisting  (#4477)
* imported objects are not persisting #4470
* disabled karma spec reporter suppressErrorSummary
* update version number
* Delete importFromJsonAction directory since it was empty
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 :( severity:critical type:bug
Projects
Development

Successfully merging a pull request may close this issue.

3 participants