This is a known issue and should be resolved in the nightly torchvision release as explained here.
torchvision