Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[AIR] Torch UserWarning during training #28003

Closed
bveeramani opened this issue Aug 18, 2022 · 1 comment · Fixed by #29808
Closed

[AIR] Torch UserWarning during training #28003

bveeramani opened this issue Aug 18, 2022 · 1 comment · Fixed by #29808
Assignees
@krfricke
Labels
bug Something that is supposed to be working; but isn't P1 Issue that should be fixed within a few weeks

Comments

@bveeramani
Copy link
Member

What happened + What you expected to happen

I ran TorchTrainer.fit and got an unexpected warning:

(RayTrainWorker pid=3415) /Users/bveeramani/GitHub/ray/python/ray/air/_internal/torch_utils.py:122: UserWarning: The given NumPy array is not writable, and PyTorch does not support non-writable tensors. This means writing to this tensor will result in undefined behavior. You may want to copy the array to protect its data or make it writable before converting it to a tensor. This type of warning will be suppressed for the rest of this program. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/torch/csrc/utils/tensor_numpy.cpp:178.)

Versions / Dependencies

Ray: 7d981d6

Reproduction script

See "Training a Torch classifier" example.

Issue Severity

Low: It annoys or frustrates me.
@bveeramani bveeramani added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) air labels Aug 18, 2022
@bveeramani bveeramani changed the title [AIR] NumPy UserWarning during training [AIR] Torch UserWarning during training Aug 18, 2022
@bveeramani bveeramani mentioned this issue Aug 18, 2022
Closed
7 tasks
@bveeramani bveeramani assigned bveeramani and unassigned bveeramani Sep 7, 2022
@matthewdeng
Copy link
Contributor

@krfricke can you take a look and see what is raising this warning, and if we should just entirely mute it?

@krfricke krfricke mentioned this issue Oct 28, 2022
Merged
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@krfricke krfricke

Labels
bug Something that is supposed to be working; but isn't P1 Issue that should be fixed within a few weeks
Projects
None yet
Milestone
No milestone
3 participants
@matthewdeng @krfricke @bveeramani