| 9 Jul 2025 |
 dramforever | std::string | 01:46:53 |
 hexa | no | 01:46:56 |
| hexa | ❯ nix-prefetch-url 'https://selenium-release.storage.googleapis.com/3.141/selenium-server-standalone-3.141.59.jar'
path is '/nix/store/zksqwm6y2706rxx96v88dlw4hvvffw2i-selenium-server-standalone-3.141.59.jar'
1jzkx0ahsb27zzzfvjqv660x9fz2pbcddgmhdzdmasxns5vipxxc
| 01:47:15 |
 jonhermansen | Can you try removing that path from the Nix store? | 01:47:40 |
| hexa | I did | 01:47:49 |
| hexa | I didn't want to keep it around from earlier | 01:48:02 |
| jonhermansen | Ah, ok, good. So it has no dependency on the state of whats in /nix | 01:48:06 |
| jonhermansen | I had the file in my store, and I was getting that result | 01:48:19 |
| jonhermansen | so thats helpful to know too. Ok! | 01:48:30 |
| jonhermansen | I can write up a bug of some sort? It would be interesting to know what went wrong with this file | 01:48:57 |
| jonhermansen | The Content-Encoding issue could also happen on other packages, I guess? | 01:49:18 |
| dramforever | it's probably worth reporting | 01:50:18 |
| dramforever | but i'm not sure how much more gracefully we can handle it | 01:50:25 |
| jonhermansen | Nix should probably throw an error. | 01:50:26 |
| jonhermansen | Content-Encoding: None makes no sense. | 01:50:35 |
| dramforever | throw a better error | 01:50:35 |
| jonhermansen | * Content-Encoding: None makes no sense from the server and it can be surfaced to the user | 01:51:06 |
| dramforever | honestly having a "error while processing http request" would be helpful enough | 01:51:12 |
| jonhermansen | Relevant: https://github.com/NixOS/nix/issues/1568#issuecomment-330163663 | 02:01:18 |
| jonhermansen | * Relevant: https://github.com/NixOS/nix/issues/1568#issuecomment-330163060 | 02:14:18 |
| dramforever | probably not | 03:11:48 |
| dramforever | given that the encoding was there before | 03:11:59 |
|  sodiboo joined the room. | 18:29:01 |
 Sergei Zimmerman (xokdvium) | In reply to @nh2:matrix.org
looks like that message should be improved to make that clear Yeah sorry, I think that error message is my bad. | 18:58:48 |
| Sergei Zimmerman (xokdvium) | In reply to @jonhermansen:matrix.org
does it happen on Lix? IIRC libarchive is used to support more compression algorithms like bz2, which are not natively supported by curl. IFAIK lix did away with encodings not supported by curl. I wonder how libcurl handles such situations under the hood when using built-in support for decompression. | 19:04:07 |
| Sergei Zimmerman (xokdvium) | In reply to @jonhermansen:matrix.org
can you see verbose curl info when running Nix? -vvvvv (I think the level there is vomit) also makes libcurl output headers and other debug info. | 19:06:03 |
| 10 Jul 2025 |
 jade_ | yeah. lix has plausibly had more refactoring of the http client because it was previously doing standards noncompliant stuff | 03:44:30 |
| 11 Jul 2025 |
|  jollywater joined the room. | 01:11:43 |
| jollywater | any plans or current development in rust for Nix/NixOS? | 01:12:32 |
 K900 | Nix itself not much, Lix folks are exploring some things | 06:17:24 |
