| 22 Jul 2025 |
 hexa | yup, I already subbed to all my packages, thx | 20:01:11 |
 asymmetric | hexa: due to the amount of packages you maintain, the bot is hitting this issue 😉 | 20:01:14 |
| hexa | 🙂 | 20:01:19 |
| hexa | that one issue that will never be fixed | 20:01:34 |
| hexa | loving it | 20:01:35 |
| hexa | might want to escape package names with backticks, if possible | 20:01:56 |
| hexa | 
Download image.png | 20:02:34 |
| hexa | also, does it update the list over time? | 20:02:55 |
| asymmetric | no, not atm. a new follow will sub to any newly maintained packages, but won't remove any. need to work on proper sync/reconciliation at some point 😅 | 20:27:05 |
| asymmetric | ok now it handles cases with lots of subs/unsubs more gracefully:
- prints something if
M_TOO_LARGE happens
- notifies user if a follow is taking > 10s
| 21:00:54 |
 Sandro 🐧 | same yesterday. Now it seems to work somewhat. | 21:27:01 |
| 23 Jul 2025 |
 kuflierl | Alright, it also works for me now | 09:08:39 |
 JacoMalan1 | Is there a way to manually have r-ryantm create a PR for a package update, or do you need to wait for the package to bubble up to the top of the queue? Also, how long does it usually take for a package update ? | 11:52:43 |
| 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 |
