Conversation
drisspg
added a commit
that referenced
this pull request
Mar 30, 2026
stack-info: PR: #2411, branch: drisspg/stack/31
045d65c to
7813484
Compare
v0i0
reviewed
Mar 30, 2026
v0i0
approved these changes
Mar 30, 2026
stack-info: PR: #2411, branch: drisspg/stack/31
7813484 to
57ab696
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.
Various bug fixes / enable subtile > 2
get_sparse_q_block_sizethis ideally just returns None if no sparsity or the set size from input. I am like 99% all things have been swapped to using the explicit setting of blocksparse data. We have switch over already in PT but want to give it 1 more release so we still infer just in case.dQ_single_wgso I fixed to use the correct wg count