rules_go | Go rules for Bazel

by bazelbuild Go Version: v0.39.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | rules_go Summary

rules_go is a Go library. rules_go has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Go rules for Bazel

Support

Quality

Security

License

Reuse

Support

rules_go has a medium active ecosystem.

It has 1243 star(s) with 596 fork(s). There are 57 watchers for this library.

It had no major release in the last 12 months.

There are 288 open issues and 1304 have been closed. On average issues are closed in 187 days. There are 29 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rules_go is v0.39.1

Quality

rules_go has 0 bugs and 0 code smells.

Security

rules_go has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rules_go code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rules_go is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

rules_go releases are available to install and integrate.

It has 15954 lines of code, 651 functions and 317 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rules_go

Get all kandi verified functions for this library.

rules_go Key Features

No Key Features are available at this moment for rules_go.

rules_go Examples and Code Snippets

No Code Snippets are available at this moment for rules_go.

Community Discussions

Trending Discussions on rules_go

Cannot build go_proto_library with gRPC

gazelle+protobuf problem: does not have mandatory providers: 'GoLibrary'

Bazel build missing strict dependencies

QUESTION

Cannot build go_proto_library with gRPC

Asked 2021-Sep-30 at 14:09

I'm getting started with bazel and trying to generate the protobuf code for golang for an RPC service.

When I try to build it I get the following error:

...

ANSWER

Answered 2021-Sep-30 at 14:09

UPDATE: it looks surely a version issue: https://github.com/grpc/grpc-go#compiling-error-undefined-grpcsupportpackageisversion

Not a bazel user, but after hours' test, I found your rpc version should be higher:

Source https://stackoverflow.com/questions/69338902

QUESTION

gazelle+protobuf problem: does not have mandatory providers: 'GoLibrary'

Asked 2020-Oct-08 at 15:04

From gazelle-generated BUILD files, I get the following error when I run bazel build //foo/bar/protos/...:

ERROR: .../foo/bar/protos/BUILD.bazel:15:17: in deps attribute of go_proto_library rule //foo/bar/protos:protos_go_proto: '//baz/quux/api:api_proto' does not have mandatory providers: 'GoLibrary'

Both BUILD files have:

...

ANSWER

Answered 2020-Oct-08 at 15:04

This error means that //baz/quux/api:api_proto is the wrong kind of target for the deps attribute of the go_proto_library rule (it does not "provide" the right information).

//baz/quux/api:api_proto is probably a proto_library target, and should be in the protos attribute instead of the deps attribute: https://github.com/bazelbuild/rules_go/blob/master/proto/core.rst#go_proto_library

Source https://stackoverflow.com/questions/64263317

QUESTION

Bazel build missing strict dependencies

Asked 2020-Aug-31 at 06:28

I am trying to build a Go application with brazel. It is an existing private GitHub repo (with this location: github.xyz.com/repo-name) that I am working on, and my aim is to create a binary out of a main.go file that depends on some other Go files for it's methods. This is my BUILD.bazel file inside the folder called e2e where all these go files are present:

...

ANSWER

Answered 2020-Aug-31 at 06:28

I resolved the issue by adding my main.go file in a new folder inside the e2e folder (while keeping the helper files in the e2e folder). This way when I added a dependency of my main.go file to the helper files, it did not lead to a cyclic dependency error.

Source https://stackoverflow.com/questions/63622610

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rules_go

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: