-
Notifications
You must be signed in to change notification settings - Fork 65
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
[MM-54551] Fix potential nil dereference panic #532
Conversation
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.
Huh. Guess we do need to always check that. Thanks!
Any idea why it's returning a nil config? |
Not sure but I think the returned setting is nil, not the config because I had the reporting user setting it to |
Also to note, what made debugging this worse was that until we enabled DEBUG level logs we couldn't get the plugin panics to show. Something to review on the server most likely. |
Yeah, currently it's something handled by the framework (https://mattermost.atlassian.net/browse/MM-54562), unless we start to implement recovers, something I tried to avoid so far. |
* [MM-54520] Soft fail in case of missing post during state cleanup (#530) * Soft fail in case of missing post during state cleanup * Add validity check on postID * Fix potential nil dereference panic (#532) --------- Co-authored-by: Claudio Costa <[email protected]>
Summary
We had a report of failures to join calls starting in v0.19. At first it looked like a networking issue but upon further inspection of the logs we were able to find multiple plugin crashes due to SIGSEGV.
Even if properly set to
false
inconfig.json
the returned object was a nil pointer. Adding a couple of extra checks to avoid future regressions.Given the severity of this I'd like to cut a new dot release once this is merged.
Ticket Link
https://mattermost.atlassian.net/browse/MM-54551