Null JIT kernel launch config#1974
Merged
rapids-bot[bot] merged 1 commit intorapidsai:release/26.04from Apr 1, 2026
Merged
Conversation
divyegala
added
bug
dantegd
approved these changes
Mar 31, 2026
Member
Author
|
/merge |
rapids-bot
bot
merged commit 6e688b3
into
rapidsai:release/26.04
178 of 183 checks passed
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
2 participants
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 is to ensure the config does not accidentally get corrupted or start with garbage values. Furthermore, the CUDA docs recommend setting
config.attrs = nullptreven ifconfig.numAttrs = 0.The need of this update comes from rapidsai/cuml#7906, where in cuML nightly wheel tests we are intermittently observing CUDA context corruption from the JIT path. While I am not sure if this PR will resolve them, it is still a step in the right direction.