-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Handle missing objects gracefully in Open MCT #4258
Comments
@alizenguyen @shefalijoshi are there 4 or more possible scenarios to test?
|
@unlikelyzero I'm not sure exactly how many ways you can remove data, I went with the instructions in the 'steps to reproduce' above. |
@alizenguyen @unlikelyzero Should this be closed for testathon? |
ALMOST fixed :) Just one edge case:
Verified all cases except for LADTableSet. In the case of LADTableSets the LadTable containing the missing object does not render at all, and the following error appears in the console: Note that there is still an error message being produced by the LADTableSet: TypeError: Cannot read properties of undefined (reading 'valueMetadatas')
at a.hasUnits (LadTableSet.vue?3c5d:86:1)
at pn.get (vue.min.js?8f59:6:26853)
at pn.evaluate (vue.min.js?8f59:6:27991)
at a.eval [as hasUnits] (vue.min.js?8f59:6:29888)
at a.LadTableSetvue_type_template_id_2afd3da8_render (LadTableSet.vue?4eb8:1:143)
at e._render (vue.min.js?8f59:6:35545)
at a.r (vue.min.js?8f59:6:68553)
at pn.get (vue.min.js?8f59:6:26853)
at pn.run (vue.min.js?8f59:6:27740)
at ln (vue.min.js?8f59:6:25804) Will file a followup issue for a future release to fix this. It appears to be otherwise benign |
Verified fixed. Nice work! |
Summary
When objects in views are missing, we should not fail but handle the issue gracefully.
Expected vs Current Behavior
Currently several views fail with console errors and Open MCT shows an endless spinner when objects are missing.
We should ensure that views load even when objects are missing.
Impact Check List
Steps to Reproduce
Environment
Additional Information
The text was updated successfully, but these errors were encountered: