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

Jump to bottom

Thrown errors should disclose from where they come #1503

Closed
nezbite opened this issue Sep 1, 2022 · 0 comments · Fixed by #1510
Closed

Thrown errors should disclose from where they come #1503

nezbite opened this issue Sep 1, 2022 · 0 comments · Fixed by #1510

Comments

@nezbite
Copy link
Contributor

nezbite commented Sep 1, 2022

Example:
When using minio-hs and not adding the keys as environment variables, minio throws MErrVMissingCredentials.
When running the prod server, it looks like this:

RunProdServer: MErrVMissingCredentials

It would be useful if we could add information about which module/package throws this error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added callstacks to exceptions thrown during config digitallyinduced/ihp
1 participant
@nezbite