Harshit
Results
1
comments of
Harshit
there's an uupdate of torchmetrics to 1.0.0 that's happened 3 hours back that's causing this. specifying **torchmetrics==0.11.4** in the packages list within the Setup section fixed it for me.