You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Spammy "TypedStorage is deprecated" warning on every epoch.
[23:52:12] WARNING [23:52:12] C:\omited\venv\lib\site-packages\torch\_utils.py:776: UserWarning: warnings.py:109
TypedStorage is deprecated. It will be removed in the future and UntypedStorage will
be the only storage class. This should only matter to you if you are using storages
directly. To access UntypedStorage directly, use tensor.untyped_storage() instead
of tensor.storage()
return self.fget.__get__(instance, owner)()
To Reproduce
Simply train a voice.
Additional context
I updated to 3.6.1 today and start seeing the issue. Unfortunately I didn't know what was last good known version.
I'm training a voice using CREPE F0 predictor and using PyTorch 2.0.0 in Windows 11 if that matters.
The text was updated successfully, but these errors were encountered:
From my understanding this is an issue with some library / package that this project is utilizing, as I can't find any usage of tensor.storage() or TypedStorage in general in the code
I don't know which package is using it and if it already has an updated version that uses UntypedStorage instead
This warning can be safely ignored for now as it shouldn't affect training 😁 (at least it doesn't for me)
I noticed that it's spamming it for every DataLoader instance... if you want to disable that warning, change the following line in your venv:
Line 316 in venv\lib\site-packages\torch\storage.py
Describe the bug
Spammy "TypedStorage is deprecated" warning on every epoch.
To Reproduce
Simply train a voice.
Additional context
I updated to 3.6.1 today and start seeing the issue. Unfortunately I didn't know what was last good known version.
I'm training a voice using CREPE F0 predictor and using PyTorch 2.0.0 in Windows 11 if that matters.
The text was updated successfully, but these errors were encountered: