!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

211 Members
62 Servers

Load older messages


SenderMessageTime
6 Oct 2023
@marie:marie.cologneMariei tried it 2 times got 2 different errors20:09:04
@marie:marie.cologneMarielooking good20:09:07
@marie:marie.cologneMarie
Error: unknown error

Caused by:
    [55] Failed sending data to the peer
Error: unknown error

Caused by:
    [18] Transferred a partial file
20:09:36
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
I wonder if all that is needed is bumping curl-sys
(If all that is needed to fix this issue of the past several weeks is to bump the crate deps on the fetcher, I'm gonna be hella embarrassed)
20:09:47
@lily:lily.flowersLily Foster
In reply to @marie:marie.cologne
Error: unknown error

Caused by:
    [55] Failed sending data to the peer
Error: unknown error

Caused by:
    [18] Transferred a partial file
Hmmmm those should be network errors, not unknown errors
20:10:04
@lily:lily.flowersLily FosterSo the curl crate is still busted20:10:14
@lily:lily.flowersLily FosterI'll look more later20:10:18
@marie:marie.cologneMariei thought i might have a clue by commenting stuff out, but turns out it's just that when i run prefetch-npm-deps via cargo run (--release) it works fine, only the one built with nix fails20:35:46
@lily:lily.flowersLily Foster
In reply to @marie:marie.cologne
i thought i might have a clue by commenting stuff out, but turns out it's just that when i run prefetch-npm-deps via cargo run (--release) it works fine, only the one built with nix fails
That makes even less sense... What curl are you linking against? Are you on nixos
20:38:18
@lily:lily.flowersLily Foster
In reply to @marie:marie.cologne
i thought i might have a clue by commenting stuff out, but turns out it's just that when i run prefetch-npm-deps via cargo run (--release) it works fine, only the one built with nix fails
* That makes even less sense... What curl are you linking against? Are you on nixos?
20:38:21
@marie:marie.cologneMariei'm on debian in wsl20:38:51
@marie:marie.cologneMariebut probably my system's curl20:38:58
@lily:lily.flowersLily FosterI wonder if this is some problem with curl 8.3.020:39:17
@lily:lily.flowersLily FosterThat would line up with when the problems started20:39:22
@marie:marie.cologneMariemy curl is 7.88.120:39:33
@lily:lily.flowersLily Fosteroh oof, ancient version20:39:40
@marie:marie.cologneMariedebian moment20:39:45
@lily:lily.flowersLily FosterOkay apparently not that ancient. It was admittedly just feb of this year20:40:14
@lily:lily.flowersLily FosterRegardless, it seems likelier to be a curl 8.3.0 problem maybe20:40:26
@marie:marie.cologneMarieany idea on how i could force cargo to link against nix's curl20:40:38
@marie:marie.cologneMarie * any idea on how i could force cargo to link against nixpkgs curl20:41:01
@lily:lily.flowersLily Foster nix-shell -p pkg-config curl 20:41:28
@lily:lily.flowersLily FosterAnd build in that shell20:41:34
@marie:marie.cologneMariethats what i did, but it's still working20:41:47
@marie:marie.cologneMariei'm not sure if it actually uses the right curl20:42:01
@marie:marie.cologneMariei could also just uninstall curl 20:42:17
@lily:lily.flowersLily Foster ldd target/release/prefetch-npm-deps? 20:42:18
@lily:lily.flowersLily Foster
In reply to @marie:marie.cologne
i could also just uninstall curl
I doubt debian would allow that 😅
20:42:28
@lily:lily.flowersLily FosterActually. It's probably not even using system curl20:42:35
@lily:lily.flowersLily FosterIt's possibly building it's own vendored curl20:42:43

Show newer messages


Back to Room ListRoom Version: 6