trim extraneous whitespaces when parsing comma-separated config sources #1535
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 20254570483Details
💛 - Coveralls |
tariq1890
force-pushed
the
trim-space-config-sources
branch
from
25fa21b to
c966833
Compare
elezar
reviewed
Dec 11, 2025
elezar
reviewed
Dec 11, 2025
Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
tariq1890
force-pushed
the
trim-space-config-sources
branch
from
c966833 to
b0e6010
Compare
cdesiniotis
approved these changes
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change makes the input parsing of the
RUNTIME_CONFIG_SOURCESa bit more forgiving. It is not impossible that users may specify a space when specifying comma separated list of container runtime config sources