An error occurred fetching the project authors.
- 30 Apr, 2019 3 commits
-
-
John Cai authored
Gitaly's FetchIntoObjectPool RPC will idempotently fetch objects into an object pool. If the pool doesn't exist, it will create an empty pool before attempting the fetch. This change adds client code as well as specs to cover this behavior.
-
Bob Van Landuyt authored
This allows uploading designs through GraphQL. The mutation requires these arguments: - `fullPath`: The path in which we can find the issue for creating designs - `iid`: The iid of the issue in which to upload designs - `files`: An array of files. We expect these to be in the format used by apollo-upload-client[0] which uses this spec[1] for multipart fileupload. The middleware used for handling the multipart upload an translating the variables is apollo_upload_server[2] When a file is uploaded, the basename is used for creating a design, when a design for the specified issue did not exist for the filename, a new one is created. Otherwise the existing one is used. When uploading a new file, a new version is created an linked to the design being updated or created. The files are stored in a repository that lives next to the project repository with the path `@hashed/[hash]/[to]/[repo].design.git. The files are not yet stored in LFS, but they should be. 0: https://github.com/jaydenseric/apollo-upload-client 1: https://github.com/jaydenseric/graphql-multipart-request-spec 2: https://github.com/jetruby/apollo_upload_server-ruby
-
Stan Hu authored
We've seen a significant performance penalty when using `BatchLoader#__replace_with!`. This defines methods on the batch loader that proxy to the 'real' object using send. The alternative is `method_missing`, which is slower. However, we've noticed that `method_missing` can be faster if: 1. The objects being loaded have a large interface. 2. We don't call too many methods on the loaded object. Avatar uploads meet both criteria above, so let's use the newly-released feature in https://github.com/exAspArk/batch-loader/pull/45. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60903
-
- 29 Apr, 2019 4 commits
-
-
Robert Speicher authored
This reverts commit 0c4a25f3, reversing changes made to 6513028e.
-
Peter Leitzen authored
Before this commit using `/rails/letter_opener` in `development` environment failed with: undefined method `before_filter' See https://github.com/fgrehm/letter_opener_web/issues/68 This commit upgrades `letter_opener_web` to 1.3.4 so Rails 5.1 is supported.
-
Bob Van Landuyt authored
This allows uploading designs through GraphQL. The mutation requires these arguments: - `fullPath`: The path in which we can find the issue for creating designs - `iid`: The iid of the issue in which to upload designs - `files`: An array of files. We expect these to be in the format used by apollo-upload-client[0] which uses this spec[1] for multipart fileupload. The middleware used for handling the multipart upload an translating the variables is apollo_upload_server[2] When a file is uploaded, the basename is used for creating a design, when a design for the specified issue did not exist for the filename, a new one is created. Otherwise the existing one is used. When uploading a new file, a new version is created an linked to the design being updated or created. The files are stored in a repository that lives next to the project repository with the path `@hashed/[hash]/[to]/[repo].design.git. The files are not yet stored in LFS, but they should be. 0: https://github.com/jaydenseric/apollo-upload-client 1: https://github.com/jaydenseric/graphql-multipart-request-spec 2: https://github.com/jetruby/apollo_upload_server-ruby
-
Bob Van Landuyt authored
This ports the changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10462/ to CE
-
- 26 Apr, 2019 1 commit
-
-
Felipe Artur authored
Accessing http://localhostrails/letter_opener is thowring an exception, updating the gem fixes it.
-
- 25 Apr, 2019 1 commit
-
-
Francisco Javier López authored
Inside a wiki, when we show the sidebar or browse to the `pages`, all page contents are retrieved from Gitaly and that is a waste of resources, since no content from that pages are going to be showed. This MR introduces the method `ProjectWiki#list_pages`, which uses new wiki_list_pages RPC call to retrieve pages without content Also in the `WikisController` we're using the method to show pages in the sidebar and also on the `pages` page.
-
- 24 Apr, 2019 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 23 Apr, 2019 6 commits
-
-
Stan Hu authored
These upgrades are necessary to support Ruby 2.6. This matches the Gitaly MR: https://gitlab.com/gitlab-org/gitaly/merge_requests/1066
-
Stan Hu authored
These upgrades are necessary to support Ruby 2.6. This matches the Gitaly MR: https://gitlab.com/gitlab-org/gitaly/merge_requests/1066
-
Heinrich Lee Yu authored
Removes unneeded patches
-
Jasper Maes authored
Model.new.attributes now also returns encrypted attributes.
-
Heinrich Lee Yu authored
Removes unneeded patches
-
Jasper Maes authored
Model.new.attributes now also returns encrypted attributes.
-
- 22 Apr, 2019 2 commits
-
-
Stan Hu authored
Fixes minor bugs (https://github.com/mperham/sidekiq/blob/master/Changes.md#526) and keeps version used with gitlab-monitor consistent.
-
Stan Hu authored
This pulls in a fix for libxslt that addresses CVE-2019-11068: https://github.com/sparklemotion/nokogiri/releases
-
- 18 Apr, 2019 2 commits
-
-
Andrew Newdigate authored
This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
-
Andrew Newdigate authored
This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
-
- 17 Apr, 2019 1 commit
-
-
Kartikey Tanna authored
-
- 12 Apr, 2019 4 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Thong Kuah authored
-
Thong Kuah authored
Also add frozen_string_literal
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 10 Apr, 2019 2 commits
-
-
Sean McGivern authored
This reverts commit a5378665.
-
Sean McGivern authored
This reverts commit fe50baf5.
-
- 05 Apr, 2019 2 commits
-
-
Stan Hu authored
This update has two important fixes: 1. It reverts the monkey patch introduced in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23385 since https://github.com/rack/rack/pull/1201 is now part of the release. 2. Preserve forwarded IP address for trusted proxy chains (https://github.com/rack/rack/pull/1343).
-
Stan Hu authored
-
- 04 Apr, 2019 2 commits
-
-
Stan Hu authored
This fixes a number of issues as described in https://weblog.rubyonrails.org/releases/. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58963
-
-
- 02 Apr, 2019 1 commit
-
-
Patrick Bajao authored
Add `GetArchiveRequest` to git-archive params. Modifies `Git::Repository#archive_metadata` to append `path` to `ArchivePrefix` so it'll not hit the cache of repository archive when it already exists.
-
- 01 Apr, 2019 1 commit
-
-
Jarka Košanová authored
- create a class for tracking snoplow events - change FE to use the class NAMESPACE constant
-
- 27 Mar, 2019 2 commits
-
-
Gabriel Mazetto authored
The new version requires `python3` to be available. In omnibus installation this is already a reality as we are currently pathing previous `gitlab-markup` version to use `python3` instead of `python2`. We are now requiring `python3` with the gem without having to patch it. As a consequence to also make it easy to use it in development, we've introduced a `Pipfile` and `Pipfile.lock`, working similarly to `Gemfile` and `Gemfile.lock`, and added documentation on how to use them.
-
Gabriel Mazetto authored
The new version requires `python3` to be available. In omnibus installation this is already a reality as we are currently pathing previous `gitlab-markup` version to use `python3` instead of `python2`. We are now requiring `python3` with the gem without having to patch it. As a consequence to also make it easy to use it in development, we've introduced a `Pipfile` and `Pipfile.lock`, working similarly to `Gemfile` and `Gemfile.lock`, and added documentation on how to use them.
-
- 26 Mar, 2019 2 commits
-
-
Stan Hu authored
This resolves a minor link issue in libgit2 with deprecated functions: https://github.com/libgit2/libgit2/releases This coincides with the Gitaly bump: https://gitlab.com/gitlab-org/gitaly/merge_requests/1154
-
Lin Jen-Shin authored
-
- 25 Mar, 2019 1 commit
-
-
Enrique Alcantara authored
- Also remove boostrap 4 migration adapter
-
- 22 Mar, 2019 1 commit
-
-
Stan Hu authored
This keeps the version used by gitlab-monitor and GitLab CE consistent. This release also adds Ruby 2.6 support and PostgreSQL 11 error codes: https://github.com/ged/ruby-pg/blob/master/History.rdoc
-
- 20 Mar, 2019 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-