Fabian Meumertzheim
Fabian Meumertzheim
I'm actually able to reproduce this in rules_go's own tests now and will investigate further.
@jsharpe Could you edit the commit messages to remove the `fmeum` mention? Otherwise I get an email on every push 😅
After digging through the call stack for a bit, I think that it's possible that this regressed in https://github.com/bazelbuild/bazel/issues/20737, which suspiciously adds a Skymeld only code path that [can end...
This should be fixed by https://github.com/bazelbuild/bazel/commit/00bb86b01397d3ad6f3794077fea2958c06d817b which is in Bazel 9. Cherry-picking it into 8.5.0 may be possible if that helps.
This generally looks good to me, we just have to get CI green. You may have to configure a more recent SDK foot the integration test.
Could we limit support to `latest` for now then with this PR? Is that already a useful mode for companies that need FIPS?
Can `--ssafunc` be passed in via `gc_goopts`? In that case we could just check whether it's been passed and if so add the emitted file to an `ssa` output group...
@jayconrod What do you think of having Go actions inherit `--action_env`? It's been "marketed" as a best practice for some time in the past, but it also leaks the (by...
Is it clear that one wouldn't want to enable this for particular targets? In the C++ world, this would probably be solved with `features`, which you set both per-target and...
Still relevant (13 upvotes)