question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

UX: Unclear error message: See more in "Output".

See original GitHub issue

Is your enhancement related to a problem? Please describe.

While reproducing steps of #15185 it didn’t work at all to run my code:

image

The message See more in "Output" is not helpful. What output? Where is “output”?

Describe the solution you’d like

ideas:

  • Include details directly in notification
  • or make “Output” clickable and navigate to output.

Environment / Steps to reproduce

  • Login to https://che.openshift.io/
  • Create new workspace
  • Use “Python Django” template
  • Wait
  • Click on the right side “box” icon: “My Workspace”
  • Click “install dependencies” (sometimes works, sometimes does nothing, sometimes the error as described above)

P.S. after finding “output” I probably should report the issue itself as well but this ticket is just about the error message itself being not helpful.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
RomanNikitenkocommented, Nov 20, 2019

I think this notification was provided within https://github.com/eclipse/che/issues/13980 So, user should open View=>Output for more details, not task output. @akurinnoy please correct me if I’m wrong

I think we can improve the behavior and provide button Output for this notification which will open the corresponding view with output. Something like we have for another warning:

task_warning

0reactions
che-botcommented, Jul 19, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Best 10 Examples And Guidelines For Error Messages
Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of...
Read more >
Error Messages: Examples, Best Practices & Common Mistakes
UX Movement talks about this in their article on making error messages more reassuring: Error summaries magnify the seriousness of the mistakes ......
Read more >
How to design and convey error messages properly - Bootcamp
The next step can be contextually-relevant actions. Actions are possible routes to solve the problem.
Read more >
Error Message Guidelines - Nielsen Norman Group
Established wisdom holds that good error messages are polite, precise, and constructive. The Web brings a few new guidelines: Make error messages clearly ......
Read more >
How to Write & Design User-Friendly Error Messages
Quick tip: A good way to incorporate a more human tone in error message UX design is to think about explaining them out...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found