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.

Sign up for GitHub

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

Jump to bottom

fix(run): Prevent possible nil-pointers by always using Cut #1600

Merged
merged 1 commit into from
Apr 25, 2024
Merged

fix(run): Prevent possible nil-pointers by always using Cut #1600

merged 1 commit into from
Apr 25, 2024

Commits on Apr 25, 2024

  1. fix(run): Prevent possible nil-pointers by always using Cut 

    When parsing environmental variables in `kraft run`, which are
often presented in circumstances with strings with an equals
delimeter, the use of `SplitN` was not always checked for empty
values.  To prevent possible nil-pointers and to keep code
consistent, replace all areas where this type of procedure
occurs with `strings.Cut` instead.

Signed-off-by: Alexander Jung <alex@unikraft.io>
    @nderjung
    nderjung committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    60c9b53 View commit details
    Browse the repository at this point in the history