| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Add reliable sidekiq fetcher
See merge request gitlab-org/gitlab-ce!21715
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Cleanup code, and refactor tests that still use Rugged. After this, there should
be no Rugged code that access the instance's repositories on non-test
environments. There is still some rugged code for other tasks like the
repository import task, but since it doesn't access any repository storage path
it can stay.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Adds list_last_commits_for_tree as the method call for the Gitaly ListLastCommitsForTree RPC
Closes #37433
See merge request gitlab-org/gitlab-ce!21921
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Implements list_last_commits_for_tree to communicate with the
ListLastCommitsForTree Gitaly RPC
Bumps the Gitaly server version
Bumps the Gitaly-Proto gem version
|
| |\ \ \
| |/ /
| | |
| | | |
# Conflicts:
# Gemfile.lock
|
| | |\ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Update grape to 1.1.0 to address a XSS vulnerability
Closes #51299
See merge request gitlab-org/gitlab-ce!21639
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | | |
| | |
| | |
| | | |
We remove this feature as it never worked properly
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | | |
Fix attachments not displaying inline with Google Cloud Storage
Closes #49957
See merge request gitlab-org/gitlab-ce!21265
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |/
| |
| |
| | |
Full list of changes: https://github.com/fnando/browser/blob/master/CHANGELOG.md
|
| | |\
| | |
| | |
| | |
| | | |
Enable JUnit results for rspec
See merge request gitlab-org/gitlab-ce!21449
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
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.
|
| | |\
| | |
| | |
| | |
| | | |
Add rbtrace to Gemfile
See merge request gitlab-org/gitlab-ce!20831
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
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
|
| | |\
| | |
| | |
| | |
| | | |
Hangouts chat integration
See merge request gitlab-org/gitlab-ce!20290
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will enable bootsnap whenver the gem is available.
|
| | |/ |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
Also update the hook logs to escape the contents properly, as the :plain
filter does not do html escaping.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
for handling multi-valued SAML assertions. Add documentation
of label argument for omniauth provider to override text
in login button.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |\
| | |
| | |
| | |
| | | |
[master] Update sanitize gem to 4.6.5 to fix HTML injection vulnerability
See merge request gitlab/gitlabhq!2399
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |/ |
|
| | |\
| | |
| | |
| | |
| | | |
Update rspec to 3.7
See merge request gitlab-org/gitlab-ce!19449
|
| | | | |
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Upgrade gitlab-markup to fix render issue with reStructuredText
See merge request gitlab-org/gitlab-ce!19596
|
