| 20 Feb 2024 |
 @janik0:matrix.org | okay, thank's that explains the error :) | 17:03:59 |
| 22 Feb 2024 |
 hexa | can we? https://github.com/samueldr/ofborg-viewer/pull/28 | 00:13:11 |
| hexa | please? | 00:13:14 |
| hexa | dark mode! | 00:13:19 |
 @adam:robins.wtf | > Use nodejs 20 instead of nodejs 6
| 01:31:02 |
| 24 Feb 2024 |
 Sandro 🐧 | In reply to @hexa:lossy.network
can we? https://github.com/samueldr/ofborg-viewer/pull/28 Can we get logs grouped by package? 🥺 | 14:58:00 |
| hexa | that is pretty much orthogonal to what you quoted. | 14:58:38 |
| Sandro 🐧 | I mean if someone is working on it, maybe that's the time to implement new features? | 14:59:36 |
| hexa | there is no clear maintenance declared on the project | 14:59:42 |
| hexa | maybe, maybe not | 14:59:54 |
| 25 Feb 2024 |
|  Simon Menke set a profile picture. | 15:25:56 |
| 28 Feb 2024 |
 Alyssa Ross | Could we have higher darwin timeouts for staging PRs, or something? OfBorg Darwin is basically completely useless on staging PRs, because it can never get past LLVM, which takes >3600 seconds to build. | 14:17:09 |
| hexa | I think we're more affected by the sheer lack of build capacity for aarch64-darwin than its timeouts | 14:19:39 |
| hexa | but yeah, I've seen it often fail on llvm for … basically anything staging | 14:20:11 |
| Alyssa Ross | well, currently we're wasting a lot of that capacity on LLVM builds that are never going to finish | 14:20:39 |
| hexa | true | 14:20:46 |
