CLion sync failes due to invalid aspect path

[milancpp]

Description of the bug:

After updating to 2025.01.21.0.2-api-version-251 and CLion 2025.1 EAP I'm getting errors like the following during syncing:

ERROR: Label '//.clwb/aspects:intellij_info_bundled.bzl' is invalid because '.clwb/aspects' is not a package; perhaps you meant to put the colon here: '//:.clwb/aspects/intellij_info_bundled.bzl'?

As a result, analysis fails and no targets are imported.

Which category does this issue belong to?

CLion

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

No response

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

CLion 2025.1 EAP

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

C++, Python

What Bazel plugin version are you using?

2025.01.21.0.2-api-version-251

Have you found anything relevant by searching the web?

No response

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

I tried importing the workspace from scratch, to no avail.

[milancpp]

Same error with 2025.01.21.0.2-api-version-243 after downgrading to CLion 2024.3.2

[ujohnny]

Thanks for the report, we received similar one internally yesterday. Could you please try invalidate IDE cache and tick "Clear file system cache..." and get back to us with the observations?

[LeFrosch]

@milancpp Also, could you make sure that .clwb is not part of your .bazelignore file.

[milancpp]

Thanks for the report, we received similar one internally yesterday. Could you please try invalidate IDE cache and tick "Clear file system cache..." and get back to us with the observations?

This yields no observable difference, same error.

@milancpp Also, could you make sure that .clwb is not part of your .bazelignore file.

@LeFrosch thanks, this is the problem. After removing .clwb syncs are working again

[LeFrosch]

@ujohnny We might need to do something about this .bazelignore stuff. Seems to be quite common that people ignore the .clwb / .ijwb directories.

[ujohnny]

Indeed, was it a common practice because it was failing the build previously because of java targets in it? I guess we can fail a sync if .*wb is in bazelignore with a meaningful message asking to remove it

[ujohnny]

and next beta will be promoted to stable next Tuesday, so we have some time for that