Vscode: Search - Spawn EACCES

[yuri1969]

• VSCode Version: 1.11.2
• OS Version: Linux gentoo 4.4.39-gentoo
• no extensions (~/.vscode) and nuked ~/.config/Code

Steps to Reproduce:

1. Open Folder
2. Ctrl + Shift + F
3. type any phrase; hit Enter
4. Warn spawn EACCES pops up
5. No search results from the selected folder displayed

There is no spam in console apart from:

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

[roblourens]

Not sure why it can't spawn ripgrep, but you can probably work around it by setting "search.useRipgrep": false.

[yuri1969]

@roblourens Thanks! Search works with disabled _ripgrep_. I'm ok with legacy grep, I guess...

[roblourens]

@yuri1969 Is this still an issue in the latest version? Have you tried again with ripgrep?

[yuri1969]

@roblourens I can confirm that the ripgrep works in _Version 1.17.1_.

[roblourens]

Thanks!

[uhrm]

I've installed VS Code 1.18.0 (Gentoo Linux), and experienced this issue (for the first time). Maybe it is reintroduced again?

Doing a
chmod a+x /opt/vscode-1.18.0/resources/app/node_modules/vscode-ripgrep/bin/rg
fixed the problem.

[tempit]

I've just spent several hours on the same issue when trying to build my extension - the .vscode-test folder got populated with 1.18.0 and had throw a ripgrep-related EACCESS error.
1.17.2 and previous versions worked fine.
Can confirm the workaround does indeed work, thanks @uhrm - that saved much digging time.

[AlexShemeshWix]

Thanks it fixed my problem.

[CryZe]

That fixed my problem too.

[tempit]

This fails to work in CI when running extension tests, however, as the test script that comes with vscode downloads vscode and immediately runs tests, leaving no place to chmod in between.
@yuri1969 , can the issue be reopened? This needs a fix on vscode side.

[yuri1969]

Currently, I have got no issue on my machine - the latest snapshot of Gentoo + VSCode 1.18.0 via _jorgicio_ layman.

However, it seems the problem persists for another fellow Gentoo users. @tempit The issue has been reopened.

[tempit]

@yuri1969 - I opened a new issue, realizing our CI machine was ubuntu after all.
You can close this one if it no longer occurs. Thanks!

[yuri1969]

Closing as @tempit requested.