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

Capturing call stack information #101

Open
JackKelly-Bellroy opened this issue Sep 28, 2021 · 0 comments
Open

Capturing call stack information #101

JackKelly-Bellroy opened this issue Sep 28, 2021 · 0 comments

Comments

@JackKelly-Bellroy
Copy link
Contributor

This may not be possible right now, but I wanted to log information that I found.

At time of writing, hal does not report a call stack on lambda errors:

setRequestBodyLBS (encode (LambdaError { errorMessage = e, stackTrace = [], errorType = "User"}))

It would be nice if it did, but it's not obvious how with the current exception machinery. There's a trick but it probably means enumerating all known exception types with no obvious extensions, so maybe we consider this blocked until the decorate exceptions with backtrace information proposal is implemented, and gate that feature behind appropriate CPP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant