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

configs/configupgrade: fix panic on nil hilNode #22181

Merged
merged 1 commit into from
Jul 23, 2019

Conversation

mildwonkey
Copy link
Contributor

In some cases (see #22020 for a specific example), the parsed hilNode
can be nil. This causes a series of panics. Instead, return an error and
move on.

This does not try to identify why the returned hilNode is nil, it just returns an error.

Fixes #22020

In some cases (see #22020 for a specific example), the parsed hilNode
can be nil. This causes a series of panics. Instead, return an error and
move on.
@mildwonkey mildwonkey requested a review from a team July 23, 2019 15:37
Copy link
Contributor

@pselle pselle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested this locally and WFM!

@mildwonkey mildwonkey merged commit 66f4a48 into master Jul 23, 2019
@mildwonkey mildwonkey deleted the mildwonkey/b-configupgrade-panic branch July 23, 2019 17:05
@ghost
Copy link

ghost commented Aug 23, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to run 0.12upgrade
2 participants