BigW Consortium Gitlab

  1. 10 May, 2016 1 commit
  2. 09 May, 2016 1 commit
  3. 06 May, 2016 1 commit
  4. 03 May, 2016 1 commit
  5. 14 Apr, 2016 1 commit
    • Use rake db:reset instead of db:setup · a54af831
      Yorick Peterse authored
      Using db:reset ensures existing tables are first dropped. This in turn
      ensures that we can drop tables regardless of any foreign key
      constraints. While CE currently doesn't have any foreign keys EE defines
      the following relation:
      
          remote_mirrors.project_id -> projects.id
      
      MySQL will complain whenever you try to drop the "projects" table first
      even when using "DROP TABLE ... CASCADE".
  6. 09 Apr, 2016 1 commit
  7. 07 Apr, 2016 1 commit
  8. 04 Apr, 2016 1 commit
  9. 30 Mar, 2016 1 commit
    • Pre-calculate Emoji digests · 5830d80b
      Yorick Peterse authored
      By pre-calculating the digests we can manually construct the emoji URLs,
      removing the need for using Rails' asset URL helpers. The reason we
      don't want to use these helpers for Emojis is two-fold:
      
      1. Rails' image_url() method is slow, really slow. For one it _might_
         have to calculate digests but it also performs a lot of other
         intensive operations (judging by the source code and based on
         measuring timings).
      
      2. We have a lot of Emoji which coupled with the above can result in it
         taking minutes to load Emoji autocomplete data.
      
      Using this pre-calculation setup generating the digests takes around 7
      seconds (including the time it takes to start Rails/Rake), and only
      around 600 milliseconds to load _all_ the autocomplete data of a project
      (measured locally).
      
      This commit _does_ change the Emoji URLs from absolute to relative URLs
      as these are much easier to generate.
      
      To update the Emoji data simply run:
      
          rake gemojione:digests
      
      Then commit any changes.
      
      Fixes gitlab-org/gitlab-ce#14009
  10. 25 Mar, 2016 1 commit
    • Improve and finish the fallback to the In-Reply-To and References header for the… · 9f218fc1
      Rémy Coutable authored
      Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature
      
      A few things to note:
      - The IncomingEmail feature is now enabled even without a
        correctly-formatted sub-address
      - Message-ID for new thread mail are kept the same so that subsequent
        notifications to this thread are grouped in the thread by the email
        service that receives the notification
        (i.e. In-Reply-To of the answer == Message-ID of the first thread message)
      - To maximize our chance to be able to retrieve the reply key, we look
        for it in the In-Reply-To header and the References header
      - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]"
      - Improve docs thanks to Axil
  11. 22 Mar, 2016 1 commit
  12. 17 Mar, 2016 1 commit
  13. 15 Mar, 2016 2 commits
  14. 10 Mar, 2016 2 commits
  15. 09 Mar, 2016 3 commits
  16. 04 Mar, 2016 1 commit
  17. 29 Feb, 2016 1 commit
  18. 25 Feb, 2016 1 commit
    • Batch size >1000 does not pay off · a3109012
      Jacob Vosmaer authored
      We did a small experiment to see how a full scan of the Redis keys on
      gitlab.com speeds up as we increase the batch size. The values on the
      right are time in seconds for a full scan (no delete operations).
      
      count: 10);      284.500529021
      count: 100);      86.21216934
      count: 1_000);    60.931676195
      count: 10_000);   60.96355610
      count: 100_000);  62.378172541
      
      It looks like 1,000 is a good number.
  19. 19 Feb, 2016 1 commit
  20. 18 Feb, 2016 1 commit
    • Use SCAN during 'rake cache:clear' · 9805fe19
      Jacob Vosmaer authored
      This allows 'rake cache:clear' to delete millions of keys without
      choking. It requires Redis 2.8.0 or newer but we needed that already
      anyway.
  21. 17 Feb, 2016 1 commit
  22. 10 Feb, 2016 2 commits
  23. 09 Feb, 2016 1 commit
  24. 05 Feb, 2016 1 commit
  25. 03 Feb, 2016 2 commits
  26. 15 Jan, 2016 1 commit
  27. 13 Jan, 2016 1 commit
  28. 05 Jan, 2016 1 commit
  29. 14 Dec, 2015 1 commit
  30. 12 Dec, 2015 1 commit
  31. 11 Dec, 2015 1 commit
  32. 09 Dec, 2015 3 commits