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

Jetpack Checklist: Display actionable error when we can't install VP, instead of endless spinner #34627

Open
jeffgolenski opened this issue Jul 12, 2019 · 2 comments

Comments

@jeffgolenski
Copy link
Member

Design tbd.

Sometimes VP can't be installed or some type of error occurs. When this is the case, the checklist displays a loading spinner that runs indefinitely.

After a given amount of time, we should recognize a "time out" and throw an actionable error within the task UI itself. Prompting them to reach out to happiness.

Example: "We're sorry, something went wrong. Get help now."

Screen Shot 2019-07-12 at 10 27 03 AM

@jeffgolenski jeffgolenski self-assigned this Jul 12, 2019
@jeffgolenski jeffgolenski added this to Backlog in Jetpack Improved Onboarding via automation Jul 12, 2019
@simison simison moved this from Backlog to In progress in Jetpack Improved Onboarding Jul 31, 2019
@simison simison moved this from In progress to Backlog in Jetpack Improved Onboarding Jul 31, 2019
@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants