#repro

1 messages · Page 1 of 1 (latest)

surreal jackal
#
dagger -m github.com/dagger/dagger@v0.20.3 call engine-dev playground terminal

▶ ✔ connect 0.5s
✘ load workspace: . 2m56s ERROR
┇ loading type definitions › load extra module: github.com/dagger/dagger@v0.20.3 › ModuleSource.asModule › load dep modules › ModuleSource.asModule › module SDK: load runtime › DangSdk.moduleRuntime(
  ┆ modSource: no(digest: "xxh3:e08905999058f50e")
  ┆ introspectionJson: no(digest: "xxh3:d8def5b6868627dc")
  ) ›
✘ http(url: "https://ziglang.org/builds/zig-aarch64-linux-0.16.0-dev.2670+56253d9e3.tar.xz"): File! 0.5s ERROR
! invalid response status 404 Not Found

Full trace at https://dagger.cloud/dagger/traces/0c9c56fbf30fbe42dce18d7ef213c6de
velvet berry
#

Same for me...

#

But I can build from main

#

No error on this one:

dagger -m github.com/dagger/dagger@v0.20.4 call engine-dev playground terminal

(calling with 0.20.5)

lapis pilot
#

yeah the zig dependency that dang used at the time was pulled. it was fixed by bumping dang (which switched to using mirrors) but those older versions are broken

velvet berry
#

Yeah we tracked it down.. An interesting case of the limits of upstream software carrying its own build harness.

#

If the build needs a fix later, you have to retroactively change that tag, or accept that some releases just don't build out of the box anymore