unable to automatically connect to vscode debug toolbar

[shaheenVA]

when attempting to use bluebazel to debug a golang bazel test target - the process seems to hang (however in reality the underlying dlv command is stopped at the defined breakpoint). regardless, theres no 'automatic' connection to the vscode debug ui toolbar.

[joshabb]

Can you please describe your exact setup so I can reproduce?

[bluecmd]

Same for me, but with a cc_test. Using Bazel 9.0.0, Blue Bazel 1.0.7.

Example build file:

load("@rules_cc//cc:cc_test.bzl", "cc_test")

cc_test(
    name = "test",
    srcs = ["test.cpp"],
    deps = [
        "@googletest//:gtest",
        "@googletest//:gtest_main",
    ],
    copts = [
        "-std=c++20"
    ],
)

test.cpp:

#include "gtest/gtest.h"

TEST(Lib, getName) {
  EXPECT_EQ("foo", "foo");
}

Example MODULES.bazel file:

bazel_dep(name = "rules_cc", version = "0.2.17")

Add the test target to Blue Bazel:

And press "Debug" in the Blue Bazel action bar. This causes a stray gdbserver to be unkillable except from the terminal. Setting breakpoints also does not seem to do anything.