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

Allow nvidia-ctk config --set to accept comma-separated lists #969

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

Conversation

elezar
Copy link
Member

@elezar elezar commented Mar 7, 2025

The urfave update to v2.27.6 fixes the behaviour when disabling a separator for repeated StringSliceFlags. This change updates the nvidia-ctk config command to allow list options to be specified as comma-separated values.

The urfave update to v2.27.6 fixes the behaviour when disabling a separator
for repeated StringSliceFlags. This change updates the nvidia-ctk config
command to allow list options to be specified as comma-separated values.

Signed-off-by: Evan Lezar <[email protected]>
@ArangoGutierrez ArangoGutierrez requested a review from Copilot March 7, 2025 14:50

Choose a reason for hiding this comment

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

PR Overview

This PR updates the nvidia-ctk configuration command to allow list options to be specified as comma-separated values. It refactors the list-splitting logic in the config module and disables the automatic slice flag separator in the CLI application.

  • Refactored list splitting in config.go to check both the provided separator and comma.
  • Disabled the slice flag separator in main.go to ensure comma-separated list support.

Reviewed Changes

File Description
cmd/nvidia-ctk/config/config.go Updated list splitting logic to support comma-separated values.
cmd/nvidia-ctk/main.go Disabled the slice flag separator in the CLI to complement the new behavior.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants