-
Notifications
You must be signed in to change notification settings - Fork 74
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
Go Bazel builds fail to find cel.dev/expr #97
Comments
Lets see if we can poke folks to go accept google/cel-spec#379 and google/cel-spec#354 |
Not sure if it's related, but I can't build with bazel in WORKSPACE mode after upgrading to a recent commit.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #89 the cel.dev/expr based annotations were reintroduced. Unfortunately, there still seem to be issues when trying to use Bazel, Go and Gazelle together, and importing this module.
I've recently added a dependency on
github.com/cncf/xds/go/xds/type/matcher/v3
and updated my dependency on go-control-plane to pick up a bugfix (envoyproxy/go-control-plane@77feb56 ).(I'm not sure my new dependency there matters, tbh. It's just very close and maybe adding confusion.)
This update to go-control-plane updated the version to this library, and thus picked up the cel.dev/expr change.
Now, my builds fail with:
ERROR: /private/var/tmp/_bazel_randerson/01ba2733315bf63f62b0e43c3a981a72/external/com_github_cncf_xds_go/xds/type/v3/BUILD.bazel:3:11: no such target '@dev_cel_expr//:expr': target 'expr' not declared in package '' defined by /private/var/tmp/_bazel_randerson/01ba2733315bf63f62b0e43c3a981a72/external/dev_cel_expr/BUILD.bazel (Tip: use
query "@dev_cel_expr//:*"
to see all the targets in that package) and referenced by '@com_github_cncf_xds_go//xds/type/v3:type'The BUILD file there doesn't actually define any go libraries, so this isn't particularly surprising, but I don't think this commit is working as expected right now.
I'm not really sure if the problem is here or in cel.dev/expr, but ... well, debugging 3 layers of modules down is not fun.
The text was updated successfully, but these errors were encountered: