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

Backport of Add stack trace to audit logging panic recovery into release/1.12.x #18166

Merged

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #18121 to be assessed for backporting due to the inclusion of the label backport/1.12.x.

The below text is copied from the body of the original PR.


Adds a stack trace to the logs when we recover from a panic, otherwise we only get the panic error string, and no code location for where it came from.

The only other bit of production code we add a recover to is:

if r := recover(); r != nil {

It wasn't clear to me that we would want a stack trace in that instance, so I've left it alone.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/add-audit-panic-stack/randomly-hot-goose branch from 6b2dd76 to 9c03afc Compare November 30, 2022 17:59
@tomhjp tomhjp enabled auto-merge (squash) November 30, 2022 17:59
@tomhjp tomhjp merged commit c889121 into release/1.12.x Nov 30, 2022
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

Successfully merging this pull request may close these issues.

2 participants