Fix panic in NewSystemd on nil values #219
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NewSystemd previously panicked if it was given a nil resource value for
resources.Memory.Max or resources.CPU.Weight (if resources.CPU or
resources.Memory is non-nil)
This also checks the value of Max and Weight before dereferencing them.
Previous to this change, the unit tests I added would fail like this:
cpu: