Description of the problem / feature request:

It is unclear what operations the value returned by select supports.

Documentation:
https://docs.bazel.build/versions/3.0.0/skylark/lib/globals.html#select
It returns an unknown

But other documentation makes it obvious that we are not supposed to treat this as an opaque object.
https://docs.bazel.build/versions/master/be/functions.html#

Everybody should now use Go modules for dependency management.

The Go build example of distroless should too.

Stardoc is a documentation generator for Bazel rules, providers, and other definitions.

Currently, rules_go documentation is maintained separately from the rule implementation themselves, so it's easy for it to drift.

We should investigate whether Stardoc is a viable replacement for the current documentation. If it is, we should migrate the current do

The README should document what version(s) of Bazel are required to run rules_docker. For example v0.8.0 uses default_mtime which appears to have been introduced with Bazel 0.24, but there was no mention that a newer version was required.

Please ask which one, some may be outdated or low priority.

Bazel's load builtin supports a syntax for aliasing loaded values, something like this:

load("//:pkg.bzl", some_alias = "some_value")

Which causes some_alias to refer to some_value in the file in which it is used.

There does not seem to be a mechanism for manipulating them within buildozer, or it is not clearly documented. Judging by looking at the [tests for `rep

• 400 - Bad Request (Client Error)
• 401 - Unauthorized, authentication required
• 404 - Not Found

JSON API reports user input errors back to the client, e.g:

{"errors":["JSON parser error: Unexpected character 'f' at input index 27 (line 1, position 28)"],"status":400}

{"errors":["Can't read null as string element for actAs"],"status":401}

However there were multiple requests

Hi,
The example in the README is not sufficient for masses to start using this confidently.
There's a documentation need to explain what you can do, how, in order to developers to start using it.

I see a great potential for this project as multi-module projects are becoming more and more common with multiple Android targets (Wear OS, TV, Auto Things...), Instant Apps and feature modules, Kotl

Problem

When manually entering additional bazel flags which contain quotes, the plugin changes the format.

Setup:

Result:

--test_filter=my.app.AppSpec "--test_arg=-testName \"Name of my spec\"" 

Other example:

--test_arg=-testName="Name of my spec"

🚀 feature request

Hi, I am trying to build opencv with opencv_contrib.

In order to build opencv_contrib, I need to pass the path of opencv_contrib to opencv cmake:

cmake -DOPENCV_EXTRA_MODULES_PATH=<opencv_contrib>/modules <opencv_source_directory>

Is there a way to include multiple filegroups in lib_source so t

In line_length.bzl:

ctx.actions.write(
    output = ctx.outputs.executable,
    content = script,
)

Notice that ctx.outputs.executable default field is used, and the documentation states this is deprecated:

(Deprecated) If the rule is marked executable or test, there is a field named "executable

If you search for a tag that works in the tulsigen files like "additionalFilePaths" you get no hits on any documentation. Just source files that generally don't explain the syntax you can use for that tag.

See if we can replace write_manifest_file with code from jvm common ruleset or something (existing or to contribute back).
Motivation for generalization- Recurring pattern of writing a manifest for a jar file

I went through the documentation and have not found:

1. how to specify a certain version of Rust compiler?
2. how to enable Rust nightly compiler?
   Thanks!

I'm using bazel version 0.22.0. I have no clue which version of rules_kotlin to use.

rules_scala has this table:

It would be very useful to have something similar in kotlin.

yaml.reader.ReaderError: unacceptable character #x1f48e: special characters are not allowed
in "", position 1195

This seems to come from the python yaml reader which incorrectly rejects special unicode characters.
The character in particular is 💎, which kubernetes gladly accepts as valid unicode.

https://www.compart.com/en/unicode/U+1F48E

Is your feature request related to a problem? Please describe.

I've found caching with rules_haskell to be hard to figure out. I'm using rules_haskell in a project I'm working on. I run locally on my Linux machine and (mostly due to inertia) on three CI services: AppVeyor (Windows), GitLab CI (Linux), and TravisCI (Linux and macOS). I use the GHC bind

This is to match tensorflow's requirement.

Current pip version is 9.0.3. (Looks like pip recently switched the versioning scheme to use the last two digits of the year.)