| 4 Mar 2025 |
 eyJhb | The fix was this https://github.com/NixOS/nixpkgs/issues/385221#issuecomment-2689389743 , it was a .gitignore file that was the issue in the end. | 12:32:36 |
| eyJhb | Just weird that it's only now, that it became a issue. Because that line has been there forever. | 12:33:53 |
|  lassulus changed their profile picture. | 17:48:54 |
| 6 Mar 2025 |
 João Moreira | In reply to @magic_rb:matrix.redalder.org
Is it deprecated now? Do we now package things purely by FOD? many/all modern ecosystems in Nixpkgs are only really feasible with FODs. Until someone proves the contrary. I also dislike it, but that's what we have. | 04:24:32 |
| João Moreira | That's one of the reasons that I find Nix is far from optimal as a local development environment. | 04:26:38 |
| João Moreira | * That's one of the reasons that I find Nix is far from optimal as a local development environment other than just a simple devshell. | 04:28:12 |
| João Moreira | Guix people totally discard FOD on their official repos. I'm not sure if non-guix people embraced FODs. | 04:30:42 |
| João Moreira | * Guix people totally discard FODs on their official repos. I'm not sure if non-guix people embraced FODs. | 04:30:55 |
| João Moreira | * Guix totally discards FODs on their official repos. I'm not sure if non-guix people embraced FODs. | 04:31:14 |
| João Moreira | * Guix totally discards FODs on their official repos. I'm not sure if nonguix people embraced FODs. | 04:32:00 |
 magic_rb | In reply to @joaomoreira:matrix.org
many/all modern ecosystems in Nixpkgs are only really feasible with FODs. Until someone proves the contrary. I also dislike it, but that's what we have. Oh i know and agree. But still make me sad :( | 05:33:49 |
| 7 Mar 2025 |
|  Qyriad changed their display name from Qyriad to qyriad. | 16:44:27 |
| 8 Mar 2025 |
| Qyriad changed their display name from qyriad to Qyriad. | 21:41:03 |
| 11 Mar 2025 |
|  avocadoom changed their profile picture. | 16:36:23 |
| 20 Mar 2025 |
|  I use NixOS btw set a profile picture. | 08:17:25 |
| I use NixOS btw changed their profile picture. | 08:17:57 |
| I use NixOS btw changed their display name from ahbk to I use NixOS btw. | 16:16:22 |
| 25 Mar 2025 |
|  Marie changed their display name from Marie to Marie Ramlow. | 17:42:27 |
| Marie changed their display name from Marie Ramlow to Marie. | 17:44:54 |
| 26 Mar 2025 |
 hexa | do we have a prefetcher for pnpm? | 20:43:36 |
| hexa | asking for one out of date discourse, which we run on discourse.nixos.org | 20:45:34 |
| hexa | hm, enoscrumplex | 20:48:13 |
| hexa | 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 | ah, my bad 😄 | 20:57:18 |
| 27 Mar 2025 |
 @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 | * 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 |
| @rosssmyth:matrix.org | If anyone has any ideas as to what could be the issue or how to debug it further please let me know | 21:25:34 |
| @rosssmyth:matrix.org | My initial thought was something with github dependencies, but creating a dummy project with only the webpack-glsl-loader dependency works fine | 21:26:20 |
| @rosssmyth:matrix.org | Ok I removed the "wasm-pack" line in the package.json and it works | 21:31:08 |
| @rosssmyth:matrix.org | It does complain that it is not able to download wasm-opt, but it does compile | 21:32:57 |
