!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

206 Members
59 Servers

Load older messages


SenderMessageTime
9 Oct 2023
@lily:lily.flowersLily Foster Okay I think we're fixed now! Try it again Cobalt, same branch 15:42:26
@lily:lily.flowersLily Foster
In reply to @c0ba1t:matrix.org
This error seems frustrating, when running the code outside of nix (run|build) it doesn't appear to be reproducible. Ig my network needs to become more unstable
Yeah no clue why it would be related to that. Except maybe namespacing shenanigans
15:42:51
@lily:lily.flowersLily FosterOh you mean when built from nix, not when run in a nix build15:43:17
@lily:lily.flowersLily FosterYeah no clue there15:43:20
@lily:lily.flowersLily FosterExcept http/2 shenanigans since if you build it with static libcurl, then it'll build without libnghttp2 support15:43:39
@lily:lily.flowersLily FosterBut our libcurl does use it15:43:42
@lily:lily.flowersLily FosterEither way it's not the core issue, just side effects15:43:50
@c0ba1t:matrix.orgCobaltFirst run was successful, reruns may take a few minutes 15:45:22
@lily:lily.flowersLily FosterNo worries! If you're able, feel free to rerun it as much as you can in loop and just come back to it when you can. I'm pretty sure I think I got it now15:45:46
@lily:lily.flowersLily FosterI'm gonna open https://github.com/NixOS/nixpkgs/compare/master...lilyinstarlight:nixpkgs:fix/prefetch-npm-deps-network-error-recovery as a PR if a few people confirm it works15:46:02
@lily:lily.flowersLily Foster Maybe Marie too 15:46:06
@c0ba1t:matrix.orgCobalt
In reply to @lily:lily.flowers
No worries! If you're able, feel free to rerun it as much as you can in loop and just come back to it when you can. I'm pretty sure I think I got it now
Sure, I'll try with 50 runs for now. The first 10 were successful, so it seems resolved.
15:49:11
@lily:lily.flowersLily Foster Also thiloho ^ 15:49:15
@lily:lily.flowersLily Foster * Also thiloho, if you could try ^ 15:49:24
@lily:lily.flowersLily FosterI've opened https://github.com/NixOS/nixpkgs/pull/26001115:57:00
@c0ba1t:matrix.orgCobalt
In reply to @c0ba1t:matrix.org
Sure, I'll try with 50 runs for now. The first 10 were successful, so it seems resolved.
All 50 runs were successful
16:08:20
@marie:marie.cologneMarie
In reply to @lily:lily.flowers
Maybe Marie too
will do!
16:08:39
10 Oct 2023
@drupol:matrix.org@drupol:matrix.org Hey, I'm trying to package Terminalizer with buildNpmPackage. 06:26:15
@drupol:matrix.org@drupol:matrix.org
{ buildNpmPackage
, fetchFromGitHub
}:

buildNpmPackage rec {
  pname = "terminalizer";
  version = "0.11.0";

  src = fetchFromGitHub {
    owner = "faressoft";
    repo = "terminalizer";
    rev = "v${version}";
    hash = "sha256-+62OM7pVtBRpeniO4e3X41R8nnk95Dk1EUL3HEEIZe4=";
  };

  npmDepsHash = "sha256-5em+VGNb+sbO7nPSvbo99fTi9O2RIUjBG2KvMRz6N6M=";

  meta.mainProgram = "terminalizer";
}
06:26:24
@drupol:matrix.org@drupol:matrix.orgAt the end of the build, it crashes... 06:26:32
@drupol:matrix.org@drupol:matrix.org
      > Validating consistency between /build/source/package-lock.json and /nix/store/1481hlnkqx4vw8y25v60gliynk07dwla-terminalizer-0.11.0-npm-deps/package-lock.json
       > Installing dependencies
       > npm ERR! code ENOTCACHED
       > npm ERR! request to https://registry.npmjs.org/yallist failed: cache mode is 'only-if-cached' but no cached response is available.
       > 
       > npm ERR! Log files were not written due to an error writing to the directory: /nix/store/1481hlnkqx4vw8y25v60gliynk07dwla-terminalizer-0.11.0-npm-deps/_logs
       > npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
       > 
       > ERROR: npm failed to install dependencies
       >
       > Here are a few things you can try, depending on the error:

06:26:45
@drupol:matrix.org@drupol:matrix.orgDo you know what I can do to fix this?06:26:55
@drupol:matrix.org@drupol:matrix.orgFind terminalizer here: https://github.com/faressoft/terminalizer06:27:07
@drupol:matrix.org@drupol:matrix.org *
       > Validating consistency between /build/source/package-lock.json and /nix/store/1481hlnkqx4vw8y25v60gliynk07dwla-terminalizer-0.11.0-npm-deps/package-lock.json
       > Installing dependencies
       > npm ERR! code ENOTCACHED
       > npm ERR! request to https://registry.npmjs.org/yallist failed: cache mode is 'only-if-cached' but no cached response is available.
       > 
       > npm ERR! Log files were not written due to an error writing to the directory: /nix/store/1481hlnkqx4vw8y25v60gliynk07dwla-terminalizer-0.11.0-npm-deps/_logs
       > npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
       > 
       > ERROR: npm failed to install dependencies
       >
       > Here are a few things you can try, depending on the error:

06:34:53
@drupol:matrix.org@drupol:matrix.org I finally switched to asciinema but it would be nice to have Terminalizer as well :) 08:02:37
@lily:lily.flowersLily Foster
In reply to @drupol:matrix.org
Find terminalizer here: https://github.com/faressoft/terminalizer
Busted upstream lockfile. Yallist is missing integrity/resolved fields :(
10:29:35
@lily:lily.flowersLily FosterI do still have a half-written local branch to refactor lockfile fixup enough for allowing injecting that info, but I've been too preoccupied for the last month or two fixing stuff to finish that10:30:26
@lily:lily.flowersLily FosterI found this the other day if you wanted to PR to upstream a fixed lockfile: https://github.com/jeslie0/npm-lockfile-fix (and you could then fetchpatch it just fine)10:33:35
@drupol:matrix.org@drupol:matrix.orgThanks :) I'll might probably open a PR against the upstream project11:42:04
@marie:marie.cologneMarie Lily Foster: i ran some tests over night, 1000 runs without a failure 11:55:25

Show newer messages


Back to Room ListRoom Version: 6