Skip to content

Prevent exchange logging crash (backport #12104) #12105

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

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 23, 2024

This is #12100 by @gomoripeti submitted by me so that Actions can run with access to GCP Bazel cache.


This is an automatic backport of pull request #12104 done by Mergify.

Don't let the `log` callback of exchange_logging handler crash,
because in case of a crash OTP logger removes the exchange_logger
handler, which in turn deletes the log exchange and its bindings.

It was seen several times in production that the log exchange suddenly
disappears and without debug logging there is no trace of why.

With this commit `erlang:display` will print the reason and stacktrace
to stderr without using the logging infrastructure.

(cherry picked from commit 34bcb91)
@michaelklishin michaelklishin merged commit e60d512 into v4.0.x Aug 23, 2024
197 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.0.x/pr-12104 branch August 23, 2024 13:05
michaelklishin added a commit that referenced this pull request Aug 23, 2024
Prevent exchange logging crash (backport #12104) (backport #12105)
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