[Documentation:Developer] Add Troubleshooting Document #594
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview:
This pull request aims to improve the troubleshooting documentation related to setting up a MacBook Pro M3 with ARM64 architecture. After encountering a unique issue during my own setup process and confirming with the Submitty Zulip Community Discussion that this issue hasn't been encountered before, I decided to contribute to the project by documenting the steps to troubleshoot and resolve similar issues.
Changes Made:
Added a new section titled "SSH connection was unexpectedly closed" to the installation_troubleshooting.md file.
Purpose:
The purpose of this contribution is to:
Testing:
I have tested the troubleshooting steps provided in the documentation on my MacBook Pro M3 (ARM64) setup to ensure accuracy and effectiveness.
Additional Notes:
Feedback and suggestions for further improvements are welcome.