Debugging tests should always run locally and not attempt remote execution

[BrianXDong]

Description of the bug:

We have remote execution set up such that all actions run remotely by default. As a result of this change, whenever we try to debug tests in intelliJ, our remote execution cluster rejects the action with the following error:

Failed Precondition: Action <digest> is invalid: A timeout specified is out of bounds with a configured range.
  Precondition Failure:
    (INVALID) 9999s > 3600s: A timeout specified is out of bounds with a configured range

While the above error is a result of our specific RBE setup, debugging tests should always run locally so that debugging information can be available. Therefore, we feel as if IntelliJ should enforce tests running locally.

Which category does this issue belong to?

Intellij

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Not sure this is immediately reproducible.
If you have a readily available RBE setup, then setup your bazel invocations to use it by default, then attempt to debug a test from IntelliJ.

Which Intellij IDE are you using? Please provide the specific version.

2024.3

What programming languages and tools are you using? Please provide specific versions.

Scala

What Bazel plugin version are you using?

Custom Fork: https://github.com/lucidsoftware/intellij

Have you found anything relevant by searching the web?

Slack thread from a few years back discussing a similar issue: https://bazelbuild.slack.com/archives/C025SBYFC4E/p1657027692628699

Any other information, logs, or outputs that you want to share?

We have a fork of IntelliJ that has a patch for this that works for us: lucidsoftware#3
This potentially can be up-streamed here for this issue.

[tpasternak]

Well, it makes perfect sense, but I'm a bit worried about changing behavior this way unconditionally.