code-server: [Bug]: xz: (stdin): File format not recognized
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: chrome
- Local OS: Ubuntu 18.04.4
- Remote OS: Ubuntu 18.04.4
- Remote Architecture: amd64
code-server --version: v4.4.0 Latest
Steps to Reproduce
Follow the Development workflow: https://github.com/coder/code-server/blob/main/docs/CONTRIBUTING.md#development-workflow
- git clone https://github.com/coder/code-server.git
- git submodule update --init
- quilt push -a
- yarn
Expected
yarn install completed
Actual
code-server/node_modules/shellcheck: Command failed. Command: ./install.sh
xz: (stdin): File format not recognized
tar: Child returned status 1
Logs
$ yarn
yarn install v1.22.18
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @coder/logger@1.1.16" has unmet peer dependency "@google-cloud/logging@^4.5.2".
[5/5] Building fresh packages...
[1/3] ⠄ argon2
[2/3] ⠄ yarn
error /home/test/code-server/node_modules/shellcheck: Command failed.
Exit code: 2
Command: ./install.sh
Arguments:
Directory: /home/test/code-server/node_modules/shellcheck
Output:
xz: (stdin): File format not recognized
tar: Child returned status 1
Screenshot/Video
No response
Does this issue happen in VS Code?
- I cannot reproduce this in VS Code.
Are you accessing code-server over HTTPS?
- I am using HTTPS.
Notes
$ bsdtar --version
bsdtar 3.2.2 - libarchive 3.2.2 zlib/1.2.11 liblzma/5.2.2 bz2lib/1.0.6 liblz4/1.7.1
$ tar --version
tar (GNU tar) 1.29
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (5 by maintainers)
ok thank you so much!
at first, I tried building code-server on latest commit
1e304b1e7d3b5cd0edb1aa35edbbe74cd79254c2, but failed.Now I’ve git checkout
v4.4.0and now everything succeeded on Ubuntu 20.04! the commitc96202528fc0daf1339a55c45951f40834b72c95 (HEAD, tag: v4.4.0)works fine to me.by the way, if you guide me official Dockerfile for Ubuntu environment, it would be really helpful for the next time.
thank you so much for this amazing project. 😃
Yes, I ran steps 1-4 in the Development Workflow exactly. I would test again when I get home. Thank you!