Hi Maxim, Maxim Cournoyer <maxim.courno...@gmail.com> writes:
> Mark H Weaver <m...@netris.org> writes: > >> Tomas Volf <~@wolfsden.cz> writes: >>> Taking into account that it includes also the comments and >>> such, that Guix repository is pretty active and that there are only 30 >>> entries in the feed, I would probably need to check close to every >>> second to make sure I do not miss anything. Which seems excessive. >> >> Occasionally, large numbers of commits are pushed in a single operation, >> possibly more than 30. Even if you check the RSS feed every second, I'm >> not sure that would ensure that nothing was missed. > > Did you see my reply to Tomas earlier? Forgejo/Codeberg provides a RSS > feed exactly made for the purpose of tracking commits to a branch; you > can test it for the master branch in Guix using the following url: > > https://codeberg.org/guix/guix/rss/branch/master > > I've been using it, and it works well. I don't think you can 'loose' > notifications with RSS (that seemed to be a concern). It doesn't show > the diff in the messages but includes an URL to visit that does. I looked at your earlier reply to Tomas, and the gitea pull request that you linked to. I didn't see any comments there addressing the potential issue that Tomas raised. Apologies if I missed it. To clarify, the issue is this: By design, RSS feeds only publish the most recent entries, i.e. there is no *flow control*. There is only the heuristic that if users check the RSS feed sufficiently often, they will hopefully not miss any entries. Tomas indicated that the RSS feed for Guix commits includes only 30 entries at any given time. So what happens if 40+ commits are pushed at once? Do you have reason to believe that no commits will be missed in the RSS feed in this scenario? Thanks, Mark
