Austin Schuh

@aiuto , I'm happy to work on at least part of this one if there's consensus that this is reasonable to do. The `include_runfiles` is making it hard to move...

No guarantees, but is this a "I don't want to fix this" and you'd take patches, or you don't think this should be fixed and pkg_expand should be the way...

FYI, @alexeagle . I don't know if this should be fixed in rules_js or in Bazel (or in both, the error message is pretty unhelpful).

> noincompatible_sandbox_hermetic_tmp Unfortunately, no. ``` $ bazel test -c opt //... --noincompatible_sandbox_hermetic_tmp INFO: Invocation ID: c3732082-ecf0-4c68-b7e6-b398ae21fd07 INFO: Analyzed 5080 targets (0 packages loaded, 0 targets configured). ERROR: /home/austin/local/971-Robot-Code/BUILD:8:22: Extracting npm...

I applied the following diff to `rules_js`: https://github.com/frc971/971-Robot-Code/blob/master/third_party/rules_js/0001-Fix-package-permissions.patch

This problem (and ones similar to it) would be well served by a gradient convergence check. That would much more directly measure what I care about since the problem is...

Yea, happy to help. I started by filing https://github.com/bazelbuild/continuous-integration/issues/2005, but I'm not sure if they have capacity right now or not. If not, I'll take a look.

Upstream Bazel will test out new versions of bazel before they release and make sure nothing breaks (on top of having everything setup to be super fast with good caching,...

I just hit this when upgrading Eigen to a newer version. I suspect there was a change in Eigen which changed the results.

Can you point this to the 2027 branch please?