An error occurred fetching the project authors.
- 24 Sep, 2018 1 commit
-
-
Valery Sizov authored
We remove this feature as it never worked properly
-
- 12 Sep, 2018 1 commit
-
-
Jan Provaznik authored
The reason for removing this gem is that it's not being maintained anymore. It uses `alias_method_chain` which is deprecated in rails 5 (and removed in 5.1), the issue is pending upstream (including a fix) - https://github.com/suranyami/peek-sidekiq/issues/3 for a while. Peek-sidekiq is used in performance bar for displaying sidekiq statistics.
-
- 10 Sep, 2018 1 commit
-
-
Rémy Coutable authored
See https://github.com/ruby-grape/grape/blob/master/CHANGELOG.md#110-842018. This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/51299. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 09 Sep, 2018 1 commit
-
-
Stan Hu authored
The most significant change in this version is that the default concurrency has been lowered from 25 to 10 (https://github.com/mperham/sidekiq/issues/3892). This doesn't affect omnibus-gitlab because the concurrency is controlled via a setting that defaults to 25 anyway and is passed in via the `-c` command-line parameter. However, source installations (including the GDK) will have to either specify the concurrency in `sidekiq.yml` or use the `-c` option. Full list of changes: https://github.com/mperham/sidekiq/blob/master/Changes.md
-
- 06 Sep, 2018 3 commits
-
-
Oswaldo Ferreira authored
We used to apply this limitation on GitLab when using Rugged. Now that we've shifted to Gitaly, this parameter needs to be sent via a RPC request. Currently this value is hardcoded on Gitaly.
-
Douglas Barbosa Alexandre authored
-
Stan Hu authored
There were several issues: 1. With Google Cloud Storage, we can't override the Content-Type with Response-Content-Type once it is set. Setting the value to `application/octet-stream` doesn't buy us anything. GCS defaults to `application/octet-stream`, and AWS uses `binary/octet-stream`. Just remove this `Content-Type` when we upload new files. 2. CarrierWave and fog-google need to support query parameters: https://github.com/fog/fog-google/pull/409/files, https://github.com/carrierwaveuploader/carrierwave/pull/2332/files. CarrierWave has been monkey-patched until an official release. 3. Workhorse also needs to remove the Content-Type header in the request (https://gitlab.com/gitlab-org/gitlab-workhorse/blob/ef80978ff89e628c8eeb66556720e30587d3deb6/internal/objectstore/object.go#L66), or we'll get a 403 error when uploading due to signed URLs not matching the headers. Upgrading to Workhorse 6.1.0 for https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/297 will make Workhorse use the headers that are used by Rails. Closes #49957
-
- 05 Sep, 2018 1 commit
-
-
Stan Hu authored
Full list of changes: https://github.com/fnando/browser/blob/master/CHANGELOG.md
-
- 03 Sep, 2018 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Kamil Trzciński authored
-
- 30 Aug, 2018 2 commits
-
-
Winnie Hellmann authored
-
Roger Rüttimann authored
-
- 21 Aug, 2018 1 commit
-
-
Stan Hu authored
This is needed to support query parameters in `Fog::Storage::Google`. See https://github.com/fog/fog-google/pull/409. Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/49957
-
- 20 Aug, 2018 1 commit
-
-
Gilbert Roulot authored
-
- 17 Aug, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 15 Aug, 2018 1 commit
-
-
Michael Kozono authored
-
- 07 Aug, 2018 1 commit
-
-
Rubén Dávila authored
-
- 29 Jul, 2018 1 commit
-
-
Stan Hu authored
Fixes failing builds with gcc on Archlinux and Ruby 2.4.4. See https://gitlab.com/gitlab-org/prometheus-client-mmap/merge_requests/26 for more details.
-
- 25 Jul, 2018 1 commit
-
-
Stan Hu authored
This will be enabled if ENABLE_RBTRACE environment variable is defined. This will allow us to debug all sorts of issues in production: https://github.com/tmm1/rbtrace
-
- 24 Jul, 2018 2 commits
-
-
Stan Hu authored
Without this parameter, every load of a Wiki page will load all the Wiki pages in the repository for the sidebar. This is a significant performance penalty that can significant slow the display of all Wiki pages. Relates to #40101
-
Stan Hu authored
sanitize 4.6.6 has this optimization that will benefit Markdown rendering: https://github.com/rgrove/sanitize/pull/183 nokogiri 1.4.4 has this memory leak fix: https://github.com/sparklemotion/nokogiri/pull/1771
-
- 20 Jul, 2018 1 commit
-
-
Gabriel Mazetto authored
This will enable bootsnap whenver the gem is available.
-
- 18 Jul, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 14 Jul, 2018 1 commit
-
-
Kukovskii Vladimir authored
-
- 11 Jul, 2018 2 commits
-
-
Rémy Coutable authored
This reverts commit 867018aa.
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 09 Jul, 2018 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 08 Jul, 2018 1 commit
-
-
Matthew Dawson authored
Also update the hook logs to escape the contents properly, as the :plain filter does not do html escaping.
-
- 06 Jul, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 05 Jul, 2018 1 commit
-
-
Tom Downes authored
for handling multi-valued SAML assertions. Add documentation of label argument for omniauth provider to override text in login button.
-
- 30 Jun, 2018 1 commit
-
-
Pirate Praveen authored
-
- 28 Jun, 2018 1 commit
-
-
Markus Koller authored
-
- 27 Jun, 2018 1 commit
-
-
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
-
- 20 Jun, 2018 1 commit
-
-
Yorick Peterse authored
In MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15834 we removed use of the data produced by the Allocations Gem. However, we never removed the code that just enables tracking of allocations. In this commit we remove all remaining traces of this Gem.
-
- 15 Jun, 2018 2 commits
-
-
Ahmad Hassan authored
-
Francisco Javier López authored
-
- 08 Jun, 2018 1 commit
-
-
Gabriel Mazetto authored
-
- 07 Jun, 2018 2 commits
-
-
Robert Speicher authored
-
Ahmad Hassan authored
-