| 10 May 2025 |
 niklaskorz | @qyliss:fairydust.space I'll take a look at the Rust std docs issue. Though if the patch did suddenly cause std docs for other targets to disappear that'd also mean upstream Rust would be affected, as they merged the patch in February 😳 (which would then be included in 1.87.0) | 20:54:52 |
 Alyssa Ross | In reply to @niklaskorz:matrix.org
@qyliss:fairydust.space I'll take a look at the Rust std docs issue. Though if the patch did suddenly cause std docs for other targets to disappear that'd also mean upstream Rust would be affected, as they merged the patch in February 😳 (which would then be included in 1.87.0) I think I found that it wasn't actually applying the patch that broke it, but adding the ebpf target | 22:12:45 |
| niklaskorz | In reply to @qyliss:fairydust.space
I think I found that it wasn't actually applying the patch that broke it, but adding the ebpf target Yeah I have a suspicion, commented it on the issue | 23:30:21 |
| niklaskorz | Basically it's installing the docs once for each target | 23:30:31 |
| niklaskorz | And each time removes the previous targets docs | 23:30:44 |
| niklaskorz | So the last target to be installed (bpf) is whose docs end up in the output | 23:31:02 |
| 11 May 2025 |
| niklaskorz | Created an upstream issue: https://github.com/rust-lang/rust/issues/140922 | 11:11:29 |
 Luke | Hey folks, can someone advise me how to use the openblas-static feature of ndarray-linalg with crane? It is pretty obvious that it is unable to download the tarball needed during build, due to network sandboxing... I don't understand how to fix this though? Do I need to add the tarball to the flake dependencies? How would I provide it to the rust crate if that is the case? | 19:52:48 |
| Luke | For a bit more context, in my Cargo.toml I have ndarray-linalg = { version = "0.16", features = ["openblas-static"] }, and when I build I see the error:
quick-start-deps> thread 'main' panicked at /nix/store/si15pm553934s2jl6h6w7ysn8vmjg4i6-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/openblas-src-0.10.11/build.rs:183:52:
quick-start-deps> called `Result::unwrap()` on an `Err` value: https://github.com/OpenMathLib/OpenBLAS/releases/download/v0.3.28/OpenBLAS-0.3.28.tar.gz: Dns Failed: resolve dns name 'github.com:443': failed to lookup address information: Temporary failure in name resolution
| 19:55:39 |
| 12 May 2025 |
 Toma | https://github.com/blas-lapack-rs/openblas-src/blob/04e9b023423744d24693458dfd0bc37d377a6f18/openblas-src/build.rs#L183
https://github.com/blas-lapack-rs/openblas-src/blob/04e9b023423744d24693458dfd0bc37d377a6f18/openblas-build/src/download.rs#L13
don't know what mechanism crane has for editing source files, but you may need to look into the code above and figure out a way to make the code above use a FOD created by fetchurl or fetchFromGitHub.
One idea would be to populate the directory where it would cache the download.
Another would be to patch the download function to just copy your fetchFromGitHub source directory to dest
| 00:10:48 |
| Toma | * https://github.com/blas-lapack-rs/openblas-src/blob/04e9b023423744d24693458dfd0bc37d377a6f18/openblas-src/build.rs#L183
https://github.com/blas-lapack-rs/openblas-src/blob/04e9b023423744d24693458dfd0bc37d377a6f18/openblas-build/src/download.rs#L13
I don't know what mechanism crane has for editing vendored source files, but you may need to look into the code above and figure out a way to use a FOD created by fetchurl or fetchFromGitHub instead f trying to download the project during build time.
One idea would be to populate the directory where it would cache the download.
Another would be to patch the download function to just copy your fetchFromGitHub source directory to dest
| 00:17:38 |
|  @saiko:knifepoint.net changed their profile picture. | 15:04:40 |
| @saiko:knifepoint.net changed their profile picture. | 15:08:18 |
| @saiko:knifepoint.net changed their profile picture. | 15:09:36 |
|  @fxomt:pub.solar joined the room. | 18:19:07 |
| 13 May 2025 |
|  kraem changed their profile picture. | 13:52:21 |
|  crop left the room. | 16:09:20 |
| 14 May 2025 |
|  amrosia joined the room. | 04:09:59 |
|  lily 🏳️⚧️ changed their profile picture. | 05:01:40 |
 cleverca22 | vcunat: are you familiar with pgrx? i see you made a commit on it in nixpkgs, and i'm having trouble with it | 05:09:15 |
 vcunat | No. I don't even recall what it is. | 05:09:56 |
| cleverca22 | ah, dang | 05:10:03 |
| cleverca22 | https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/rust/cargo-pgrx/buildPgrxExtension.nix is the file in question | 05:10:42 |
| cleverca22 | its some kind of framework for writing postgres extensions in rust | 05:10:57 |
| cleverca22 | but its being dumb, and trying to copy files to the extensions/ subdir of the postgres derivation | 05:11:14 |
| vcunat | I don't think I really touched the file, at a quick glance in the git log. | 05:12:12 |
| vcunat | * I don't think I've really touched the file, at a quick glance in the git log. | 05:12:18 |
| vcunat | It shows just a merge of staging-next to master. | 05:12:32 |
| cleverca22 | the git blame only shows you editing the line dealing with .pg_config output on postgres itself | 05:12:42 |
| cleverca22 | ah, maybe git blame is also blaming merge commits, rather then the commit your merging | 05:13:02 |
