Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: bazel configure fails on fresh checkout #356

Open
smason-apex opened this issue Sep 13, 2024 · 0 comments
Open

[Bug]: bazel configure fails on fresh checkout #356

smason-apex opened this issue Sep 13, 2024 · 0 comments
Labels
bug Something isn't working untriaged Requires traige

Comments

@smason-apex
Copy link

What happened?

Cloning the repo and running bazel configure fails.

❯ bazel version
Aspect CLI Pro version: 5.11.0-alpha0.dev.150.g12ded54
Build label: 7.3.1
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Aug 19 16:17:23 2024 (1724084243)
Build timestamp: 1724084243
Build timestamp as int: 1724084243
❯ bazel configure
Updating BUILD files for protobuf, go, javascript, python, aspect-configure
Source rule generation error: failed to generate target "//logger/frontend" of kind "ts_project": a target of kind "js_run_devserver" with the same name already exists. Use the '# gazelle:js_project_naming_convention' directive to change the naming convention.

For example:
	# gazelle:js_project_naming_convention {dirname}_js
	# gazelle:js_tests_naming_convention {dirname}_js_tests
❯ git rev-parse HEAD
9fee1bb667747157a7417414981955f3176823c6

expect it to run successfully albeit with no changes.

Version

Development (host) and target OS/architectures:

Output of bazel --version: aspect 5.10.14

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: Nothing changed after git clone

Language(s) and/or frameworks involved:

How to reproduce

bazel configure


### Any other information?

_No response_
@smason-apex smason-apex added the bug Something isn't working label Sep 13, 2024
@github-actions github-actions bot added the untriaged Requires traige label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Requires traige
Projects
None yet
Development

No branches or pull requests

1 participant