Skip to content

Conversation

@awdeorio
Copy link
Contributor

Add a few troubleshooting items suggested in 3 issues.

Closes #204, closes #209, closes #231

@awdeorio
Copy link
Contributor Author

@hardy-ethan I would value your feedback if you can take a look. You created some of the issues.

@github-actions
Copy link

github-actions bot commented Dec 19, 2025

The spec from this PR is available at https://preview.sesh.rs/previews/eecs280staff/tutorials/241/.

(Available until Wed Jan 21 2026.)

@hardy-ethan
Copy link
Contributor

hardy-ethan commented Dec 19, 2025 via email

Copy link
Contributor

@jamesjuett jamesjuett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a typo fix commit and a few minor suggestions.

@hardy-ethan
Copy link
Contributor

I'll reply to Prof. Juett's comments for the other two issues, but for here:

#204

I'm thinking that in the case where the user has VSCode installed in the Downloads folder, they probably had it installed from a previous class or project, and might not remember that it's in the Downloads folder. It might be easier for them to look for the error message that VSCode shows:

Cannot update while running on a read-only volume. The application is on a read-only volume. Please move the application and try again. If you're on macOS Sierra or later, you'll need to move the application out of the Downloads directory. This might mean the application was put on quarantine by macOS. See this link for more information.

Maybe like (remove, add)

Installed to Downloads Cannot update while running on a read-only volume

VSCode may think the system is read only and fail to update if it is installed in the Downloads folder.

Probably should've included that error text in my original issue...

@awdeorio awdeorio requested a review from jamesjuett December 19, 2025 19:47
@awdeorio
Copy link
Contributor Author

Thanks for the feedback. I think I got it all. Take another look.

@hardy-ethan
Copy link
Contributor

Thanks for the feedback. I think I got it all. Take another look.

For #204 I only put the bolding to show that it was an addition, but if you think it looks good in the text feel free to keep 😂

Planning on testing the two other issues on a Windows install if I can get one running

Copy link

@jkloosterman jkloosterman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not able to test myself but looks reasonable

Copy link
Contributor

@jamesjuett jamesjuett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@hardy-ethan
Copy link
Contributor

hardy-ethan commented Dec 19, 2025

Tested on a fresh Windows VM:

#209 works fine with and without the WSL distro running
#231 the wsl --install command blocks CTRL + C at this phase. Closing the terminal window works, so we could tell the students to do that instead

@awdeorio
Copy link
Contributor Author

the wsl --install command blocks CTRL + C at this phase. Closing the terminal window works, so we could tell the students to do that instead

Done! Thanks for testing this. 1bebad3

@awdeorio awdeorio merged commit ea42c37 into main Dec 22, 2025
1 check passed
@awdeorio awdeorio deleted the troubleshooting branch December 22, 2025 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider warning about storing VSCode in ~/Downloads WSL Tutorial Nuclear Option Add Troubleshooting for Being Stuck on Enabling Features for WSL

5 participants