Age | Commit message (Collapse) | Author |
|
Update ffi to 1.9.25
Closes #51180
See merge request gitlab-org/gitlab-ce!21561
|
|
|
|
|
|
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
|
|
Update rubyzip gem to 1.2.2 (CVE-2018-1000544)
Closes #50930
See merge request gitlab-org/gitlab-ce!21460
|
|
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
|
|
|
|
|
|
|
|
|
|
See https://github.com/libgit2/libgit2/releases for more details.
|
|
|
|
|
|
|
|
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.
|
|
Bump haml gem to 5.0.4
See merge request gitlab-org/gitlab-ce!20847
|
|
As pointed out in #49625, this version is needed to support Ruby 2.5.
See https://github.com/haml/haml/blob/master/CHANGELOG.md 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
|
|
Bump html-pipeline to 2.8.4
See merge request gitlab-org/gitlab-ce!20828
|
|
In 2.8.3, it was possible to modify a constant without knowing it, which
led to a major performance regression (https://gitlab.com/gitlab-org/gitlab-ce/issues/49409).
Now attempting to modify the HTML::Pipeline::SanitizationFilter.WHITELIST will result in
"can't modify frozen Hash".
See https://github.com/jch/html-pipeline/pull/299.
|
|
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.
|
|
Bump Carrierwave gem to 1.2.3 (which contains the monkey patch for memory consumption)
Closes #46182
See merge request gitlab-org/gitlab-ce!20287
|
|
update html-pipeline 2.7.1 -> 2.8
Closes #48571
See merge request gitlab-org/gitlab-ce!20348
|
|
|
|
|
|
|
|
|
|
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
|