1. 16 Dec, 2018 2 commits
  2. 15 Dec, 2018 1 commit
  3. 13 Dec, 2018 1 commit
  4. 12 Dec, 2018 1 commit
  5. 10 Dec, 2018 2 commits
  6. 07 Dec, 2018 6 commits
    • Zeger-Jan van de Weg's avatar
      Allow public forks to be deduplicated · 896c0bdb
      Zeger-Jan van de Weg authored
      When a project is forked, the new repository used to be a deep copy of everything
      stored on disk by leveraging `git clone`. This works well, and makes isolation
      between repository easy. However, the clone is at the start 100% the same as the
      origin repository. And in the case of the objects in the object directory, this
      is almost always going to be a lot of duplication.
      
      Object Pools are a way to create a third repository that essentially only exists
      for its 'objects' subdirectory. This third repository's object directory will be
      set as alternate location for objects. This means that in the case an object is
      missing in the local repository, git will look in another location. This other
      location is the object pool repository.
      
      When Git performs garbage collection, it's smart enough to check the
      alternate location. When objects are duplicated, it will allow git to
      throw one copy away. This copy is on the local repository, where to pool
      remains as is.
      
      These pools have an origin location, which for now will always be a
      repository that itself is not a fork. When the root of a fork network is
      forked by a user, the fork still clones the full repository. Async, the
      pool repository will be created.
      
      Either one of these processes can be done earlier than the other. To
      handle this race condition, the Join ObjectPool operation is
      idempotent. Given its idempotent, we can schedule it twice, with the
      same effect.
      
      To accommodate the holding of state two migrations have been added.
      1. Added a state column to the pool_repositories column. This column is
      managed by the state machine, allowing for hooks on transitions.
      2. pool_repositories now has a source_project_id. This column in
      convenient to have for multiple reasons: it has a unique index allowing
      the database to handle race conditions when creating a new record. Also,
      it's nice to know who the host is. As that's a short link to the fork
      networks root.
      
      Object pools are only available for public project, which use hashed
      storage and when forking from the root of the fork network. (That is,
      the project being forked from itself isn't a fork)
      
      In this commit message I use both ObjectPool and Pool repositories,
      which are alike, but different from each other. ObjectPool refers to
      whatever is on the disk stored and managed by Gitaly. PoolRepository is
      the record in the database.
      896c0bdb
    • Matija Čupić's avatar
      Extract context in JobsController spec · 5de224e3
      Matija Čupić authored
      5de224e3
    • Matija Čupić's avatar
      Extract context in JobsController spec · 7fd0f503
      Matija Čupić authored
      7fd0f503
    • Nick Thomas's avatar
      4d801a70
    • jhampton's avatar
      Fixes rubocop offenses · 13baad36
      jhampton authored
      - Fixes multiple hooks within the same group
      - Omits the default 'each'
      13baad36
    • Dylan Griffith's avatar
      f31429c1
  7. 06 Dec, 2018 10 commits
  8. 04 Dec, 2018 2 commits
  9. 03 Dec, 2018 2 commits
  10. 30 Nov, 2018 1 commit
    • Sean McGivern's avatar
      Add a flag to use a subquery for group issues search · 7fd5dbf9
      Sean McGivern authored
      We already had a flag to use a CTE, but this broke searching in some
      cases where we need to sort by a joined table. Disabling the CTE flag
      makes searches much slower.
      
      The new flag, to use a subquery, makes them slightly slower than the
      CTE, while maintaining correctness. If both it and the CTE flag are
      enabled, the subquery takes precedence.
      7fd5dbf9
  11. 29 Nov, 2018 8 commits
  12. 28 Nov, 2018 1 commit
  13. 27 Nov, 2018 1 commit
  14. 23 Nov, 2018 2 commits