You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Print stack traces for -ldebug or -ltrace by default #19986
Is your feature request related to a problem? Please describe.
When a user runs into a problem like #19979, it's sensible to increase logging, e.g. passing -ldebug or -ltrace. But this doesn't show all info that's potentially relevant, because (AIUI) full stack traces are only shown via the separate flag --print-stacktrace.
Describe the solution you'd like
Maybe we could make this a bit smoother by implicitly enabling stack trace printing at more verbose log levels (DEBUG or TRACE).
Describe alternatives you've considered
Alternatively, we log stack traces at DEBUG level so they automatically show up for -ldebug, as an orthogonal aspect to --print-stacktrace.
I'd lean towards the DEBUG level, seeing as trace is likely overkill in most cases for end-users (risk they drown in log output rather than finding the issue)
This issue has been open for over one year without activity and is not labeled as a bug. It has been labeled as stale to invite any further updates. If you can confirm whether the issue is still applicable to the latest version of Pants, appears in other contexts, or its priority has changed, please let us know. Please feel free to close this issue if it is no longer relevant.
Activity
kaos commentedon Oct 6, 2023
I'd lean towards the DEBUG level, seeing as trace is likely overkill in most cases for end-users (risk they drown in log output rather than finding the issue)
github-actions commentedon Oct 31, 2025
This issue has been open for over one year without activity and is not labeled as a bug. It has been labeled as stale to invite any further updates. If you can confirm whether the issue is still applicable to the latest version of Pants, appears in other contexts, or its priority has changed, please let us know. Please feel free to close this issue if it is no longer relevant.