An error occurred fetching the project authors.
  1. 23 Oct, 2016 1 commit
    • Stan Hu's avatar
      Expire and build repository cache after project import · 4ea1973f
      Stan Hu authored
      After a project import, there's a chance that the UI checks the
      branch count before the project has been imported. This change
      causes more of the keys to be flushed after an import and forces
      a rebuild of the repository cache.
      
      Closes #13518
      4ea1973f
  2. 14 Oct, 2016 1 commit
  3. 11 Oct, 2016 1 commit
  4. 10 Oct, 2016 1 commit
  5. 09 Oct, 2016 1 commit
  6. 04 Oct, 2016 1 commit
  7. 19 Sep, 2016 1 commit
  8. 14 Sep, 2016 1 commit
  9. 07 Sep, 2016 3 commits
  10. 02 Sep, 2016 1 commit
  11. 01 Sep, 2016 1 commit
  12. 19 Aug, 2016 1 commit
  13. 09 Aug, 2016 1 commit
  14. 03 Aug, 2016 1 commit
  15. 28 Jul, 2016 1 commit
  16. 27 Jul, 2016 1 commit
  17. 24 Jul, 2016 1 commit
  18. 22 Jul, 2016 1 commit
    • Stan Hu's avatar
      Gracefully handle case when keep-around references are corrupted or exist already · 39106483
      Stan Hu authored
      We were seeing a number of error messages when attempting to create a keep-around ref:
      
      1. Failed to create locked file `refs/keep-around/XYZ`: File exists
      2. Failed to write reference `refs/keep-around/XYZ`: a reference with that name already exists.
      
      I'm not sure how these happen, but I suspect when multiple workers attempt to write the same
      file we may have an issue. The force parameter should help ensure the file gets created,
      as well as the rescues to prevent 500 Errors.
      
      Rugged/libgit2 unfortunately do not allow you to delete or re-create a reference that has
      been corrupted, even with the force parameter.
      
      Closes #20109
      39106483
  19. 21 Jul, 2016 2 commits
  20. 20 Jul, 2016 1 commit
  21. 19 Jul, 2016 1 commit
  22. 18 Jul, 2016 3 commits
  23. 13 Jul, 2016 2 commits
  24. 12 Jul, 2016 1 commit
  25. 06 Jul, 2016 1 commit
  26. 04 Jul, 2016 2 commits
  27. 01 Jul, 2016 1 commit
  28. 30 Jun, 2016 1 commit
    • Paco Guzman's avatar
      Expire branch/tag git data when needed. · 5fe85bc8
      Paco Guzman authored
      When pushing commits to existing branches we don’t
      need to flush branch git data (branch names / counts)
      
      When flushes the cache when pushing commits skip to
      flush branch and tag git data (names / counts) because
      those operations are managed explicitly in each case
      
      Repopulated expired cache as soon as possible
      5fe85bc8
  29. 16 Jun, 2016 1 commit
  30. 03 Jun, 2016 2 commits
  31. 25 May, 2016 1 commit
  32. 24 May, 2016 1 commit