bazel cquery with --output label_kind gives

ERROR: Invalid output format 'label_kind'. Valid values are: label, transitions, proto, textproto, build

I couldn't find any place in the documentation that would showcase all possible configurational parameters that can be used inside backpack.config.js file. Is it possible to add not only config.entry.main but also showcase all other available options with a brief explanation of its purpose?

Currently, mangle.json writes always remove a trailing newline from the file. We could detect the existence of the trailing newline when reading, then preserve whatever was used when writing.

See https://github.com/preactjs/preact/blob/e22cc99ca398bb0a417ccc151a520c41215afe55/.editorconfig#L17-L22

There seems to be a problem with nodemode (an internal flag) without an argument.
I set MSBUILDDEBUGONSTART to 1 and built a project that referenced two other libraries using the command:
<path to MSBuild.exe> <path to project file> /m /nodemode /nodereuse:false

Expected behavior: useful error message about how nodemode works.
Actual behavior: unexpected bug with a message asking me to fil

Hi,

Im having issues with using the SSH key for my account. I followed the default guide here which apparently outputs an encrypted private key that golang ssh does not support I believe?

Cannot access git repo: ssh: cannot decode encrypted private keys

Iv not seen any issues related to

Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example, .use and .define are provided by Base and implicitely added through Templates.

It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the @mixinand [`@mix

Some of the repos that we import has ".go" in the file path. eg. https://github.com/nats-io/nats.go.

When using packr v2 to build packr parses the folder path as a file and reports error ".../nats.go" is a directory.

The issue is in findAllGoFiles in jam/parser/finder.go

I am happy to raise a PR if you like

Issues and ideas for improvement:

• Docs show how to define and run tasks, but how do you integrate them into the build process?
• Difference between scripts and tasks? Between just-script and just-task? When do you need one, other or both?
• Steps for integrating with existing repos/monorepos.
• Monorepo doc page still refers to npm.
• JS examples seem to be using 'import' and other invalid

Prerequisites

• [y] Have you tried launching atom . from the terminal in your project's directory?
• [y] Have you verified the output from go env is correct? If it is, please include the output in this issue.
• [y] Have you updated Atom to the latest version?
• [n] Have you tried using Atom Beta, which can be run side-by-side with Atom Stable? Is the behavior

Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.

Is this a feature or a bug?

• Feature
• Bug

Please describe the actual behavior.

Received the following error when following the installation instructions.

api-extractor run --local --verbose

Error: Unable to create the API report file. Please make sure the target fold

Is it possible to provide some descriptions in the documentation about some of the global variables (such as g:asyncrun_silent)? It looks like there are quite a few of said variables, and only two appear in the documentation.

Personally, I'm very interested in what variables are available and how they are intended to be used.

This is a feature request for the website, more than for Please.Build itself.

Please.build has terrible search-ability on the Internet. Any attempts to find projects which use plz falls flat. Attempting to use plz in my own project (which has both Python executables and C executables) results in errors which are not helpful to me as a beginning user. I don't know if I've uncovered some kind

I have an OCaml library that gets built by dune, which calls code in a Linux dynamic library (using the Ctype.Foreign mechanism). I have other OCaml code that calls this OCaml library, from which dune builds an executable. That executable shows errors when it's run, unless I add flags to the dune file so that the OCaml compiler links against the Linux library (it's librocksdb.so).

The library

Affected builder image

gcr.io/cloud-builders/gke-deploy)

Expected Behavior

When deploying a Kubernetes Deployment config that includes init containers, the images in the initContainers section of the config matching the image passed on the command line will have their versions updated to the version specified, same as what happens with the images in the containers section of t

For easier sudo configuration with the sudo isolation plugin, we really want the vespene user to be in sudoers.

This is not something that the setup automation currently sets up.

We should at least add a note in the docs for this

The plugin should align with other plugins in the Gradle ecosystem by generating artifacts in the $buildDir directory. For example test reports should be created in build/reports/tests/<task-name> and build/test-results/<task-name> instead of .gogradle/reports/<task-name>. Users familiar with Gradle would expect to find generated artifacts there.

Is your feature request related to a problem? Please describe.
Today if the user is using paths in tsconfig.json he has to define the mappings manually in jest.config.js.

Describe the solution you'd like
We can save the user the headache by using this approach for mapping tsconfig paths.

Affected builder image

remote-builder

Expected Behavior

The main build uses scp to copy files to the remote machine.

Actual Behavior

ssh: connect to host 35.238.52.245 port 22: Connection timed out

Additional Info

It's probably just a problem with the setup of the GCP project?

In the README the assets? task definition is a bit wrong.

    p.Task("assets?", nil,  func(c *do.Context) {
        // The "?" tells Godo to run this task ONLY ONCE regardless of
        // how many tasks depend on it. In this case watchify watches
        // on its own.
	    c.Run("watchify public/js/index.js d -o dist/js/app.bundle.js")
    }).Src("public/**/*.{css,js,html}")

docs.buildout.org/en/latest/
is not reachable via HTTPS as the certificate is only valid for readthedocs

Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for docs.buildout.org. The certificate is only valid for the following names: *.readthedocs.io, readthedocs.io

Is there an easy way to deploy a Let's Enc

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)