23 Jul 2025 |
Sandro 🐧 | nope, you need to wait | 11:55:09 |
Sandro 🐧 | depends, some days, sometimes longer | 11:55:18 |
JacoMalan1 | Damn | 11:55:25 |
Sandro 🐧 | if you want the PR immediately, just open it yourself 😅 | 11:55:39 |
JacoMalan1 | If I wait, though, and the bot opens it, then I can merge it myself. Otherwise I have to clog up the already clogged up PR review queue 😂 | 11:56:40 |
Sandro 🐧 | If it is a straight forward update and no build failures and you tick the PR template, it can probably be merged immeadetely | 12:08:12 |
Sandro 🐧 | * If it is a straight forward update and no build failures and you tick the PR template, it can probably be merged immediately | 12:08:23 |
kuflierl | Honestly same issue here. I always tend to wait a bit for the update queue to trickle down | 12:09:42 |
kuflierl | I also have to ask... Why do we have a queue and why is it so long? | 12:10:35 |
Sandro 🐧 | the bot just iterates through everything IIRC | 12:24:04 |
Sandro 🐧 | there is no real "queue" | 12:24:10 |
kuflierl | I would beg to differ
https://nixpkgs-update-logs.nix-community.org/~supervisor/queue.html | 12:26:19 |
JacoMalan1 | Yeah... It also seems like it does the queue from back to front | 12:27:22 |
JacoMalan1 | So 1st in line is actually last | 12:27:30 |
24 Jul 2025 |
zowoq | Updates are moved to the bottom of the queue when the bot starts processing them. There are multiple workers running package updates in parallel so the queue can advance quite a bit while an update is still in progress. Because of the time it takes to build a package and run nixpkgs-review it can take several hours for the bot to actually open a PR for an update. | 03:08:19 |
| @sorimaxuki:matrix.org set a profile picture. | 07:16:51 |
| @sorimaxuki:matrix.org removed their profile picture. | 07:19:23 |
| codgician changed their profile picture. | 16:58:08 |
28 Jul 2025 |
| @sorimaxuki:matrix.org left the room. | 20:50:42 |