Bug: Fix device/dtype mismatch in DetaForObjectDetection bias initialization . #40869
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
|
I think this is a duplicate of #40878 ! |
|
@Rocketknight1 Thanks ! Should I close this PR. |
|
Yeah, I'll close it. Thanks for the PR anyway - your fix was good, it's just unfortunate that someone at Hugging Face was working on it too! |
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.
#40853
This PR fixes a bug that prevented DETA object detection models from loading in recent Transformers versions due to a device/dtype mismatch when initializing self.class_embed.bias.data. The fix ensures the tensor is created on the correct device and with the correct dtype, resolving error .
Please let me know if my approach or fix needs any improvements . I’m open to feedback and happy to make changes based on suggestions.
Thankyou !