Pass an executable or tools argument to ctx.actions.run or ctx.actions.run_shell instead of calling ctx.resolve_tools.

[vorburger]

With bazel_dep(name = "rules_graalvm", version = "0.11.1"),

which is the last version that I have been able to figure out how to use, because blocked by #401,

it's failing for me like this on Bazel 8.1.1:

 bazelisk build //tools/hello:hello-native
ERROR: /home/vorburger/git/github.com/enola-dev/enola/tools/hello/BUILD:20:13: in _native_image rule //tools/hello:hello-native:
Traceback (most recent call last):
        File "/home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/rules_graalvm+/internal/native_image/rules.bzl", line 61, column 40, in _graal_binary_implementation
                graal_inputs, _ = ctx.resolve_tools(tools = [
Error in resolve_tools: Pass an executable or tools argument to ctx.actions.run or ctx.actions.run_shell instead of calling ctx.resolve_tools.
Use --noincompatible_disallow_ctx_resolve_tools to temporarily disable this check.
ERROR: /home/vorburger/git/github.com/enola-dev/enola/tools/hello/BUILD:20:13: Analysis of target '//tools/hello:hello-native' failed
ERROR: Analysis of target '//tools/hello:hello-native' failed; build aborted
INFO: Elapsed time: 3.383s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully

Adding common --noincompatible_disallow_ctx_resolve_tools to .bazelrc seems to do the trick.

But that's probably just postponing this problem, until a newer Bazel version doesn't allow that anymore?

Has this been fixed in more recent rules_graalvm versions than 0.11.1?

If yes, how does one use them, re. #401?

If no, this probably still needs to be fixed?

[BenNeighbour]

Having this same issue - do we think this will make it into a release soon?