Levi Zim

> I've tested the server on macOS (node-v20) and linux x64 (node-v16, node-v18, node-v20) and I don't have the issue. I tested by symlinking nodejs 22 binary from Arch Linux...

I opened PR #2061 to fix it. Let's wait for the CI. > Btw. there is a rg binary installed, but the x86 (32 Bit) version Yes. Microsoft will fallback...

> > > Btw. there is a rg binary installed, but the x86 (32 Bit) version > > > > > > Yes. Microsoft will fallback to assume the architecture...

> > No, that logic is hardcoded into @vscode/ripgrep package. > > Ok, I see that there no case for riscv64 at https://github.com/microsoft/vscode-ripgrep/blob/e1773d7264e95fb02fba0f0e20029723d0cfa4b8/lib/postinstall.js#L40 Maybe you could make a PR there?...

> > It won't do too much good until proper CI/CD is set up for ripgep itself, which I got stuck at. > > The swap of the binary could...

The errors from TypeScript LSP is perhaps caused by some path manipulation operations in `00_typescript.js`. In function `pathForLibFile` in `00_typescript.js`: ```js function hexEncode(s) { // helper function for debugging let...

Hi @Brooooooklyn, the renovate bot broke it in https://github.com/napi-rs/node-rs/pull/963. Probably we should not let the bot automatically merge it without passing CI checks.

> I had a discussion with Fedora team. They said me that the `rg` binary used by VSCodium during the building, despite it is for `aarch64` (ARM), that binary doesn't...

> In the attached project I can't get any struct to get generated. > ```c > struct { > __uint(type, BPF_MAP_TYPE_SOCKHASH); > __uint(max_entries, 8192); > __uint(key_size, sizeof(struct sock_key)); > __uint(value_size,...

> I have also made some additional changes to rvv_ops-inl.h and set_macros-inl.h in pull request [#2587](https://github.com/google/highway/pull/2587) that along with the changes in pull request [#2586](https://github.com/google/highway/pull/2586) allow Google Highway to be...