-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix(core): always pass ngx.ctx
to log_init_worker_errors
#13731
Conversation
Signed-off-by: Aapo Talvensaari <[email protected]>
467a6e4
to
7a77881
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you attach a Jira Ticket to this PR?
@@ -0,0 +1,4 @@ | |||
message: | | |||
Fix to always pass `ngx.ctx` to `log_init_worker_errors` as otherwise it may runtime crash. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this msg is very technical, could you make it more customer-friendly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ADD-SP there is no way to make it customer friendly. Thus I was thinking about removing the whole changelog. But then I though people start complaining that it is not there. It is internal change that I am not sure has anyone except me hit. If you are looking after something like "Made Kong more robust when logging errors when starting a node". Then customers start to ask "how it is now more robust, should I know more about this".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it's perfectly fine to leave internal changes off the changelog.
Successfully created cherry-pick PR for |
Signed-off-by: Aapo Talvensaari <[email protected]> (cherry picked from commit fd7ea93)
Summary
Just saw this on my local machine when started to kill -9 worker processes on a control plane. So just a tiny fix here. Not sure how easy this is to test, but it is quite an obvious fix and bug. Without this the
log_init_worker_errors
may runtime crash.Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.md