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
We've flipped the default for the weights_only argument in torch.load to True in pytorch/pytorch, see here for details + documentation and this is coming in torch 2.6.
This is expected to be quite a BC-breaking change, especially if any torch.load calls are not loading state_dicts of plain tensors.
We've flipped the default for the weights_only argument in torch.load to True in pytorch/pytorch, see here for details + documentation and this is coming in torch 2.6.
This is expected to be quite a BC-breaking change, especially if any torch.load calls are not loading state_dicts of plain tensors.
I see that
ignite
runs nightly CI as https://github.com/pytorch/ignite/pull/3299/files already addressed some of thetorch.load
calls in test cases.However, I see a couple other
torch.load
calls without weights_only explicitly set and wanted to double check that these are passing with the flip :) e.g.ignite/ignite/handlers/lr_finder.py
Line 515 in 0d8b8a1
and
ignite/ignite/handlers/param_scheduler.py
Line 848 in 0d8b8a1
The text was updated successfully, but these errors were encountered: