Open
Conversation
Signed-off-by: Peter St. John <pstjohn@nvidia.com>
Contributor
Greptile SummaryThis PR fixes a dtype mismatch bug that occurred when creating Key changes:
The fix is straightforward and directly addresses the root cause. Tests now verify the fix works for both float32 and bfloat16 dtypes. Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 8061e42 |
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.
Previously layers would fail with
if you created a layer with dtype != float32. This ensures the dtype of the layernorm layers match those of the base attention layer.