Fix: Replace assert statements with ValueError in runtime config validation - #8585
Open
mayuriphad wants to merge 1 commit into
Open
mayuriphad wants to merge 1 commit into
mayuriphad wants to merge 1 commit into
Conversation
…dation\n\nSigned-off-by: Mayuri <163738104+mayuriphad@users.noreply.github.com>
mayuriphad
force-pushed
the
fix-config-asserts
branch
from
September 19, 2026 12:56
063cc46 to
a7299e7
Compare
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
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 PR replaces the \�ssert\ statements in \deepspeed/runtime/config.py\ with explicit \if not (cond): raise ValueError(...)\ checks. Using asserts is unsafe here because when Python is executed with optimization enabled (\python -O), assertion statements are completely removed, bypassing critical runtime configuration validation. Fixes #8572.