build-tool

The local files produced by SAVE ARTIFACT ... AS LOCAL ... always give the same modification time, even when the file content changed. It leads to Earthly targets depended on local artifacts incorrectly cached.

To demonstrate:

FROM busybox

date:
    RUN --no-cache date | tee date
    RUN date -r ./date
    SAVE ARTIFACT date AS LOCAL .

print-date:
    COPY ./date da

steps

Using Scala 2.12.14 + SBT 1.5.x
Just include this import in your source

import java.time.temporal.ChronoUnit.MILLIS.{between => millisBetween}

problem

java.lang.NullPointerException
	at xsbt.Dependency$DependencyTraverser.lookupImported$1(Dependency.scala:394)
	at xsbt.Dependency$DependencyTraverser.$anonfun$traverse$1(Dependency.scala:396)
	at xsbt.Dependency$De

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

For the sake of completeness, the Task runner in verbose with (i.e. task -vvvvv) should report when a task is complete and starts.

right now the image-loader middleware only supports the formats ICO, JPEG, PNG, GIF, SVG and WEBP.

It would be very useful to also add the new AVIF format, that is already being used on the web and that is quickly gaining popularity and browser supports

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
{
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na

Hi,

I looked into the CLI part of style-dictonary to construct a similar thing and I found a bug when I run the command style-dictionary test or npx -p style-dictionary style-dictionary test in my case:

npx : 43 installé(s) en 3.911s
/Users/xzalawa/.npm/_npx/19473/lib/node_modules/style-dictionary/bin/style-dictionary:75
  console.error('Invalid command: %s\nSee --help for a list o

Thanks to using PyO3 (pantsbuild/pants#13526), error handling is now much more ergonomic. Notably, we no longer need to hold the GIL to create a PyErr.

It'd be great to chip away at how much we call .unwrap() in our code, which should make our code more reliable. Instead, probably the only place unwrapping should happen is in our #[pyfunction] and #[pymethods], i

This issue is tracking the documentation that has to be updated.

• Document new platform commands
• Update the section dedicated to page <title> and tell about [Browser.documen