Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature] Backtracing Errors #1204

Closed
gluax opened this issue Jul 27, 2021 · 0 comments 路 Fixed by #1242
Closed

[Feature] Backtracing Errors #1204

gluax opened this issue Jul 27, 2021 · 0 comments 路 Fixed by #1242
Assignees
@gluax
Labels
feature A new feature. priority-high A high priority bug/task in Leo.

Comments

@gluax
Copy link
Contributor

gluax commented Jul 27, 2021

馃殌 Feature

When an environment flag is set, we should use the backtrace crate for errors as suggested by @0rphon.

Motivation

This is a convenience option similar to RUST_BACKTRACE that Leo developers could make use of to generate a backtrace without having to make a codebase change to generate a backtrace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gluax gluax

Labels
feature A new feature. priority-high A high priority bug/task in Leo.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP Implementation] Better Errors ProvableHQ/leo
1 participant
@gluax