!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

193 Members
57 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
7 Mar 2025
@qyriad:katesiria.orgQyriad changed their display name from Qyriad to qyriad.16:44:27
8 Mar 2025
@qyriad:katesiria.orgQyriad changed their display name from qyriad to Qyriad.21:41:03
11 Mar 2025
@avocadoom:avocadoom.deavocadoom changed their profile picture.16:36:23
20 Mar 2025
@ahbk:matrix.orgI use NixOS btw set a profile picture.08:17:25
@ahbk:matrix.orgI use NixOS btw changed their profile picture.08:17:57
@ahbk:matrix.orgI use NixOS btw changed their display name from ahbk to I use NixOS btw.16:16:22
25 Mar 2025
@marie:marie.cologneMarie changed their display name from Marie to Marie Ramlow.17:42:27
@marie:marie.cologneMarie changed their display name from Marie Ramlow to Marie.17:44:54
26 Mar 2025
@hexa:lossy.networkhexado we have a prefetcher for pnpm?20:43:36
@hexa:lossy.networkhexa asking for one out of date discourse, which we run on discourse.nixos.org 20:45:34
@hexa:lossy.networkhexahm, enoscrumplex20:48:13
@hexa:lossy.networkhexa
nix-repl> :b pnpm_9.fetchDeps { pname = "discourse"; src = /tmp/discourse; hash = ""; }
warning: found empty hash, assuming 'sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA='
error: build of '/nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv' on 'ssh://hexa@build1.darmstadt.ccc.de' failed: builder for '/nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv' failed with exit code 1;
       last 8 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/9vkknlvpk9k2r13k1pa7xxfbnr8a7xrm-discourse
       > source root is discourse
       > Running phase: patchPhase
       > Running phase: updateAutotoolsGnuConfigScriptsPhase
       > Running phase: installPhase
       > yq: Error running jq: ScannerError: mapping values are not allowed in this context
       >   in "pnpm-lock.yaml", line 209, column 75.
       For full logs, run 'nix log /nix/store/i96hrd6k8k1d1kjccpkp9sqfdm1xwvlr-discourse-pnpm-deps.drv'.
20:56:43
@hexa:lossy.networkhexaah, my bad 😄 20:57:18
27 Mar 2025
@rosssmyth:matrix.org@rosssmyth:matrix.org

Hello. I have a pnpm+rsbuild package I am trying to build with nix. It used to build, but it does not any longer. I'm unsure in the exact change that has caused it, nor have my attempts at enabling logging actually enabled any useful logging. The error is:

> rsbuild build
>   Rsbuild v1.2.19
>
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> ● web ━━━━━━━━━━━━━━━━━━━━━━━━━ (93%) sealing after asset optimization          error   Compile error:
> Failed to compile, check the errors for troubleshooting.

This is a TS project with some WASM. I poked around in the wasm pack plugin source and couldn't find where it may attempt to fetch some release.

Outside of the sandbox it builds fine.

Doing a bisect shows that three dependencies were added to the project in the commit that broke the sandboxed builds:

"devDependencies": {
"vitest": "^2.1.8",
"wasm-pack": "^0.13.1",
"webpack-glsl-loader": "github:grieve/webpack-glsl-loader"
21:25:06
@rosssmyth:matrix.org@rosssmyth:matrix.org *

Hello. I have a pnpm+rsbuild package I am trying to build with nix. It used to build, but it does not any longer. I'm unsure in the exact change that has caused it, nor have my attempts at enabling logging actually enabled any useful logging. The error is:

> rsbuild build
>   Rsbuild v1.2.19
>
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> 🧐  Checking for wasm-pack...
>
> ✅  wasm-pack is installed at /build/source/node_modules/.bin/wasm-pack.
>
> â„šī¸  Compiling your crate in release mode...
>
> Error fetching release: getaddrinfo EAI_AGAIN github.com
> ● web ━━━━━━━━━━━━━━━━━━━━━━━━━ (93%) sealing after asset optimization          error   Compile error:
> Failed to compile, check the errors for troubleshooting.

This is a TS project with some WASM. I poked around in the wasm pack plugin source and couldn't find where it may attempt to fetch some release.

Outside of the sandbox it builds fine.

Doing a bisect shows that three dependencies were added to the project in the commit that broke the sandboxed builds:

"devDependencies": {
...
"vitest": "^2.1.8",
"wasm-pack": "^0.13.1",
"webpack-glsl-loader": "github:grieve/webpack-glsl-loader"
}
21:25:20

Show newer messages


Back to Room ListRoom Version: 6