build

Description of the problem / feature request:

glob throws an evaluation error when it detects an infinite recursion in a
directory traversal. However, it detects this recursion even if the specific
subpath leading to that recursion is excluded via the exclude=[] argument.

This means that recursive symlinks cannot be ignored in glob expressions,
even if they occur in subtrees that

FROM alpine:3.12

foo:
    ARG file
    RUN ls $file

all:
    BUILD +foo --file=/this-should-fail --file=/this-should-fail-also-fail

$ earthly -i +all 
           buildkitd | Found buildkit daemon as docker container (earthly-buildkitd)
         alpine:3.12 | --> Load metadata linux/amd64
               +base | --> FROM alpine:3.12
               +base | [██████████] 

These are new in .NET 5.0: https://docs.microsoft.com/en-us/dotnet/api/system.operatingsystem?view=net-5.0

They expose methods for all the common operating systems like OperatingSystem.IsWindows() but also still support the API where you pass in a string: OperatingSystem.IsOSPlatform(string platform).

The new APIs are easier to understand so we should consider exposing them.

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

Labeling subsystems with their backends would make it clearer which backends needed to be enabled in order to activate certain features. It would also make it safe(r) to render experimental backends on the docsite.

Relates to #8992.

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