1. 06 Sep, 2021 1 commit
    • Georges Racinet's avatar
      RefService.FindLocalBranches: fixing discrepancies with Gitaly · ee43254c76e1
      Georges Racinet authored
      The expected response was actually in full ref form (as `refs/heads`).
      It is probable that the Rails app is resilient with respect to that.
      Gitaly response is sorted (bad for perf, but nothing obvious we can
      do, GitLab 14.2 will even introduce different sorting criteria).
      This RPC method was implemented before we had Gitaly Comparison tests,
      this underlines once more how crucial they are.
      branch : stable
  2. 24 Aug, 2021 4 commits
  3. 23 Aug, 2021 2 commits
    • Georges Racinet's avatar
      Next version will be 0.15 · ad9dbe8dcd2d
      Georges Racinet authored
      We have a bump of protocol, even if it looks to be orthogonal
      to Mercurial concerns
      branch : stable
    • Georges Racinet's avatar
      Bumped upstream Gitaly protocol to 14.0.0 · 53a2b9627c97
      Georges Racinet authored
      Notable differences:
      - The Golang library package path now based on the major
        version number (`/v14')
      - RPC methods for remote mirror updating (should be only
        in the push direction).
      - Removal of some Wiki methods.
      branch : stable
  4. 04 Aug, 2021 6 commits
  5. 03 Aug, 2021 1 commit
  6. 19 Jul, 2021 5 commits
  7. 11 Jun, 2021 2 commits
  8. 28 May, 2021 1 commit
  9. 31 May, 2021 1 commit
  10. 26 May, 2021 5 commits
  11. 15 May, 2021 2 commits
  12. 13 May, 2021 1 commit
  13. 04 Jul, 2021 8 commits
    • Georges Racinet's avatar
      doc: HGitaly specific protocol and language libraries · 3f7820ebf7e1
      Georges Racinet authored
      also adapted the Gitaly protocol upgrade procedure to
      avoid removing the HGitaly specific `proto` files.
      I don't honestly remember why this `rm` was there. Could have been
      general concern in case an upstream proto file actually has
      to disappear (not likely, we'll deal it manually if that happens)
    • Georges Racinet's avatar
      MercurialRepositoryService: minimal impl for client testing · e36cba66fb29
      Georges Racinet authored
      The goal of this implementation is to validate that this HGitaly
      specific service can be called from the Rails app, using the
      generated HGitaly Ruby library.
      The provided `GetConfigItem` method works, but its implementation
      has to be completed with:
      - error treatment
      - `STRING` type case (the only one currently listed in the protocol)
    • Georges Racinet's avatar
      Ruby library: generated for the first time · ff03b8aef234
      Georges Racinet authored
      First committed run of `generate-grpc-lib`
    • Georges Racinet's avatar
      Ruby generated lib: Gem definition · 5ecbdbbf3749
      Georges Racinet authored
      This is enough to install the generated lib locally and use
      it from the Rails application.
    • Georges Racinet's avatar
      Ruby library: adapted generating script · 438b0a4c7693
      Georges Racinet authored
      Our files layout differs from upstream's, because of the `hgitaly`
      package name, and also because we only care about the generated lib,
      whereas Gitaly also has Ruby code of its own.
      We also derive the version module directly from `hgitaly/version`
    • Georges Racinet's avatar
      Ruby library: copy of upstream generating scripts · 40e11e7dc7ee
      Georges Racinet authored
      The `generate-proto-ruby` script and its supporting `run.rb`
      are pristine copies from Gitaly 13.12.2.
      They don't work for HGitaly at this point: this changeset is there
      to make application of upstream updates easier.
    • Georges Racinet's avatar
      Ruby generated library: initial structure · c52e3be18244
      Georges Racinet authored
    • Georges Racinet's avatar
      MercurialRepositoryService, initial definition · c2b6480dbea2
      Georges Racinet authored
      This is the first definition of Mercurial (or Heptapod)
      gRPC methods. It takes the form of a dedicated service,
      in a separate `hgitaly` protobuf package.
      ## About the separate package
      The protobufs `package` directive translates directly into a
      the module name in Ruby generated code. This doesn't happen with
      Python because Python modules and packages names are derived from
      the file system layout, wich is obviously out of control of the
      code generation.
      Upstream's Ruby generated code is packaged in a separate gem,
      historically from the `gitaly-proto` project, and soon to be
      built from the bundled proto files within Gitaly. We are not
      not going to fork either of those, and hence we need our own
      At some point, we may also need to generate a Go library,
      which require a `option go_package` statement that we couldn't
      provide right away because it means choosing the appropriate
      full path (see examples in upstream GitLab proto files).
      A consequence of u...
  14. 05 Jul, 2021 1 commit