We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When executing bazel with an elastic search dependency:
ERROR: C:/users/caros/_bazel_caros/5stqozjs/external/com_github_elastic_go_elasticsearch_v7/esapi/BUILD.bazel:3:11: GoCompilePkg external/com_github_elastic_go_elasticsearch_v7/esapi/esapi.a failed: (Exit 1): builder.exe failed: error executing command (from target @com_github_elastic_go_elasticsearch_v7//esapi:esapi) bazel-out\x64_windows-opt-exec-2B5CBBC6\bin\external\go_sdk\builder.exe -param=bazel-out/x64_windows-fastbuild/bin/external/com_github_elastic_go_elasticsearch_v7/esapi/esapi.a-0.params <unknown line number>: internal compiler error: panic: badly formatted input
Local Execution
include in the build: "@com_github_elastic_go_elasticsearch_v7//:go_default_library", run with bazel
Windows 11
bazel info release
No response
development version
(@non-git)
git remote get-url origin; git rev-parse HEAD
The text was updated successfully, but these errors were encountered:
That looks like a problem with the Go compiler or the Go rules, not with Bazel. Try filing an issue against https://github.com/bazelbuild/rules_go?
Sorry, something went wrong.
sgowroji
iancha1992
satyanandak
No branches or pull requests
Description of the bug:
When executing bazel with an elastic search dependency:
Which category does this issue belong to?
Local Execution
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
include in the build:
"@com_github_elastic_go_elasticsearch_v7//:go_default_library",
run with bazel
Which operating system are you running Bazel on?
Windows 11
What is the output of
bazel info release
?No response
If
bazel info release
returnsdevelopment 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?
No response
The text was updated successfully, but these errors were encountered: