-
Notifications
You must be signed in to change notification settings - Fork 525
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
bazel build //extensions/key_rate_limit:key_rate_limit.wasm" reports an error #1518
Comments
我是在本地起来一个容器higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/build-tools-proxy:release-1.19-ef344298e65eeb2d9e2d07b87eb4e715c2def613编译的。看了一下WORKSPACE文件,里面指定的URL为https://github.com/higress-group/proxy-wasm-cpp-sdk/archive/eaec483b5b3c7bcb89fd208b5a1fa5d79d626f61.tar.gz,手动下载这个包解压后确实没有/bazel:dep/deps.bzl |
你的 higress 分支更新到最新了吗 |
就是在master上拉的最新的编译的 |
不好意思看错了,看到了4天前的更新,我再试试 |
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via ASRC(Alibaba Security Response Center) where the issue will be triaged appropriately.
Ⅰ. Issue Description
按照dockerfile中内容,使用docker run命令启动编译镜像higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/build-tools-proxy:release-1.19-ef344298e65eeb2d9e2d07b87eb4e715c2def613,执行编译命令 bazel build //extensions/key_rate_limit:$key_rate_limit.wasm。如果是在main分支下执行,报错_ERROR: error loading package '': Label '@proxy_wasm_cpp_sdk//bazel/dep:deps.bzl' is invalid because 'bazel/dep' is not a package; perhaps you meant to put the colon here: '@proxy_wasm_cpp_sdk//bazel:dep/deps.bzl'?_
切换到release-1.x分支,报错变成了_ERROR: /home/.cache/bazel/_bazel_root/171c9fb4c80b6f8959f81ec79e458aab/external/rust_windows_aarch64__wasm32-wasi__stable/BUILD.bazel:1:10: no such target '@platforms//os:wasi': target 'wasi' not declared in package 'os' defined by /home/.cache/bazel/_bazel_root/171c9fb4c80b6f8959f81ec79e458aab/external/platforms/os/BUILD and referenced by '@rust_windows_aarch64__wasm32-wasi__stable//:toolchain'_
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: