Missing repositories after upgrading to Bazel 8

[psalaberria002]

Description of the bug:

We have seen various errors related to repositories (missing) after upgrading to Bazel 8.

Setting --noincompatible_no_implicit_watch_label seems to fix the issues.

@fabian

https://bazelbuild.slack.com/archives/CA31HN1T3/p1734339844946189

Which category does this issue belong to?

No response

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

In a repository where rules_go is used, changing dependencies in go.mod

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 8.0.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

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

Example error log.

Error in fail: gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws: fetch_repo: go mod download exec error: /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go mod download -json -modcacherw go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/[email protected]: fork/exec /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go: no such file or directory

(08:33:02) ERROR: no such package '@@gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws//': gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws: fetch_repo: go mod download exec error: /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go mod download -json -modcacherw go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/[email protected]: fork/exec /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go: no such file or directory

(08:33:02) ERROR: /workspace/infrastructure/services/platform/gollum/pkg/pgrepos/aws/BUILD.bazel:3:11: //services/platform/gollum/pkg/pgrepos/aws:aws depends on @@gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws//:otelaws in repository @@gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws which failed to fetch. no such package '@@gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws//': gazelle++go_deps+io_opentelemetry_go_contrib_instrumentation_github_com_aws_aws_sdk_go_v2_otelaws: fetch_repo: go mod download exec error: /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go mod download -json -modcacherw go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/[email protected]: fork/exec /bazel-cache/infrastructure/external/rules_go++go_sdk+go_sdk/bin/go: no such file or directory

[mortenmj]

@bazel-io fork 8.0.1

[fmeum]

Can you reproduce this without other flags in .bazelrc? Could you post the output of running with --announce_rc (feel free to redact values)?

[fmeum]

@bazel-io fork 8.0.1

[fmeum]

May or may not be related to #24694

[fmeum]

I still haven't managed to reproduce this. Any more information would be highly appreciated.

[fmeum]

Quoting from Slack (https://bazelbuild.slack.com/archives/CSV56UT0F/p1734548734488839?thread_ts=1734475559.039469&cid=CSV56UT0F):

Using https://github.com/abrisco/rules_pyo3, it's reproducible with
bazel build //pyo3/private/tests/bzl_version:bzl_version_test --config=strict --output_groups=rustfmt_checks
The action refers to a dangling symlink, which I'm at a loss for how that's possible

I'm unable to reproduce this, but it seems related to this issue.