Host of issues after upgrading to v3.6.1

[agneevX]

• Web Browser: Safari
• Local OS: macOS
• Remote OS: Raspberry Pi OS Debian Buster
• Remote Architecture: armv7l
• Version: 3.6.1 62735da69466a444561ab9b1115dc7c4d496d455

Ever since I upgraded to v3.6.1, I've not been able to use code-server properly.

1. Most of the time I get Activating Extensions in the status bar
2. Open Preview to the side won't open
3. Color theme get randomly reset upon refresh (Theme resets to default on relaunch #2231)

Browser console log:

[agneevX]

Meanwhile, downgrading to v3.6.0.

sudo npm install -g [email protected] --unsafe-perm

[Talent30]

same issue

[ghokun]

Most of the reported problems applies for me. One thing I might add:
.vscode/launch.json is not recognized in 3.6.1 and can not create new one.

[Talent30]

#2262

[Talent30]

#2259

[agneevX]

I'm quite surprised as to why 3.6.1 hasn't been pulled yet. @code-asher

[code-asher]

It seems these issues are related to Safari and how VS Code now loads the web worker extension host. It looks like they have a fix in the works which I think should be out with the next version (probably the next week or two). I'm hesitant to pull the release since it doesn't affect other browsers and because the last time I did that I broke things downstream. >.<

[ykazakov]

Looks like the issues are still there in v3.7.1

[code-asher]

Yeah, unfortunately. :( I think they'll be resolved once we upgrade to VS Code 1.51.1 though which I'm currently working on. I'll update this issue once that's merged.

[code-asher]

It seems there are still issues after the upgrade (different ones though). Will need to dig further.

[izewang]

issues are still there in v3.7.2

[ghokun]

My issues seem to be fixed with the 3.7.3. Thanks

• Settings are persistent
• launch and tasks files under .vscode are visible to debugger

[ykazakov]

My plugin activation issues #2243 have been fixed as well! 👍

[agneevX]

Reopening this since there’s an active milestone.

[oxy]

It's closed even though the milestone is active because the issue is technically fixed on the latest development version - it helps because it shows up as a completed task on the milestone.

Closing again!