BigW Consortium Gitlab

  1. 10 May, 2017 1 commit
  2. 06 Apr, 2017 3 commits
  3. 31 Mar, 2017 1 commit
  4. 17 Mar, 2017 1 commit
  5. 15 Mar, 2017 1 commit
  6. 07 Mar, 2017 1 commit
  7. 06 Mar, 2017 1 commit
  8. 03 Mar, 2017 1 commit
  9. 01 Mar, 2017 1 commit
  10. 28 Feb, 2017 1 commit
  11. 23 Feb, 2017 1 commit
  12. 21 Feb, 2017 1 commit
  13. 15 Feb, 2017 1 commit
  14. 01 Feb, 2017 1 commit
  15. 16 Dec, 2016 2 commits
  16. 23 Nov, 2016 1 commit
    • Remove event caching code · 5371da34
      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
  17. 17 Nov, 2016 4 commits
  18. 16 Nov, 2016 3 commits
  19. 18 Aug, 2016 2 commits
    • Address review comments from @smcgivern. · dbedf3a6
      Timothy Andrew authored
      1. Remove an unnecessary (since we're fetching all the records anyway)
         `pluck` while fetching U2F registration records.
      
      2. Align "Your device was successfully set up!" section with the "U2F
         Devices" table below.
    • Allow naming U2F devices. · 16c44a5d
      Timothy Andrew authored
      1. Display a list of U2F devices on the `two_factor_auth` page.
      
      2. Allow deleting individual U2F devices.
      
      3. Allow setting a (optional) name for a device (during registration).
  20. 08 Aug, 2016 1 commit
  21. 14 Jul, 2016 1 commit
    • Load Javascript U2F library selectively. · 4b33c4c6
      Timothy Andrew authored
      1. Only on supported Chrome versions
      
      2. Mainly, this lets us simplify the javascript-based U2F check to
         `window.u2f`, where `window.u2f` can either be loaded from the GitLab
         server (for Chrome) or from the Firefox extension.
      
      3. This is a better way to provide browser detection for U2F.
  22. 17 Jun, 2016 1 commit
  23. 16 Jun, 2016 3 commits
    • Revert "squashed merge and fixed conflicts" · 452c076a
      James Lopez authored
      This reverts commit 13e37a3e.
    • squashed merge and fixed conflicts · 13e37a3e
      James Lopez authored
    • Implement @DouweM's feedback. · 7ee0898a
      Timothy Andrew authored
      - Extract a duplicated `redirect_to`
      - Fix a typo: "token", not "certificate"
      - Have the "Expires at" datepicker be attached to a text field, not inline
      - Have both private tokens and personal access tokens verified in a
        single "authenticate_from_private_token" method, both in the
        application and API. Move relevant logic to
        `User#find_by_personal_access_token`
      - Remove unnecessary constants relating to API auth. We don't need a
        separate constant for personal access tokens since the param is the
        same as for private tokens.
  24. 14 Jun, 2016 1 commit
  25. 10 Jun, 2016 2 commits
  26. 09 Jun, 2016 1 commit
    • Implement @jschatz1's comments. · 1f5ecf91
      Timothy Andrew authored
      - No hardcoded colors in any SCSS file except `variables.scss`
      - Don't allow choosing a date in the past
      - Use the same table as in the "Applications" tab
      - The button should say "Create Personal Access Token"
      - Float the revoke button to the right of the table cell
      - Change the revocation message to be more explicit.
      - Date shouldn't look selected on page load
      - Don't use a panel for the created token
          - Use a normal flash for "Your new personal access token has been created"
          - Show the input (with the token) below it full width.
          - Put the "Make sure you save it - you won't be able to access it again." message near the input
      - Have the created token's input highlight all on single click
  27. 06 Jun, 2016 1 commit
    • Implement U2F registration. · 128549f1
      Timothy Andrew authored
      - Move the `TwoFactorAuthsController`'s `new` action to `show`, since
        the page is not used to create a single "two factor auth" anymore. We
        can have a single 2FA authenticator app, along with any number of U2F
        devices, in any combination, so the page will be accessed after the
        first "two factor auth" is created.
      - Add the `u2f` javascript library, which provides an API to the
        browser's U2F implementation.
      - Add tests for the JS components
  28. 03 Jun, 2016 1 commit