-
Notifications
You must be signed in to change notification settings - Fork 5.9k
[Bug]: ripgrep giving segfault and quietly making searches fail #5322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We've definitely had issues before with @code-asher any ideas? |
I think we would need to look into how exactly this installs
code-server. Is there a recipe somewhere? I have no experience
with conda.
|
Thank you for the link!
It appears to download the standalone releases from GitHub so I
tried replicating by downloading and running it on an Ubuntu host:
```
$ wget
https://github.com/cdr/code-server/releases/download/v4.5.0/code-server-4.5.0-linux-amd64.tar.gz
$ tar -xf *.tar.gz
$ ./code-server-4.5.0-linux-amd64/bin/code-server --auth none
```
Then I opened code-server in a browser and successfully ran a
search.
The recipe seems to get rid of the packaged Node. Does it use the Node
installed on the system instead maybe? What does `node --version`
give you?
|
It requires (and installs) 16.X. The installed version is 16.14.2. |
Ah, I was thinking that since the `code-server` script Conda
installs invokes plain `node` then depending on your path or the
last version of Node you installed it could be the wrong version.
But I realized that ripgrep segfaults when you run it directly so
the version of Node has nothing to do with this anyway.
The sha256 does not match the release on GitHub so I am not sure
what happened to it. There might be another part to the Conda
build process I am missing.
```
9b85e1a11cd624e775ab33e6b7e86fe60844f534be89d04b34a17cebf6ccc611
/home/coder/miniconda3/share/code-server/lib/vscode/node_modules/@vscode/ripgrep/bin/rg
80e049a3e46689b4fdee6b70bb02ee748a6ab88f6f4853753f23ae4aa2a7e958
/home/coder/code-server-4.5.0-linux-amd64/lib/vscode/node_modules/@vscode/ripgrep/bin/rg
```
Edit: fixed the paths; GitHub mangled them thinking they were email addresses.
|
I was going to say that checksum mismatches on the binaries are not surprising, since conda builds everything from source. However, that's clearly not what's happening here. Something is very wrong:
|
Hello, just a heads up, I believe this issue was being caused by the conda build system and has been resolved as of last week, please test the conda-forge package if you can. more info here: conda-forge/code-server-feedstock#100 |
Thank you for the heads up! |
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.5.0Steps to Reproduce
code-server
in the remote machine via conda-forge (mamba install code-server=4.5.0
)Expected
rg
, the binary executes (i.e. if you just execute/path/to/conda/env/share/code-server/lib/vscode/node_modules/@vscode/ripgrep/bin/rg
, you should get an error that no arguments were required - which is expected)Actual
rg
executes.Logs
Having trouble finding relevant logs doing this, but I have confirmed that if I install a working version of ripgrep (i.e. via
mamba install ripgrep
and then replace the segfaulting binaryrg
inside ofshare/code-server/lib/vscode/node_modules/@vscode/ripgrep/bin
with a symlink to this working version (which I tried based on #5216) then the search functionality works fine. So I'm pretty sure this is the source of the issue. I just don't know WHY that binary gives a segfault.Screenshot/Video
No response
Does this issue happen in VS Code or GitHub Codespaces?
Are you accessing code-server over HTTPS?
Notes
No response
The text was updated successfully, but these errors were encountered: