Error:Cannot run program "bazel" : CreateProcess error=206, The filename or extension is too long

[kool79]

Description of the issue. Please be specific.

Error:Cannot run program "bazel" (in directory "D:\dev\github\selenium"): CreateProcess error=206, The filename or extension is too long
Most of files are non-synced after project rebase
Standard 'sync' does not work
IDEA Cache clear did not help

What's the simplest set of steps to reproduce this issue? Please provide an example project, if possible.

1. checkout [email protected]:/SeleniumHQ/selenium.git
2. Bazel > Sync > Non-incrementally sync...
   Same for regular sync.

Version information

IdeaUltimate: 2024.2 EAP
Platform: Windows 10.0
Bazel for IntelliJ plugin: 2024.06.03.0.1-api-version-242
Bazel: 7.1.2

[kool79]

IDEA log contains:

2024-06-13 06:06:42,308 [ 780429] INFO - #com.google.idea.async.process.CommandLineTask - Running task:
C:\ProgramData\chocolatey\bin\bazel.exe build --tool_tag=ijwb:IDEA:ultimate --override_repository=intellij_aspect=C:\Users\o.kulychok\AppData\Roaming\JetBrains\IntelliJIdea2024.2\plugins\ijwb\aspect --keep_going --build_event_binary_file=C:\Users\O4937~1.KUL\AppData\Local\Temp\intellij-bep-d74dde3a-53d3-4ec3-9c0f-6954fa2064e2 --nobuild_event_binary_file_path_conversion --curses=no --color=yes --progress_in_terminal_title=no --noexperimental_run_validations --aspects=@@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --output_groups=intellij-resolve-java-direct-deps,intellij-resolve-py-direct-deps,intellij-info-generic,intellij-info-java-direct-deps,intellij-info-py-direct-deps -- //java:auto-service //java/src/org/openqa/selenium:client-combined-lib //java/src/org/openqa/selenium:core-lib //java/src/org/openqa/selenium/bidi:augmenter //java/src/org/openqa/selenium/bidi:bidi //java/src/org/openqa/selenium/bidi/browsingcontext:browsingcontext //java/src/org/openqa/selenium/bidi/log:log //java/src/org/openqa/selenium/bidi/module:module //java/src/org/openqa/selenium/bidi/network:network //java/src/org/openqa/selenium/bidi/script:script //java/src/org/openqa/selenium/bidi/storage:storage //java/src/org/openqa/selenium/chrome:chrome-lib //java/src/org/openqa/selenium/chromium:chromium-lib //java/src/org/openqa/selenium/cli:cli //java/src/org/openqa/selenium/concurrent:concurrent //java/src/org/openqa/selenium/devtools:augmenter //java/src/org/openqa/selenium/devtools:devtools //java/src/org/openqa/selenium/devtools:devtools-prototypes //java/src/org/openqa/selenium/devtools/v123:cdp //java/src/org/openqa/selenium/devtools/v123:v123-lib //java/src/org/openqa/selenium/devtools/v124:cdp //java/src/org/openqa/selenium/devtools/v124:v124-lib //java/src/org/openqa/selenium/devtools/v125:cdp //java/src/org/openqa/selenium/devtools/v125:v125-lib //java/src/org/openqa/selenium/devtools/v85:cdp //java/src/org/openqa/selenium/devtools/v85:v85-lib //java/src/org/open

Seems plugin tries to pass all data, all files via command line

[kool79]

Maybe similar to #6478

[tpasternak]

Thanks for the report. I think this one is different, it happens in a different place and probably is a windows-only problem

[GoKlaus]

IDE: idea
do u set derive_targets_from_directories: true?
i got the same problem, change .brazelproject like below:

directories:
  .

# dont set derive_targets_from_directories true
# derive_targets_from_directories: true 

targets:
  # If source code isn't resolving, add additional targets that compile it here
  //:compiler_internals
  //:dagger_with_compiler
  //:producers_with_compiler
  //:spi
  //gwt:gwt
  //gwt:manual_deps
  //java/dagger:core
  //java/dagger/android/internal/proguard:proguard-processor
  //java/dagger/android/processor:base_processing_step
  //java/dagger/android/processor:processor
  //java/dagger/errorprone:errorprone
  //java/dagger/example/atm:atm
  //java/dagger/grpc/server:annotations
  //java/dagger/grpc/server:server
  //java/dagger/grpc/server/processor:processor
  //java/dagger/hilt:artifact-core-lib
  //java/dagger/hilt:define_component
  //java/dagger/hilt:entry_point
  //java/dagger/hilt:generates_root_input
  //java/dagger/hilt:install_in
  //java/dagger/hilt:package_info
  //java/dagger/hilt/android:entry_point_accessors_internal_kt
  //java/dagger/hilt/android:package_info
  //java/dagger/hilt/android/components:package_info
  //java/dagger/hilt/android/internal/earlyentrypoint:earlyentrypoint
  //java/dagger/hilt/android/internal/legacy:aggregated_element_proxy
  //java/dagger/hilt/android/internal/testing:test_injector
  //java/dagger/hilt/android/internal/uninstallmodules:uninstallmodules
  //java/dagger/hilt/android/lifecycle:hilt_view_model_extensions_internal_kt
  //java/dagger/hilt/android/lifecycle:package_info
  //java/dagger/hilt/android/migration:package_info
  //java/dagger/hilt/android/processor:artifact-lib
  //java/dagger/hilt/android/processor/internal:android_classnames
  //java/dagger/hilt/android/processor/internal/androidentrypoint:android_generators
  //java/dagger/hilt/android/processor/internal/androidentrypoint:metadata
  //java/dagger/hilt/android/processor/internal/androidentrypoint:processor_lib
  //java/dagger/hilt/android/processor/internal/bindvalue:bind_value_processor_lib
  //java/dagger/hilt/android/processor/internal/customtestapplication:processor_lib
  //java/dagger/hilt/android/processor/internal/viewmodel:processor_lib
  //java/dagger/hilt/android/processor/internal/viewmodel:validation_plugin_lib
  //java/dagger/hilt/android/qualifiers:package_info
  //java/dagger/hilt/android/scopes:package_info
  //java/dagger/hilt/android/testing:package_info
  //java/dagger/hilt/android/testing/compile:compile
  //java/dagger/hilt/codegen:originating_element
  //java/dagger/hilt/codegen:package_info
  //java/dagger/hilt/components:components
  //java/dagger/hilt/components:package_info
  //java/dagger/hilt/internal:component_entry_point
  //java/dagger/hilt/internal:component_manager

additional_languages:
  kotlin
  python

[tpasternak]

it might be fixed in #6595