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

Display Blueprint execution errors in the UI #1230

Closed
adamziel opened this issue Apr 11, 2024 · 1 comment · Fixed by #1336
Closed

Display Blueprint execution errors in the UI #1230

adamziel opened this issue Apr 11, 2024 · 1 comment · Fixed by #1336
Assignees

Comments

@adamziel
Copy link
Collaborator

When a Blueprint fails to execute, it seems like a bug in Playground. Sometimes it is, but sometimes it's a developer error, e.g. downloading a non-existent file. Let's clearly communicate any Blueprint execution problems to the user directly in the UI so they at least know what went wrong.

Ideally, these two could be tackled too:

Related:

@adamziel adamziel added this to the Zero Crashes milestone Apr 11, 2024
@adamziel
Copy link
Collaborator Author

This console UI for errors could work here:

CleanShot 2024-04-16 at 11 19 25@2x

@bgrgicak bgrgicak self-assigned this Apr 18, 2024
bgrgicak added a commit that referenced this issue May 7, 2024
Fixes #1230

## What is this PR doing?

It adds a modal that loads if Playground fails to start. The modal
contains error details.

## What problem is it solving?

It should help users debug startup issues like Blueprint errors.

## How is the problem addressed?

By showing a modal with Playground logs when `startPlaygroundWeb` fails
to start.

## Testing Instructions

- Checkout this branch
- Open [Playground with an incorrect
blueprint](http://localhost:5400/website-server/#{%20%22steps%22:%20[%20{%20%22step%22:%20%22error%22%20}%20]%20})
- Click _Don't show again_ 
- Reload and confirm that the modal doesn't load
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants