Sender | Message | Time |
---|---|---|
20 Nov 2024 | ||
In reply to @zowoq:matrix.orgwhat's the relationship between r-ryantm and ofborg? like, why does high load on ofborg result in r-ryantm being throttled? | 22:06:20 | |
are they running on the same infra? | 22:06:57 | |
21 Nov 2024 | ||
No, they don't run on the same infra. It gets throttled to keep the PR eval queue wait time reasonable, unfortunately ofborg seems to be kinda broken at the moment and the eval queue just keeps getting worse. Ofborg is being replaced with github actions so hopefully won't need to throttle it. https://github.com/NixOS/nixpkgs/issues/355847 | 02:18:11 | |
10:27:01 | ||
22 Nov 2024 | ||
17:49:25 | ||
25 Nov 2024 | ||
looking at this, it seems like the package that's printed in the logs is [generic.nix ](https://github.com/NixOS/nixpkgs /tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/generic.nix) rather than [ 4.5.nix ](https://github.com/NixOS/nixpkgs /tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix), which imports it. is that a bug? | 12:19:45 | |
* looking at this, it seems like the package that's printed in the logs is generic.nix rather than [4.5.nix ](https://github.com/NixOS/nixpkgs/tree/master/pkgs/data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix), which imports it. is that a bug? | 12:20:08 | |
* looking at this, it seems like the package that's printed in the logs is generic.nix rather than 4.5.nix , which imports it. is that a bug? | 12:20:19 | |
* looking at this, it seems like the package that's printed in the logs is then nixpkgs-update can't find 4.5 in the package, and doesn't file an update PR to 5.1. is that a bug? | 12:20:58 | |
26 Nov 2024 | ||
It looks in
Sorry, I don't understand this. If the bot did file that PR, wouldn't it be incorrect? | 04:16:53 | |
27 Nov 2024 | ||
18:17:37 | ||
1 Dec 2024 | ||
00:10:18 | ||
00:10:55 | ||
08:33:26 | ||
2 Dec 2024 | ||
19:59:30 | ||
8 Dec 2024 | ||
yes i guess you're right it shouldn't file that pr, my bad who/what sets | 16:33:32 | |
one more thing: i get pinged for jitsi updates, even though i'm not a maintainer since this got merged. any idea why? | 16:34:32 | |
19:21:35 | ||
9 Dec 2024 | ||
IIRC it is set by mkDerivation. You were pinged by the bot when it opened the PR but not in the next comment when it updated the PR? | 00:17:49 | |
ah sorry, i overlooked that the pr was created a long time ago, and only merged now. all good | 09:49:49 | |
10 Dec 2024 | ||
18:11:23 | ||
hey, we would want to automate updates of what would it take to run | 18:15:39 | |
(i am just asking for now) | 18:15:57 | |
* hey, we would want to automate updates of what would it take to run | 19:09:56 | |
https://nixpkgs-update-logs.nix-community.org/vimPluginsUpdater/ The bot has already picked up | 23:53:56 | |
| 23:54:12 | |
15 Dec 2024 | ||
is there any way to examine how quickly nixpkgs-update is making its way through the queue? (e.g. "~N items are processed per day, so (say) fflogs at position 5269 will be processed in ~M days") | 21:25:52 | |
16 Dec 2024 | ||
No, not at the moment. An approximate version of the queue is public, I'll probably get around to making it more accurate in the next few weeks, should be able to add "~N items are processed per day" at the same time. I don't think "will be processed in ~M days" is feasible, some days the bot may only process a few hundred updates, other days it will process thousands. | 00:22:55 | |
* No, not at the moment. An approximate version of the queue is public, I'll probably get around to making it more accurate in the next few weeks, should be able to add "~N items are processed per day" at the same time (and show 48 hours and a week as well). I don't think "will be processed in ~M days" is feasible, some days the bot may only process a few hundred updates, other days it will process thousands. | 00:25:01 | |
19 Dec 2024 | ||
07:48:00 |