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

fix(core): always pass ngx.ctx to log_init_worker_errors #13731

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bungle
Copy link
Member

@bungle bungle commented Oct 7, 2024

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

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

@github-actions github-actions bot added the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Oct 7, 2024
Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
@bungle bungle force-pushed the fix/pass-ctx-to-log-init-worker-errors branch from 467a6e4 to 7a77881 Compare October 7, 2024 17:02
Copy link
Contributor

@ADD-SP ADD-SP left a 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.
Copy link
Contributor

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?

Copy link
Member Author

@bungle bungle Oct 9, 2024

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 expect 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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants