-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make get_bounds_as_ndarray
device safe
#1567
Conversation
This pull request was exported from Phabricator. Differential Revision: D42060124 |
Codecov Report
@@ Coverage Diff @@
## main #1567 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 153 153
Lines 13562 13562
=========================================
Hits 13562 13562
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for cleaning this up
Should we add a test for this on both CPU and GPU? |
Summary: Pull Request resolved: pytorch#1567 Issue raised in pytorch#1566. The `bounds` can be a `Dict[str, Tuple[Tensor, Tensor]]` where the tensors live on GPU, which leads to a device error when trying to assign them to a numpy array. Reviewed By: Balandat Differential Revision: D42060124 fbshipit-source-id: 549a0f220edcc34ecdeb2813a2978bde7cab4b6c
2df50ae
to
d01be04
Compare
This pull request was exported from Phabricator. Differential Revision: D42060124 |
This pull request has been merged in 6d120db. |
Summary:
Issue raised in #1566.
The
bounds
can be aDict[str, Tuple[Tensor, Tensor]]
where the tensors live on GPU, which leads to a device error when trying to assign them to a numpy array.Differential Revision: D42060124