Feature Request: Include stack trace of error in log

[thomas-neitmann]

Feature Idea

Instead of just printing the error in the log, include the stack strack in the log. Without this it's almost impossible to discover from the log file where the error originated.

Relevant Input

No response

Relevant Output

No response

Reproducible Example/Pseudo Code

No response

[parmsam-pfizer]

I agree that this would be really nice. We could also include the line number of the error using
options(show.error.locations = TRUE). Maybe we could use traceback() to get this info via options(error = traceback).

• https://rstats.wtf/debugging-r#traceback
• https://stackoverflow.com/questions/60475935/always-show-traceback-in-interactive-r
• https://stackoverflow.com/questions/1445964/how-to-get-r-script-line-numbers-at-error

[bms63]

Hey @thomas-neitmann - just wondering if Denali is using this package at all?

We have had some people reach out for really specific issues lately and want to make sure any updates we make don't impact folks.

[thomas-neitmann]

We are using it on a daily basis!

[bms63]

Awesome!! There shouldn't be any breaking changes for our early Spring release.

#275 and #270 could slightly change behavior for axecute but in the way that the axecute should perform as intended.