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
While setting up the repository on Macs with M1, M2, and M3 chips, I encountered issues installing PyTorch. Although the README.md includes setup instructions, it lacks troubleshooting information for Macs with M-series chips, particularly regarding PyTorch installation. To help new contributors, I suggest adding a section to the README.md or creating a separate troubleshooting guide (e.g., TROUBLESHOOTING.md) with instructions for:
PyTorch installation issues on M1, M2, and M3 Macs.
Platform-specific tips and workarounds.
Common error resolutions for M-series chips.
This would help streamline the process for new contributors using Macs with M-series chips.
Proposed Solution:
Add troubleshooting information for PyTorch installation on M1, M2, and M3 Macs to the README.md or a new TROUBLESHOOTING.md file.
Include tips and workarounds for common issues faced on these Macs.
Tagging Relevant People: @prarabdhshukla – Requesting guidance on handling this issue and feedback on adding the troubleshooting guide.
The text was updated successfully, but these errors were encountered:
While setting up the repository on Macs with M1, M2, and M3 chips, I encountered issues installing PyTorch. Although the README.md includes setup instructions, it lacks troubleshooting information for Macs with M-series chips, particularly regarding PyTorch installation. To help new contributors, I suggest adding a section to the README.md or creating a separate troubleshooting guide (e.g., TROUBLESHOOTING.md) with instructions for:
Proposed Solution:
Add troubleshooting information for PyTorch installation on M1, M2, and M3 Macs to the README.md or a new TROUBLESHOOTING.md file.
Include tips and workarounds for common issues faced on these Macs.
Tagging Relevant People:
@prarabdhshukla – Requesting guidance on handling this issue and feedback on adding the troubleshooting guide.
The text was updated successfully, but these errors were encountered: