Closed thegamecracks closed 1 year ago
Tested with an older version of vscodium and this extension - worked like a charm; just updated both to the current one - still works fine.
How does your workspace file look like (I assume the file to search are included in there)? Does the log output show anything? Which node processes show up on the server after connecting to the remote workspace?
... just updated both to the current one - still works fine.
Double checked my versions, I'm running VSCodium 1.77.1 (user setup) with Open Remote - SSH v0.0.33.
How does your workspace file look like (I assume the file to search are included in there)?
The workspace folder is a clone of this repository: thegamecracks/thegamebot I also tried opening another folder and had the same issue of not seeing any search results.
Does the log output show anything? Which node processes show up on the server after connecting to the remote workspace?
Nothing I found notable in the console or log file:
console_output.txt
vscodium_server.log
ps axjf | grep "node"
: node_processes.txt
Curiously after reconnecting, my pyproject.toml tab doesn't appear in the search results as I haven't yet clicked on it to view its contents:
Hm, so you have a remote folder with that checkout, opened as "open folder"? I've just connected to a ssh machine, then opened a random folder, then tried search - and everything worked...
The node process list looks good.
Also rechecked here - using the default logging options the search is not logged anywhere - but I don't know how to enable logging there, maybe you can find something...
Found it from a vscode issue:
As GitMensch mentioned enabling trace logs will be helpful, also do you see any error in dev tools console? In any case this is not an issue with the open-remote-ssh extension, it's a vscodium/vscode related issue, maybe you are missing some dependency that's required by ripgrep 🤔
Now that you mention it, I also have this issue with VSCode and their remote ssh extension...
Searching works perfectly fine locally, and I can't recognize any fault during the
Figured out a likely cause after pruning through more logs, Extension Host (Remote) showed the ripgrep extension was failing due to my glibc version being 2.28 instead of 2.29/2.32/2.33/2.34:SearchService#search
Window trace logs. "search model building" records were a lot more frequent in the local test though.
2023-04-11 20:47:34.956 [debug] RipgrepSearchEH#search provideTextSearchResults thegamebot, {"folder":"file:///home/pi/thegamebot","excludes":["**/.git","**/.svn","**/.hg","**/CVS","**/.DS_Store","**/Thumbs.db","**/.trunk/*out","**/node_modules","**/bower_components","**/*.code-search"],"includes":[],"useIgnoreFiles":true,"useGlobalIgnoreFiles":false,"useParentIgnoreFiles":false,"followSymlinks":true,"encoding":"utf8","maxResults":20000,"previewOptions":{"matchLines":1,"charsPerLine":1000},"usePCRE2":false}
2023-04-11 20:47:34.959 [debug] RipgrepSearchEH#search /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg --hidden --ignore-case -g '!**/.git' -g '!**/.svn' -g '!**/.hg' -g '!**/CVS' -g '!**/.DS_Store' -g '!**/Thumbs.db' -g '!**/.trunk/*out' -g '!**/node_modules' -g '!**/bower_components' -g '!**/*.code-search' --no-ignore-parent --follow --crlf --fixed-strings --no-config --no-ignore-global --json -- 'thegamebot' '.'
- cwd: /home/pi/thegamebot
2023-04-11 20:47:34.988 [debug] RipgrepSearchEH#search /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.29' not found (required by /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg)
/home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.32' not found (required by /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg)
/home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.33' not found (required by /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg)
/home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.34' not found (required by /home/pi/.vscodium-server/bin/8311b9c0ddd6ed7738146332e5a0629c76f17be3/node_modules/@vscode/ripgrep/bin/rg)
As for actually getting it upgraded I'll have to figure that out as even the bullseye release only comes with glibc 2.31...
@thegamecracks You may could build that node module on the Pi yourself and replace the binary in that folder. @daiyam Do we have an option to self-build the node-module when building vscode-reh to decrease the dependency? Would there be other known modules with similar issues?
@GitMensch Thanks for the recommendation to replace the rg binary! I went with copying it from my package manager, but taking it from a fresh @vscode/ripgrep installation also fixed the search functionality.
As it seems, my remote workspace does not get fully indexed when displaying search results from the search tab. The results update correctly when I open another file in the same workspace containing the search term, and equally disappear once the file is closed. Toggling exclusion rules and trying different inclusion paths does not affect the results.
Opening a second file and re-running the search: