Refactor error handling

[alyssadai]

• [ ] Display error messages in alert UI elements
  • https://dash-bootstrap-components.opensource.faculty.ai/docs/components/toast/
  • https://dash-bootstrap-components.opensource.faculty.ai/docs/components/alert/
• [ ] When parsing of a new user-uploaded bagel raises errors, show alert (include problematic file name) and use dash.no_update to keep all previous inputs instead of clearing them
• [ ] Use input-filename component to display prompt to upload bagel when one has not been chosen
• [ ] Wrap any non-handled errors in an informative message for display to user as well ("Something went wrong while processing this file")

Other resources:

• https://community.plotly.com/t/informing-user-of-callback-exceptions/7870

[github-actions[bot]]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days. We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[github-actions[bot]]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days. We have applied the _flag:stale label to indicate that this issue should be reviewed again. When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this label in the future. Use sparingly!