An error occurred fetching the project authors.
  1. 25 Apr, 2016 1 commit
  2. 18 Apr, 2016 3 commits
  3. 15 Apr, 2016 1 commit
  4. 13 Apr, 2016 1 commit
    • Stan Hu's avatar
      Fix repository cache invalidation issue when project is recreated with an empty repo · 2ce7559d
      Stan Hu authored
      To reproduce:
      
      1. Create a project with some content
      2. Rename the project
      3. Create a new project with the same name.
      4. Boom - 404.
      
      After step 2, the branch and tag counts were not being cleared. This would
      cause `repository.has_visible_content?` to erroneously return `true`
      for the newly-created project.
      
      Closes #13384
      2ce7559d
  5. 11 Apr, 2016 3 commits
  6. 09 Apr, 2016 1 commit
  7. 07 Apr, 2016 1 commit
  8. 04 Apr, 2016 1 commit
  9. 02 Apr, 2016 1 commit
  10. 01 Apr, 2016 1 commit
  11. 27 Mar, 2016 1 commit
  12. 25 Mar, 2016 3 commits
  13. 24 Mar, 2016 2 commits
  14. 19 Mar, 2016 1 commit
    • Yorick Peterse's avatar
      Cache output of Repository#exists? · 68a4c98f
      Yorick Peterse authored
      This caches the output of Repository#exists? in Redis while making sure
      it's flushed properly when creating new repositories, deleting them,
      etc.
      
      For the ProjectWiki tests to work I had to make ProjectWiki#create_repo!
      public as testing private methods in RSpec is a bit of a pain.
      68a4c98f
  15. 17 Mar, 2016 3 commits
    • Yorick Peterse's avatar
      Don't rebuild diverging commit count caches · 3d7feeed
      Yorick Peterse authored
      When calling Repository#build_cache we _don't_ want to build the
      diverging commit count cache as doing so can be _very_ slow for
      repositories with lots of branches. Because these caches are built
      whenever needed (= when actually viewing the list of branches in the web
      UI) we can safely remove this code from
      Repository#build_cache.
      3d7feeed
    • Yorick Peterse's avatar
      Removed Repository#rebuild_cache · 81d191ed
      Yorick Peterse authored
      This method is not used or tested anywhere.
      81d191ed
    • Yorick Peterse's avatar
      Cache project avatars stored in Git · cd05d3f7
      Yorick Peterse authored
      The avatar logic has been moved from Project to Repository as this makes
      caching easier. The logic itself in turn has been changed so that the
      logo file names are cached in Redis. This cache is flushed upon pushing
      a commit but _only_ if:
      
      1. The commit was pushed to the default branch
      2. The commit actually changes any of the logo files
      
      If no branch or commit is given the cache is flushed anyway, this
      ensures that calling Repository#expire_cache without any arguments still
      flushes the avatar cache (e.g. this is used when removing a project).
      
      Fixes gitlab-org/gitlab-ce#14363
      cd05d3f7
  16. 16 Mar, 2016 1 commit
  17. 08 Mar, 2016 4 commits
  18. 07 Mar, 2016 3 commits
  19. 02 Mar, 2016 2 commits
  20. 25 Feb, 2016 1 commit
  21. 23 Feb, 2016 2 commits
  22. 20 Feb, 2016 1 commit
    • Yorick Peterse's avatar
      Flush emptiness caches whenever needed · e0cb3212
      Yorick Peterse authored
      This ensures that the emptiness cache (used for Repository#empty? and
      Repository#has_visible_content?) is flushed after comitting changes
      (using the web editor, API or Git) for new repositories. Once a
      repository is no longer empty there's no need to explicitly flush the
      cache for Repository#empty?. The cache for
      Repository#has_visible_content? in turn is already flushed whenever
      needed.
      
      Fixes gitlab-org/gitlab-ce#13387
      e0cb3212
  23. 19 Feb, 2016 2 commits