Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

v4.9.0-rc.2 #5824

Nov 30, 2022 · 1 comments · 5 replies
Discussion options

Code v1.73.1

This is the second pre-release for v4.9.0.

To install via the install script, pass the --edge flag.


This discussion was created from the release v4.9.0-rc.2.
You must be logged in to vote

Replies: 1 comment 5 replies

Comment options

Linux users: could you check to make sure the Terminal works? I tested on macOS and didn't see any issues.

cc @benz0li

You must be logged in to vote
5 replies
Comment options

The issue with /opt/code-server/lib/vscode/product.json1 remains. It should have permissions 644 not 600.
i️ Tested with code-server v4.9.0-rc.2 (code-server-4.9.0-rc.2-linux-amd64.tar.gz)

Cross reference: #5769 (comment)

Footnotes

  1. /opt/code-server: Installation path

Comment options

code-server v4.9.0-rc.2 (code-server-4.9.0-rc.2-linux-amd64.tar.gz; fixed version with CS_DISABLE_GETTING_STARTED_OVERRIDE=1 set) is deployed at https://coder.jupyter.b-data.ch; Image R (base:test-devtools).

Functionality [modified by patches] tested and found to work:

  • base-path
  • cli-window-open
  • local-storage
  • marketplace
  • proxy-url
  • service-worker
  • webview

Jupyter Notebooks also work fine:

  • ms-toolsai.jupyter@2022年10月11日0
  • ms-python.python@2022182
Comment options

The issue with /opt/code-server/lib/vscode/product.json1 remains. It should have permissions 644 not 600.

Interesting 🤔 I wonder how that happened. I will update in #5772 and then ping you to help test.

Comment options

This is normally something I'd ping @code-asher for help with but he is out until next week. I think this should do it: fc4d2b5

I ran build:vscode locally and checked permissions with: stat -f%p product.json and got 100755 so I think that should fix it? I'm not certain though.

CI is building and when it's done we'll have the npm artifact.

If you need me to do another release-candidate for testing, let me know.

Comment options

I guess it's probably best to do a release candidate then others can test too. Plus it tests in the same way (linux-amd package) vs. the npm artifact in CI. I'll do that now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants

AltStyle によって変換されたページ (->オリジナル) /