Skip to content

Conversation

@Techatrix
Copy link
Member

The zig executable may be some kind of proxy that internally forwards to different Zig versions. When ZLS runs the zig executable in different locations (e.g. packages in the global zig cache), this may cause multiple Zig versions to be downloaded and used which can cause all kinds of issues.

This change will ensure that the proxy will only ever be queried once by using the zig_exe field from the zig env output. If zig env fails, the zig exe path will be unset and any zig compiler integrated will be disabled.

The zig executable may be some kind of proxy that internally forwards to different Zig versions.
When ZLS runs the zig executable in different locations (e.g. packages in the global zig cache), this may cause multiple Zig versions to be downloaded and used which can cause all kinds of issues.

This change will ensure that the proxy will only ever be queried once by using the `zig_exe` field from the `zig env` output.
If `zig env` fails, the zig exe path will be unset and any zig compiler integrated will be disabled.
@Techatrix Techatrix merged commit dc19fde into master Feb 2, 2026
6 checks passed
@Techatrix Techatrix deleted the techatrix/unproxy-zig branch February 2, 2026 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant