build

Description of the problem / feature request:

Bazel crashes due to an internal error when using a bzlmod registry that doesn't correctly specify a bazel_registry.json file. The stack-trace printed by Bazel when it crashes is included in the last section below.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

To demonstra

I have an existing Dockerfile that I'd like to use earthly with, but it requires a secret and I don't know how to provide that secret.

Let's say I have the following Dockerfile:

FROM busybox:latest

RUN --mount=type=secret,id=my_secret,target=/mount.txt \
  cp /mount.txt /secret.txt

To build this I'd run
docker build . --secret id=my_secret,env=A_SECRET_IN_MY_ENV

I want t

An interesting one, gotten from hitting Ctrl-C during a build of dotnet/runtime using 6.0.100-rc.2.21505.57

This line
https://github.com/dotnet/msbuild/blob/a59d7a533c9154e8aa99b823625e7eff199ddf1a/src/Tasks/Copy.cs#L588
should perhaps be

                if (!partitionAccepted && !CancellationToken.IsCancellationRequested)

Build FAILED.

C:\git\runtime\.dotnet\sdk\6.0.100

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

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

For example, if you set skip_tests=True then run on a python_test target:

./pants test src/python/pants/util/strutil_test.py

17:00:12.68 [WARN] No applicable files or targets matched. The `test` goal works with these target types:

  * go_package
  * junit_test
  * python_test
  * shunit2_test

However, you only specified files with these target types:

  * python_test

P

What version of Garble and Go are you using?

$ garble version
v0.4.1-0.20210929123233-e7320ec9c034
$ go version
go version go1.17.2 linux/amd64

What environment are you running Garble on?

Dune systematically buffers the output of commands so that their output is not mixed up during parallel builds. However, this is not ideal for interactive commands that require direct access to the terminal.

Currently, the only workaround is to run dune with -j 1 --no-buffer which is not ideal since it completely disables parallelism and also require a specific dune invocation.

Another ide