!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

208 Members
59 Servers

Load older messages

SenderMessageTime
12 Nov 2023
@lily:lily.flowersLily Fosterturning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic bacisally means they will eventually be tried one at a time if that causes problems noe16:50:59
@lily:lily.flowersLily Foster* turning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic bacisally means they will eventually be tried one at a time if that causes problems now16:51:02
@lily:lily.flowersLily Foster* turning off parallelism shouldn't ever help with anything but making the logs more coherent unless your internet link gets spooked by the concurrent connections to the same domain. but even then the retry backoff logic basically means they will eventually be tried one at a time if that causes problems now16:51:17
13 Nov 2023
@keiichi:matrix.org@keiichi:matrix.org

I try to build a small package.json with buildNpmPackage. I seem to deterministically (repeatdly) hit:

       > invalid type nullinvalid type nullnpm ERR! code ENOTCACHED
       > npm ERR! request to https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz failed: cache mode is 'only-if-cached' but no cached response is available.

while nix-prefetch-url https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz works fine. what could explain this specific error ?

16:57:15
@lily:lily.flowersLily Foster
In reply to @keiichi:matrix.org

I try to build a small package.json with buildNpmPackage. I seem to deterministically (repeatdly) hit:

       > invalid type nullinvalid type nullnpm ERR! code ENOTCACHED
       > npm ERR! request to https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz failed: cache mode is 'only-if-cached' but no cached response is available.

while nix-prefetch-url https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz works fine. what could explain this specific error ?

Prefetching that URL has nothing to do with npm trying to do something it shouldn't in the nix sandbox. Can you share the full lock and the package-lock.json file you are using? 		16:59:01
@lily:lily.flowersLily Foster (ENOTCACHED should really be renamed to ENPMDIDABADTHINGAGAIN) 16:59:28
@keiichi:matrix.org@keiichi:matrix.orgsure, where is the best place to upload those files ?17:02:43
@lily:lily.flowersLily Fosteri mean you could put them on a pastebin. or https://tmp.lily.flowers/17:03:21
@lily:lily.flowersLily Foster
In reply to @keiichi:matrix.org

I try to build a small package.json with buildNpmPackage. I seem to deterministically (repeatdly) hit:

       > invalid type nullinvalid type nullnpm ERR! code ENOTCACHED
       > npm ERR! request to https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz failed: cache mode is 'only-if-cached' but no cached response is available.

while nix-prefetch-url https://registry.npmjs.org/@pulumi/query/-/query-0.3.0.tgz works fine. what could explain this specific error ?

* Prefetching that URL has nothing to do with npm trying to do something it shouldn't in the nix sandbox. Can you share the full log and the package-lock.json file you are using? 		17:03:41
@keiichi:matrix.org@keiichi:matrix.orghttps://tmp.lily.flowers/package.json and the package-lock.json https://tmp.lily.flowers/wuhszr17:06:22
@lily:lily.flowersLily Fostercan you share full build log?17:08:41
@lily:lily.flowersLily Fosteri don't see anything wrong with this lockfile17:08:46
@keiichi:matrix.org@keiichi:matrix.org

I build it with :

            pulumiSdks = pkgs.buildNpmPackage {
              pname = "ci-runner";
              version = "1.0.0";

              src = ./.;

              npmDepsHash = "sha256-mUNksrt+S90RoXTofPSwhRAMw5wqrdjKtINkUA0KrQE=";

              dontNpmBuild = true;
              dontBuild = true;

};

and a nixpkgs of 8ac5c1191b06206f8508595f0c17332b851240f0

17:10:01
@keiichi:matrix.org@keiichi:matrix.orglet me regenerate the log17:10:50
@lily:lily.flowersLily Fosteri mean i've got it building on my end now17:13:18
@lily:lily.flowersLily Fosteroh it's happening during prune...??17:14:22
@lily:lily.flowersLily Fosterwhat the hell17:14:26
@lily:lily.flowersLily Foster(why does npm prune logic always have to be so horribly busted)17:15:37
@keiichi:matrix.org@keiichi:matrix.org yes. I haven't tried dontNpmPrune = true yet, trying 17:25:18
@lily:lily.flowersLily Foster apparently npm prunes deps but then decides that the node_modules/@pulumi/query (that already has been reified when deps were built) is insufficient and needs to be re-reified. which would be fine except it also decides that the cache is for losers and ignores or otherwise gets too spooked by the existing entry for query-0.3.0.tgz 17:27:43
@lily:lily.flowersLily Fosterwhic17:28:00
@lily:lily.flowersLily Foster * which17:28:01
@lily:lily.flowersLily Fostermakes no sense17:28:03
@lily:lily.flowersLily Foster npm is very eager to silently get spooked and redownload though so i'm ultimately not surprised 17:28:21
@lily:lily.flowersLily Fosterit would be nice to know whether it got spooked or didn't try the cache to begin with though (and even npm's debug logging does not log a lot of the situations where it gets spooked and bails for, unfortunately)17:28:54
@keiichi:matrix.org@keiichi:matrix.orgdontNpmPrune "fixed" the build ty for help I hope this helps improving the understanding of npm xD17:30:03
@lily:lily.flowersLily Fosteri'm trying to root out the bug now17:33:18
@lily:lily.flowersLily Fosterin npm17:33:20
@lily:lily.flowersLily Fosterwhich upstream will invariably ignore a PR for but oh well17:33:28
@lily:lily.flowersLily Foster okay so npm is actually just removing the cache value from npmrc? 17:39:14

Show newer messages

Back to Room ListRoom Version: 6