| 22 Sep 2025 |
 emily | but too late for this cycle | 19:56:48 |
 Lun | Problem: electron/chromium seem to be broken
Pinning an earlier LLVM builds for me but it looks like rust having a newer LLVM risks incompatible bitcode errors so isn't a correct fix
- earlier patch ensuring chromium always uses same LLVM version as rust https://github.com/NixOS/nixpkgs/commit/a71762621bb17c2c19a31fa50926c78007907d76
- patch to pin to 20 that's probably wrong and logs of the failure https://gist.github.com/LunNova/219767a842bdbda4e43d3766db199d4d
| 20:45:14 |
| Lun | * Problem: electron/chromium seem to be broken in staging-next
Pinning an earlier LLVM builds for me but it looks like rust having a newer LLVM risks incompatible bitcode errors so isn't a correct fix
- earlier patch ensuring chromium always uses same LLVM version as rust https://github.com/NixOS/nixpkgs/commit/a71762621bb17c2c19a31fa50926c78007907d76
- patch to pin to 20 that's probably wrong and logs of the failure https://gist.github.com/LunNova/219767a842bdbda4e43d3766db199d4d
| 20:45:21 |
| emily | we can probably backport a patch | 20:47:57 |
| emily | "chromium relies on these invalid enum values to represent histogram data" 🙃 | 20:48:12 |
| Lun | I think patching the enums used with the UMA_HISTOGRAM_ENUMERATION macro to have an underlying type makes it not UB but there are a lot of different enums used with UMA_HISTOGRAM_ENUMERATION. I failed to find a patch in the chromium repo so I may be missing something silly. | 20:48:15 |
| Lun | * I think patching the enums used with the UMA_HISTOGRAM_ENUMERATION macro to have a specific underlying numeric type makes it not UB but there are a lot of different enums used with UMA_HISTOGRAM_ENUMERATION. I failed to find a patch in the chromium repo so I may be missing something silly. | 20:48:48 |
| emily | no upstream report? | 20:50:23 |
| emily | cc emily | 20:50:29 |
| emily | didn't know Chromium was downstream of LLVM, gues we should be testing it along with Firefox | 20:50:44 |
| Lun | https://chromium-review.googlesource.com/c/chromium/src/+/6633292/2/base/metrics/histogram_macros_internal.h yay! | 20:53:30 |
| Lun | I was wrong about how hard it is to fix :phew: | 20:53:54 |
| emily | nice | 20:54:39 |
| emily | my impression is that the browsers try new compiler versions early | 20:54:55 |
 hexa | compiler updates are an obvious performance and security win, no? | 21:02:03 |
| emily | depends, they do get better at exploiting UB 😅 | 21:03:28 |
| Lun | i misdiagnosed it and it was just using an invalid enum value to represent the number of possible values
and let's be fair to them! it's only been UB since a 2014 wg meeting | 21:05:03 |
 emily | chromium rolls virtually every dependency on a regular schedule and thus is always ahead of us, so yeah | 21:29:47 |
 Gaétan Lepage | thrift (dependency of arrow-cpp) is currently broken on staging-next. | 22:01:16 |
| Gaétan Lepage | * thrift (dependency of arrow-cpp) is currently broken on staging-next.
Compatibility with CMake < 3.5 has been removed from CMake.
| 22:01:27 |
| emily | nim65s has a WIP(?) fix | 22:02:02 |
| emily | it is known | 22:02:10 |
 Grimmauld (any/all) | a bunch of things broke, chances are patches exist somewhere | 22:02:22 |
 nim65s | yep, still planing to do this tonight | 22:02:53 |
| Grimmauld (any/all) | i spent the evening teaching a friend about fetchpatch and guided them through fixing three packages, its basically all just grunt work | 22:02:57 |
| emily | we found the tests are broken in thrift | 22:03:13 |
| emily | or that the fix bump breaks them | 22:03:16 |
| emily | so that was fun | 22:03:16 |
| nim65s | that was in https://github.com/NixOS/nixpkgs/pull/444660, but I removed thrift from there for now, as it was the only not-ready thing | 22:04:03 |
| nim65s | oh, merge conflict | 22:04:34 |
