| 27 Mar 2024 |
 atemu12 | Both | 20:47:26 |
| atemu12 | And probably both muppets too | 20:47:37 |
 eyJhb | I gave up, I don't have enough space for that. | 21:23:40 |
| eyJhb | * I gave up, I don't have enough space for it. | 21:23:44 |
| eyJhb | What kind of hardware are you running Atemu ? :p | 21:23:54 |
| 28 Mar 2024 |
| atemu12 | 7950x3d with 64GB | 03:26:22 |
| eyJhb | In reply to @atemu12:matrix.org
7950x3d with 64GB What about storage? I tried to get the ASOP mirror setup. It's more than 700 GB in size.... | 06:36:43 |
| atemu12 | Ah I just put it on my NAS | 06:37:55 |
| atemu12 | It's a little over a Terabyte or so | 06:38:04 |
| atemu12 | And I've got like 18TB | 06:38:21 |
| atemu12 | And I don't need to back it up since it's just a mirror | 06:38:36 |
| eyJhb | https://mirrors.tuna.tsinghua.edu.cn/status/ | 06:40:45 |
| eyJhb | Current size according to that is 2.24TB. That's insane 😅 | 06:41:11 |
| atemu12 | Might be a full mirror | 06:41:27 |
| atemu12 | repo only mirrors the "relevant" branches by default | 06:41:53 |
| eyJhb | The one I just tied to create was over 800GB when I ran out of space. | 06:42:47 |
| eyJhb | Seems like it's mirrors all branches, otherwise it'll be insanely large | 06:43:08 |
| eyJhb | Might have to rethink it. Not sure I can actually do that part myself, which is annoying. My "NAS" doesn't have much storage | 06:43:55 |
| atemu12 | :/ | 06:44:07 |
| atemu12 | btw do note that repo and device dirs are separate | 06:44:45 |
| eyJhb | In reply to @atemu12:matrix.org
:/ Nix ASOP mirror when? :D | 06:45:25 |
| 29 Mar 2024 |
|  SebTM joined the room. | 03:39:13 |
|  CyberShadow joined the room. | 09:15:49 |
| eyJhb |
I suspect that to be the case too. Considering that nixpkgs scripts are executed without errexit or any other bash strict mode flags, I am not at all surprised about such bugs.
I was quite sure that it was required for all phases to exit with code 0. Isn't that the case?
| 09:16:52 |
| CyberShadow | In reply to @eyjhb:eyjhb.dk
I suspect that to be the case too. Considering that nixpkgs scripts are executed without errexit or any other bash strict mode flags, I am not at all surprised about such bugs.
I was quite sure that it was required for all phases to exit with code 0. Isn't that the case?
Hi!
Yes, but without errexit, you can have a failing command followed by a successful command, and the failing command won't stop the script, and the successful command will still run and cause the script to exit with success (status of last command)
| 09:18:50 |
| eyJhb | Ahhhhhhhhhhhhhhhhhhhh, yeah that makes sense | 09:19:15 |
| eyJhb | I wonder how much of Nix would break with errexit. Most likely, a lot. | 09:19:30 |
| CyberShadow | Yes, same is true for most shell scripts written without it in mind in general | 09:20:35 |
| CyberShadow | There are gotchas like grep returning failure if it doesn't find at least one match, so a lot of grep invocations need to be pacified with || true OSLT | 09:21:17 |
| eyJhb | Yeah true. But I think we have many hidden failures as well. Bash might not have been the best way to package things :p | 09:22:29 |
