build

If you use aquery_differ to diff 2 aquery proto files and you pass both --attrs=inputs and --attrs=cmdline, if there is a difference in the Environment keys of actions it will not appear in the final diff

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

Some UDCs (or even targets) could benefit from strictly required ARGs - ARGs that must be passed in, in order for the command (or target) to work.

This helps eliminate cases where the user is chasing their tail trying to figure out what's wrong when an ARG is unexpectedly set to "" when declared as ARG something and no value is provided on the call itself.

Sytanx suggestion:

ARG 

Issue Description

msbuild's code is open source under the MIT license. This allows anyone to examine, modify and distribute the sources (among other things). However, the source code repository includes a documentation file that has a "Microsoft Confidential" notice:

https://github.com/dotnet/msbuild/blob/master/src/Shared/Shared%20Code.doc

I suspect this is a mistake since there i

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