Skip to content
Snippets Groups Projects
  1. Feb 13, 2018
  2. Feb 12, 2018
  3. Feb 09, 2018
  4. Feb 07, 2018
    • Zeger-Jan van de Weg's avatar
      Don't use rugged in Repository#refs_hash · 73e78c4e
      Zeger-Jan van de Weg authored
      The refs hash is used to determine what branches and tags have a commit
      as head in the network graph. The previous implementation depended on
      Rugged#references. The problem with this implementation was that it
      depended on rugged, but also that it iterated over all references and
      thus loading more data than needed if for example the project uses CI/CD
      environments, Pipelines, or Merge Requests.
      
      Given only refs are checked the network cares about the GraphHelper#refs
      method has no need to reject those, simplifying the method.
      
      Closes gitlab-org/gitaly#880
      Unverified
      73e78c4e
  5. Feb 06, 2018
  6. Feb 05, 2018
  7. Feb 02, 2018
  8. Feb 01, 2018
  9. Jan 31, 2018
  10. Jan 30, 2018
  11. Jan 29, 2018
  12. Jan 28, 2018
  13. Jan 27, 2018
  14. Jan 25, 2018
  15. Jan 23, 2018
    • Jan Provaznik's avatar
      Use limit for search count queries · 090ca9c3
      Jan Provaznik authored
      Search query is especially slow if a user searches a generic string
      which matches many records, in such case search can take tens of
      seconds or time out. To speed up the search query, we search only for
      first 1000 records, if there is >1000 matching records we just display
      "1000+" instead of precise total count supposing that with such amount
      the exact count is not so important for the user.
      
      Because for issues even limited search was not fast enough, 2-phase
      approach is used for issues: first we use simpler/faster query to get
      all public issues, if this exceeds the limit, we just return the limit.
      If the amount of matching results is lower than limit, we re-run more
      complex search query (which includes also confidential issues).
      Re-running the complex query should be fast enough in such case because the
      amount of matching issues is lower than limit.
      
      Because exact total_count is now limited, this patch also switches to
      to "prev/next" pagination.
      
      Related #40540
      090ca9c3
  16. Jan 22, 2018
  17. Jan 19, 2018
  18. Jan 18, 2018
    • Felipe Artur's avatar
      a956fac2
    • Jan Provaznik's avatar
      Return last edited time instead of update time · 4b6b8ecc
      Jan Provaznik authored
      For issuable models we keep two timestamps:
      updated_at which is updated whenever any model attribute is changed,
      last_edited_at which is changed when only title or description is
      changed.
      
      In UI bellow description we display who and when updated the item. But
      last_edited_by (used for 'who') is mistakenly combined with updated_at
      (when), last_edited_at should be used instead.
      
      Closes #41247
      4b6b8ecc
Loading