An error occurred fetching the project authors.
  1. 01 Feb, 2018 1 commit
    • Yorick Peterse's avatar
      Track and act upon the number of executed queries · cca61980
      Yorick Peterse authored
      This ensures that we have more visibility in the number of SQL queries
      that are executed in web requests. The current threshold is hardcoded to
      100 as we will rarely (maybe once or twice) change it.
      
      In production and development we use Sentry if enabled, in the test
      environment we raise an error. This feature is also only enabled in
      production/staging when running on GitLab.com as it's not very useful to
      other users.
      cca61980
  2. 10 Jan, 2018 1 commit
  3. 05 Jan, 2018 1 commit
  4. 20 Dec, 2017 2 commits
  5. 15 Dec, 2017 1 commit
  6. 25 Nov, 2017 1 commit
  7. 23 Nov, 2017 1 commit
    • Sean McGivern's avatar
      Use latest_merge_request_diff association · 991bf24e
      Sean McGivern authored
      Compared to the merge_request_diff association:
      
      1. It's simpler to query. The query uses a foreign key to the
         merge_request_diffs table, so no ordering is necessary.
      2. It's faster for preloading. The merge_request_diff association has to load
         every diff for the MRs in the set, then discard all but the most recent for
         each. This association means that Rails can just query for N diffs from N
         MRs.
      3. It's more complicated to update. This is a bidirectional foreign key, so we
         need to update two tables when adding a diff record. This also means we need
         to handle this as a special case when importing a GitLab project.
      
      There is some juggling with this association in the merge request model:
      
      * `MergeRequest#latest_merge_request_diff` is _always_ the latest diff.
      * `MergeRequest#merge_request_diff` reuses
        `MergeRequest#latest_merge_request_diff` unless:
          * Arguments are passed. These are typically to force-reload the association.
          * It doesn't exist. That means we might be trying to implicitly create a
            diff. This only seems to happen in specs.
          * The association is already loaded. This is important for the reasons
            explained in the comment, which I'll reiterate here: if we a) load a
            non-latest diff, then b) get its `merge_request`, then c) get that MR's
            `merge_request_diff`, we should get the diff we loaded in c), even though
            that's not the latest diff.
      
      Basically, `MergeRequest#merge_request_diff` is the latest diff in most cases,
      but not quite all.
      991bf24e
  8. 30 Oct, 2017 1 commit
  9. 05 Oct, 2017 1 commit
  10. 18 Sep, 2017 1 commit
  11. 14 Sep, 2017 1 commit
  12. 05 Sep, 2017 1 commit
  13. 31 Aug, 2017 1 commit
  14. 29 Aug, 2017 1 commit
  15. 28 Aug, 2017 2 commits
  16. 27 Jul, 2017 2 commits
  17. 24 Jul, 2017 1 commit
  18. 20 Jul, 2017 1 commit
  19. 11 Jul, 2017 2 commits
  20. 10 Jul, 2017 2 commits
  21. 09 Jul, 2017 1 commit
  22. 07 Jul, 2017 1 commit
  23. 18 Jun, 2017 1 commit
  24. 16 Jun, 2017 1 commit
  25. 26 Apr, 2017 1 commit
  26. 25 Apr, 2017 1 commit
  27. 24 Apr, 2017 1 commit
  28. 10 Apr, 2017 1 commit
  29. 27 Mar, 2017 1 commit
  30. 16 Mar, 2017 1 commit
  31. 07 Mar, 2017 1 commit
  32. 06 Mar, 2017 1 commit
  33. 01 Mar, 2017 1 commit
    • James Lopez's avatar
      Update occurrences of MWBS to MWPS · a0101ebf
      James Lopez authored
       Rename column in the database
       Rename fields related to import/export feature
       Rename API endpoints
       Rename documentation links
       Rename the rest of occurrences in the code
       Replace the images that contain the words "build succeeds" and docs referencing to them
       Make sure pipeline is green and nothing is missing.
      
      updated doc images
      
      renamed only_allow_merge_if_build_succeeds in projects and fixed references
      
      more updates
      
      fix some spec failures
      
      fix rubocop offences
      
      fix v3 api spec
      
      fix MR  specs
      
      fixed issues with partials
      
      fix MR spec
      
      fix alignment
      
      add missing v3 to v4 doc
      
      wip - refactor v3 endpoints
      
      fix specs
      
      fix a few typos
      
      fix project specs
      
      copy entities fully to V3
      
      fix  entity error
      
      more fixes
      
      fix failing specs
      
      fixed missing entities in V3 API
      
      remove comment
      
      updated code based on feedback
      
      typo
      
      fix spec
      a0101ebf
  34. 23 Feb, 2017 2 commits
    • Douwe Maan's avatar
      Revert "Enable Style/DotPosition" · 56de781a
      Douwe Maan authored
      This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9.
      
      # Conflicts:
      #	.rubocop.yml
      #	.rubocop_todo.yml
      #	lib/gitlab/ci/config/entry/global.rb
      #	lib/gitlab/ci/config/entry/jobs.rb
      #	spec/lib/gitlab/ci/config/entry/factory_spec.rb
      #	spec/lib/gitlab/ci/config/entry/global_spec.rb
      #	spec/lib/gitlab/ci/config/entry/job_spec.rb
      #	spec/lib/gitlab/ci/status/build/factory_spec.rb
      #	spec/lib/gitlab/incoming_email_spec.rb
      56de781a
    • Douwe Maan's avatar
      Revert "Prefer leading style for Style/DotPosition" · 1fe7501b
      Douwe Maan authored
      This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
      1fe7501b