Show error in UI if mission model upload fails

[dandelany]

Background

Original backend ticket: https://github.com/NASA-AMMOS/aerie/issues/1273

Users have run into a situations where an error occured when Aerie processed the mission model jar, but no error appeared to the user. Fixing this is a bit more difficult than just displaying an HTTP response, because the upload & subsequent processing happen asynchronously, so there is some delay between the initial request & the error.

@Mythicaeda has implemented an events view in the Hasura API to allow us to get any errors that occur into the frontend, see implementation details here: https://github.com/NASA-AMMOS/aerie/pull/1418

Requirements

• Aerie should show an error message in the UI if an error occurs during mission model upload.
• The frontend can implement this by querying the event views detailed in https://github.com/NASA-AMMOS/aerie/pull/1418 after uploading
• Unclear if UI needs to subscribe to these views or just include the extra query info with the existing status check after upload

Tagging @parkerabercrombie for visibility..

Design direction: https://www.figma.com/design/gWEDKg40Uv0EUvEB9BVmGZ/Model-Spec-Error-Handling?node-id=19-18496&t=hw9Sf1BK9kROvi2T-4

• [ ] Plan select dropdown
  • [ ] Update plan select dropdown text to show extracting... and extraction failed if present
• [ ] Model page
  • [ ] update table to include icons + spinner for extracting and extraction errors
  • [ ] Add jar file status line to details and show callouts for states
  • [ ] add ability to re-check extraction
• [ ] Plan browse page
  • [ ] show extracting and extraction errors by model select dropdown
  • [ ] disable create plan if a model currently being extracted is selected
  • [ ] Show extraction errors icon next to model name if there are errors
• [ ] Single plan page
  • [ ] show banner (similar to plan snapshot) if a model is linked that has extraction errors
  • [ ] (stretch): Add model errors to console

[duranb]

@lklyne @dandelany Is there a design for this? Showing the error immediately after upload is easy enough, but currently the users can still see that uploaded model if they go to the model list page. I feel like we should at the very least show that error maybe in the models table in a column or something. But it also feels weird that we even show that model at all in the table if it's not something that the user can use. Can we filter out any models with errors from the table if it's not useful to show them?

[lklyne]

@lklyne @dandelany Is there a design for this? Showing the error immediately after upload is easy enough, but currently the users can still see that uploaded model if they go to the model list page. I feel like we should at the very least show that error maybe in the models table in a column or something. But it also feels weird that we even show that model at all in the table if it's not something that the user can use. Can we filter out any models with errors from the table if it's not useful to show them?

A few potential approaches top of mind:

1. Treatment in the table
2. Details about what went wrong with the upload in model details
3. Hide failed uploads and show some sort of callout at the top (not a great approach for collaboration)
4. A pop up of some sort? (Probably the worst approach)