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.

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

Already on GitHub? Sign in to your account

Improve panic reporting #333

Open
flowchartsman opened this issue Feb 3, 2021 · 1 comment · May be fixed by #436
Open

Improve panic reporting #333

flowchartsman opened this issue Feb 3, 2021 · 1 comment · May be fixed by #436
Labels

Comments

@flowchartsman
Copy link

From a UX perspective, "Error: runtime error: invalid memory address or nil pointer dereference" is not particularly helpful if I've made a mistake in my magefile that causes a panic, since there's zero context to localize it. Though I appreciate the desire to keep error message parsimonious in a build tool, it would be super helpful if I could get a full stacktrace when running with -debug or at least the relevant location of the panic without -debug

@natefinch
Copy link
Member

yeah 100%. I think this is just not a flow I have spent a lot of time on. Just dumping the regular panic message shouldn't be too hard.

@jespino jespino linked a pull request Jul 28, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants