imsnif/diskonaut

Feature: error reporting with clean stacktraces

Open

#18 opened on Jun 17, 2020

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Rust (93 forks)github user discovery
help wanted

Repository metrics

Stars
 (3,066 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Right now, if the app panics, the stacktrace we see is very much messed up and hard to read, since the terminal is in "raw mode". It would be nice if we could catch all these errors, clear the terminal, exit raw mode and then print them to the screen.

Contributor guide

Research direction
Implement a custom panic hook that restores the terminal to cooked mode before printing the panic message and stack trace. Look into using `std::panic::set hook` and the `termion` or `crossterm` crate for terminal manipulation.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70