Malte Poll
Malte Poll
Thank you for reaching out! Your feature request makes a lot of sense. I’m curious, though, if there’s a specific reason you’re looking for a Go toolchain from `nixpkgs`. Starting...
I think we need to migrate to nixpkgs_core and adopt rules_js fully for this. Probably needs Bazel >= 7
Thank you for pointing this out. @jtacoma since you appear to be a user of rules_nixpkgs and the Go toolchain provided by it, do you have an opinion on #473?...
Thank you for this contribution! Just out of interest: Is there a specific new feature this unblocks for you?
Can you provide a minimal reproducer for this? I would like to provide a fix, but I'm not sure I can get into the same state.
Here is the relevant test failure: ``` ---8
I'm seeing the following issue when building `bazel_deps` of `bazel_73` on Linux amd64: ``` Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/build/.cache/bazel/_bazel_nixbld/96c321f6d4067432c019ff2725c18acb/server/jvm.out') ``` Anyone else...
> I'm now leaning toward upgrading the existing package in place. I share that sentiment. > I think a better fetcher might be a preferable solution in the long run...
> > a JSON lockfile instead of creating a vendor_dir. > > What are concrete reproducibility issues one might run in with the current `bazel vendor`? If it's not only...
Result of `nixpkgs-review pr 338264` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review) 1 package built: bazel_7