| 13 Mar 2026 |
 emily | I've thought more lately about how we can avoid conflicts arising in the first place though | 12:12:07 |
| emily | the ideal would be that we don't get two PRs that don't know about each other both landing in different "timelines" at all | 12:12:38 |
| emily | multiple merge queues kind of dampen the benefit of having them | 12:13:52 |
 Ramses 🇵🇸 | Yeah, AFAICT, the commit to switch kitty to a non-EOL go could've gone to master, which would've avoided this conflict and discussion. But maybe there were other reasons why it didn't, I don't have the context | 14:20:46 |
| Ramses 🇵🇸 | But in general indeed it's hard to know when you make a PR to master, that there are any conflicting changes on staging(-next). And even if we detected this in CI, I don't think it's always possible to modify the changes such that they cleanly apply on both branches | 14:22:24 |
| emily | well, I had some ideas for making it so that they always can :) but which ones are practical, not sure | 15:52:03 |
| emily | at the very least having to explicitly handle it when such a situation arrives rather than being able to sleepwalk into it would be goo | 15:52:22 |
| emily | * at the very least having to explicitly handle it when such a situation arrives rather than being able to sleepwalk into it would be good | 15:52:33 |
| Ramses 🇵🇸 | In reply to @emilazy:matrix.org
at the very least having to explicitly handle it when such a situation arrives rather than being able to sleepwalk into it would be good Definitely | 17:58:55 |
| 15 Mar 2026 |
 whispers [& it/fae] | hai. chromium seems to be having issues on staging-next on my system. if i build (well, substitute) chromium on the latest staging-next, trying to run it immediately sigills on my system (x86_64-linux nixos):
~> nix run github:nixos/nixpkgs/521d05a303dcd44e66f27ad94cc244adaabace12#chromium
[0314/233404.245952:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
fish: Job 1, 'nix run github:nixos/nixpkgs/52…' terminated by signal SIGILL (Illegal instruction)
whereas nix run github:nixos/nixpkgs/master#chromium launches successfully. this might be a »my system is fucked issue«, but i'm wondering if anyone else can maybe reproduce this? | 03:37:52 |
| whispers [& it/fae] | …and now that i post i remembered there's a nixos test. that indeed does fail, so i don't think it's just a me thing. fun | 03:40:38 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test. that indeed does fail as well, so i don't think it's just a me thing. fun | 03:40:43 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun | 03:42:48 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun. i'll make an issue i suppose | 03:46:24 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun. i'll investigate & make an issue | 03:50:27 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun. i'll make an issue i suppose | 03:51:33 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun. i'll make an issue | 03:58:49 |
| whispers [& it/fae] | * …and now that i post i remembered there's a nixos test for a more isolated environment. that indeed does fail as well, so i don't think it's just a me thing. fun. i'll make an issue (https://github.com/NixOS/nixpkgs/issues/499982) | 04:07:23 |
 dramforever | looks like a strict-flex-arrays violation | 05:38:25 |
| dramforever | https://source.chromium.org/chromium/chromium/src/+/main:base/metrics/persistent_histogram_allocator.cc;drc=854512ccb0f2d89203be1ec15dbea3fb4e31a326
UNSAFE_TODO(memcpy(histogram_data->name, name.data(), name.size()));
// Space for the histogram name will be added during the actual allocation
// request. This must be the last field of the structure. A zero-size array
// or a "flexible" array would be preferred but is not (yet) valid C++.
char name[sizeof(uint64_t)]; // Force 64-bit alignment on 32-bit builds.
| 05:39:04 |
| dramforever | can my laptop build chromium? only one way to find out | 05:44:12 |
| emily | UNSAFE_TODO oh okay | 05:46:18 |
| emily | reassuring words to come across when your browser is crashing | 05:46:38 |
| dramforever | how much disk space does it take to build this thing asking for a friend | 05:49:03 |
| emily | I think it's many gigs to even just check out the repository | 05:50:21 |
| emily | and its several copies of Debian or whatever | 05:50:25 |
| dramforever | i have 622G according to df -lh | 05:51:05 |
| emily | that seems like it should be more than enough | 05:51:40 |
| emily | RAM OTOH… | 05:51:44 |
| dramforever | 32G ram, m1 pro | 05:52:28 |
