Read about our upcoming Code of Conduct on this issue

  1. 03 Oct, 2019 1 commit
  2. 01 Oct, 2019 1 commit
  3. 26 Sep, 2019 1 commit
  4. 10 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Remove Git circuit breaker · ed28255abc06
      Zeger-Jan van de Weg authored
      Was introduced in the time that GitLab still used NFS, which is not
      required anymore in most cases. By removing this, the API it calls will
      return empty responses. This interface has to be removed in the next
      major release, expected to be 12.0.
      ed28255abc06
  5. 19 Sep, 2018 1 commit
    • gfyoung's avatar
      Enable frozen string in app/controllers/**/*.rb · ee72286c9404
      gfyoung authored
      Enables frozen string for the following:
      
      * app/controllers/*.rb
      * app/controllers/admin/**/*.rb
      * app/controllers/boards/**/*.rb
      * app/controllers/ci/**/*.rb
      * app/controllers/concerns/**/*.rb
      
      Partially addresses #47424.
      ee72286c9404
  6. 28 Jul, 2018 2 commits
  7. 27 Jun, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Gitaly metrics check for read/writeability · 554a9aa7a89d
      Zeger-Jan van de Weg authored
      Prior to this change, health checks checked for writeability of the NFS
      shards. Given we're moving away from that, this patch extends the checks
      for Gitaly to check for read and writeability.
      
      Potentially some dashboards will break, as over time these metrics will
      no longer appear as Prometheus doesn't get the data anymore.
      Observability in the circuit breaker will be reduced, but its not
      expected to be turned on and the circuit breaker is being removed soon
      too.
      
      Closes https://gitlab.com/gitlab-org/gitaly/issues/1218
      554a9aa7a89d
  8. 21 Jun, 2018 1 commit
  9. 24 Jan, 2018 1 commit
  10. 08 Dec, 2017 1 commit
    • Bob Van Landuyt's avatar
      Move the circuitbreaker check out in a separate process · 0c71778c3046
      Bob Van Landuyt authored
      Moving the check out of the general requests, makes sure we don't have
      any slowdown in the regular requests.
      
      To keep the process performing this checks small, the check is still
      performed inside a unicorn. But that is called from a process running
      on the same server.
      
      Because the checks are now done outside normal request, we can have a
      simpler failure strategy:
      
      The check is now performed in the background every
      `circuitbreaker_check_interval`. Failures are logged in redis. The
      failures are reset when the check succeeds. Per check we will try
      `circuitbreaker_access_retries` times within
      `circuitbreaker_storage_timeout` seconds.
      
      When the number of failures exceeds
      `circuitbreaker_failure_count_threshold`, we will block access to the
      storage.
      
      After `failure_reset_time` of no checks, we will clear the stored
      failures. This could happen when the process that performs the checks
      is not running.
      0c71778c3046
  11. 11 Jul, 2017 1 commit
  12. 04 Jul, 2017 1 commit
  13. 02 Jun, 2017 4 commits
  14. 10 May, 2017 1 commit
  15. 07 Apr, 2017 1 commit