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.

Sign up for GitHub

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

Jump to bottom

[content-initializer] Provide actionable feedback when content init fails #7605

Closed
csweichel opened this issue Jan 14, 2022 · 0 comments · Fixed by #7753
Closed

[content-initializer] Provide actionable feedback when content init fails #7605

csweichel opened this issue Jan 14, 2022 · 0 comments · Fixed by #7753
Labels
component: content-service priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team type: improvement Improves an existing feature or existing code

Comments

@csweichel
Copy link
Contributor

Is your feature request related to a problem? Please describe

Today content initializer failure is a frustrating experience. Not only does the workspace not start, but the error message isn't helpful either.

Describe the behaviour you'd like

We must aim to provide a message/feedback which gives more insight into what went wrong, for example:

  • when git operations fail, show the output of Git,
  • when prebuild operations fail highlight that that's the case.

Describe alternatives you've considered

Something will always fail - there is no alternative.
@csweichel csweichel added component: content-service type: improvement Improves an existing feature or existing code team: workspace Issue belongs to the Workspace team labels Jan 14, 2022
@csweichel csweichel added the priority: highest (user impact) Directly user impacting label Jan 14, 2022
@csweichel csweichel mentioned this issue Jan 14, 2022
Closed
@csweichel csweichel moved this to Scheduled in 🌌 Workspace Team Jan 21, 2022
@csweichel csweichel moved this from Scheduled to In Progress in 🌌 Workspace Team Jan 21, 2022
@csweichel csweichel mentioned this issue Jan 21, 2022
Merged
Repository owner moved this from In Progress to Done in 🌌 Workspace Team Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: content-service priority: highest (user impact) Directly user impacting team: workspace Issue belongs to the Workspace team type: improvement Improves an existing feature or existing code
Projects
No open projects
🌌 Workspace Team
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[content-init] Propagate sensible error messages gitpod-io/gitpod
1 participant
@csweichel