[NPMCLI-66] Improve crash handling with next steps and more informations Created: 17/Jan/17 Updated: 02/Feb/17 Resolved: 25/Jan/17 |
|
| Status: | Closed |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Robert Kowalski | Assignee: | Robert Kowalski |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | CLI: Help users get started |
| Sprint: | Basel 80 |
| Story Points: | 5 |
| Description |
|
Right now the Command Line Client dumps the stack trace on a hard crash, which helps to find the root cause of the issue. To improve the users life and developers life we can improve our error handling: Additonally add informations to the stacktrace about:
The idea is that even if we crash and things get messed up, the user gets at least help in our issue tracker (worst case scenario) - which is better than nothing. |