Read about our upcoming Code of Conduct on this issue

  1. 02 Dec, 2016 1 commit
  2. 01 Dec, 2016 1 commit
  3. 29 Nov, 2016 1 commit
  4. 28 Nov, 2016 1 commit
  5. 23 Nov, 2016 2 commits
    • Yorick Peterse's avatar
      Remove event caching code · 0b3b7320a525
      Yorick Peterse authored
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
      0b3b7320a525
    • Douwe Maan's avatar
      af649c2dab0e
  6. 21 Nov, 2016 1 commit
  7. 17 Nov, 2016 2 commits
  8. 09 Nov, 2016 1 commit
  9. 04 Nov, 2016 1 commit
  10. 03 Nov, 2016 1 commit
  11. 28 Oct, 2016 1 commit
  12. 24 Oct, 2016 1 commit
  13. 20 Oct, 2016 3 commits
  14. 19 Oct, 2016 1 commit
  15. 18 Oct, 2016 3 commits
  16. 14 Oct, 2016 5 commits
  17. 13 Oct, 2016 1 commit
    • Sean McGivern's avatar
      Allow setting content for resolutions · 0483c1e6acbc
      Sean McGivern authored
      When reading conflicts:
      
      1. Add a `type` field. `text` works as before, and has `sections`;
         `text-editor` is a file with ambiguous conflict markers that can only
         be resolved in an editor.
      2. Add a `content_path` field pointing to a JSON representation of the
         file's content for a single file.
      3. Hitting `content_path` returns a similar datastructure to the `file`,
         but without the `content_path` and `sections` fields, and with a
         `content` field containing the full contents of the file (with
         conflict markers).
      
      When writing conflicts:
      
      1. Instead of `sections` being at the top level, they are now in a
         `files` array. This matches the read format better.
      2. The `files` array contains file hashes, each of which must contain:
         a. `new_path`
         b. `old_path`
         c. EITHER `sections` (which works as before) or `content` (with the
            full content of the resolved file).
      0483c1e6acbc
  18. 06 Oct, 2016 1 commit
  19. 03 Oct, 2016 2 commits
  20. 27 Sep, 2016 1 commit
  21. 21 Sep, 2016 2 commits
  22. 20 Sep, 2016 7 commits