hgitaly issueshttps://foss.heptapod.net/heptapod/hgitaly/-/issues2024-03-21T13:42:01Zhttps://foss.heptapod.net/heptapod/hgitaly/-/issues/166Handle Group / Namespace HGRC2024-03-21T13:42:01ZGeorges RacinetHandle Group / Namespace HGRCHistorically, the Namespace (Group or User) Mercurial configuration is loaded in Heptapod by a direct inclusion from HGRC files stored in an actual directory hierarchy on the file system. Before upstream switched to hashed storage, this ...Historically, the Namespace (Group or User) Mercurial configuration is loaded in Heptapod by a direct inclusion from HGRC files stored in an actual directory hierarchy on the file system. Before upstream switched to hashed storage, this was the actual hierarchy of directories holding the repositories. After the switch to hashed storage, the sole purpose of this hierarchy had become to host these Mercurial configuration files, and was entirely deprecated upstream.
In [the 16.4 development cycle](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131576), upstream removed the capability to delete a namespace directory from the file system (both in Rails and in Gitaly). We can probably put it back if needed, but it would be better to have HGitaly handle it because all direct accesses to the repositories file system should be removed from the Rails application, as part of the %"HGitaly3: fully in charge" effort.Heptapod 1.4https://foss.heptapod.net/heptapod/hgitaly/-/issues/73BlobsService: implement ListBlobs and ListAllBlobs2024-03-21T13:36:36ZGeorges RacinetBlobsService: implement ListBlobs and ListAllBlobsThese new methods in Gitaly 14.2 are documented in `blob.proto`.
On the Rails side, **as of 14.2.0**, only `ListBlobs` is exposed in `Gitlab::Git::Repository#blobs`, and the main current use case is to be a new backing for size limits o...These new methods in Gitaly 14.2 are documented in `blob.proto`.
On the Rails side, **as of 14.2.0**, only `ListBlobs` is exposed in `Gitlab::Git::Repository#blobs`, and the main current use case is to be a new backing for size limits of push operations in `GitAccess` (was previously using `RefService.ListNewBlobs`). This access control is not relevant for Mercurial anyway, because content is received in one step from the point of view of the Rails app (in Git, commits are received first, and only then references get updated, allowing to do more checking between both).Heptapod 1.3.2