volta-cli/volta

investigate a way to get backtraces independent of RUST_BACKTRACE

Open

#75 opened on May 17, 2018

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Rust (189 forks)batch import
enhancementgood first issue

Repository metrics

Stars
 (8,309 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Backtraces would be useful for verbose diagnostics, not just for Volta maintainers. But we don't want to require Volta users to know about the RUST_BACKTRACE environment variable (and it could cause nasty interactions between Volta and other software written in Rust). Investigate if there are mechanisms for getting backtraces in the failure library (or a fork of failure) without being sensitive to that environment variable.

Contributor guide

Research direction
Investigate the failure crate's backtrace handling to see if it provides APIs to enable backtraces independently of the RUST BACKTRACE environment variable. If not, explore forking or patching failure to add such functionality.
Tech stack
rust
Domain
clideveloper experience
Issue type
Research
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.
1-3 hours
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.
50