volta-cli/volta

investigate a way to get backtraces independent of RUST_BACKTRACE

Open

#75 opened on May 17, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (8,309 stars) (189 forks)batch import
enhancementgood first issue

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

Tech stack
rust
Domain
developer experience
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rustfailure crateerror handling basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the failure crate's documentation and source code for methods to capture backtraces without relying on RUST BACKTRACE. Look at Cargo.toml to see the version of failure used and check if there are any forked versions or alternative crates like backtrace. Review any existing error handling code in the repository, such as in the src/error.rs or similar files. The issue requests a mechanism that works independently of the environment variable, so focus on crate features or compile time flags.