volta-cli/volta

investigate a way to get backtraces independent of RUST_BACKTRACE

Open

#75 创建于 2018年5月17日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Rust (8,309 star) (189 fork)batch import
enhancementgood first issue

描述

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.

贡献者指南

技术栈
rust
领域
developer experience
议题类型
research
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Rustfailure crateerror handling basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
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.
investigate a way to get backtraces independent of RUST_BACKTRACE · volta-cli/volta#75 | Good First Issue