Re: git ports-tree doesn't work, please check!
- Reply: Peter : "Re: git ports-tree doesn't work, please check!"
- Reply: Tatsuki Makino : "Re: git ports-tree doesn't work, please check!"
- Reply: Jamie Landeg-Jones : "Re: git ports-tree doesn't work, please check!"
- In reply to: Peter : "git ports-tree doesn't work, please check!"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 02 May 2024 19:08:02 UTC
On Thu, May 02, 2024 at 08:39:24PM +0200, Peter wrote: > > $ fetch https://cgit.freebsd.org/ports/log/devel/py-python-dateutil > fetch: transfer timed out > > My local replica has the same problem, git goes into a loop at that > location. Hmm, testing locally there's only a single commit to that path (moving it from Move devel/py-dateutil) so git has to read the whole commit history to discover there is only one commit. Even on a 40-core machine with nvme disks that's very slow process (but it does eventually complete). I suspect cgit is timing out because it's looking for enough logs to fill a single page before sending a reply. This is an advantage of github's progressive rendering (and the pile of javascript it requires). For example, see: https://github.com/freebsd/freebsd-ports/commits/main/devel/py-python-dateutil where you get the first commit and then a spinning thing for a bit before "End of commit history for this file" appears. -- Brooks