15 Oct 2024 |
emily | kicking Hydra to get an early channel eval maybe? | 22:46:21 |
hexa | bumped the -small jobsets to front | 22:49:28 |
hexa | * bumped the -small jobsets to the front of the queue | 22:49:35 |
f0x | In reply to @hexa:lossy.network I'm kicking the hydra jobsets next not really sure what it entails, like what you mentioned here for the firefox stuff | 22:49:42 |
hexa | that meant triggering an evaluation | 22:49:59 |
hexa | and evaluation results in all jobs being identified and queued for execution | 22:50:17 |
hexa | that happens on a schedule and I triggered it manually | 22:50:46 |
f0x | ahh I see. In the meantime also did some searching and looking at the wiki; a fix like this gets backported to release-24.05, which normally would be picked up by Hydra every once in a while but can be manually triggered too, and when the build/tests pass it gets published to the nixos-24.05 branch, which also 'updates' the channel, and cache.nixos.org? | 22:52:45 |
hexa | build results get pushed to the cache as soon as they finish building | 22:54:49 |
hexa | and yes, once a jobset has completed all jobs, and its tested set has completed successfully, hydra will update the channel and its correlating github branch | 22:55:24 |
hexa | result-24.05 -> hydra -> nixos-24.05{,-small} | 22:55:37 |
hexa | pol created this uml diagram at some point http://www.plantuml.com/plantuml/uml/rPDDYzim48Rl-XKlz984ih3NvB3Rfj2UagKVz3oMnhPgMJBIYDr0VdoziWCrWQM7NlPYHjOpCyzhy6CIYf9xfyIAOnpjo-axjZYqv3qxvC6GS5AfitwWI3qgqbqJG_Rc45o8-63kMTVtIbtcwlBrR29Tb2gZ5L27s2a0U6qRyCJH1cCrENSkhssDrKT_nkzG8MMjEQKwkuSrRCBgp6aDQTaN5DZzYBPfE6A8GRF9aI5XreIUhDE-m6F1MFcmdaxUsFfQJIgp6wWXwzyoZ3mmoMmmvxlwF6NdokA64-eOUdonqkPg_rSddblhHfT3mM1OM0kR4h4OmWUPijuOJexNRKT-Bjzfi_7sPUYQj9EOVRVPb7LBUCG_PUiC1j8TZNepimWzWpy75yYWAZn5iJLfIP00JRhbkt5RI7SXDlECeZZlkXsur0opv5Q7lhAUpR_RBYwEhwFG1vFTulPRzX1EyaQ-_ntmDc7sIQXol4qzEVVk4fP3px5XfQRVxFJvjCElbWGj3GDxj1pvOQyMw5Ygn_6HU_S7 | 22:56:47 |
hexa | * pol created this uml diagram at some point | 22:56:58 |
emily | I like the todo :) | 22:57:48 |
hexa | 🙂 | 22:58:06 |
f0x | deployed & tested the commit for element-web, all good :) | 23:06:42 |
f0x | and ffs looking at the fix.. I remember looking through that exact piece of code and wondering if the way they compared url/path/origin on a string instead of parsed url could lead to issues... | 23:07:45 |
16 Oct 2024 |
| @eisfunke:eisfunke.com left the room. | 13:36:03 |
17 Oct 2024 |
hexa | https://github.com/NixOS/nixpkgs/pull/349172 | 00:38:18 |
Fabián Heredia | Hi, just to get a bit more context, has the listed maintainer participated in previous updates? | 00:41:10 |
emily | that package is deployed on discourse.nixos.org by flying circus right? wonder if they could spare maintainer resources for it | 00:41:27 |
emily | Fabián Heredia: looks like they're quite inactive in Nixpkgs these days | 00:41:58 |
Fabián Heredia | Ok, then this does makes sense. Hopefully someone else steps up to maintain this package UnU | 00:42:27 |
hexa | Redacted or Malformed Event | 00:47:15 |
hexa | Redacted or Malformed Event | 00:47:49 |
hexa | Redacted or Malformed Event | 00:47:53 |
emily | "NixOS community forum. Hosted by flyingcircus.io, running on NixOS 23.11." uhh 🫠| 00:49:09 |
emily | I hope the text is just out of date | 00:49:13 |
| Mic92 changed their display name from Mic92 to Mic3000. | 06:51:17 |
| Mic92 changed their display name from Mic3000 to Mic3000 🌋. | 06:51:46 |