| Age | Commit message (Collapse) | Author |
|---|
|
# Conflicts:
# db/schema.rb
|
|
Rephrase Merge Request Maintainer Edit
See merge request gitlab-org/gitlab-ce!19061
|
|
Optimise runner update cached info
See merge request gitlab-org/gitlab-ce!19187
|
|
Fix an N+1 in avatar URLs
Closes #43114
See merge request gitlab-org/gitlab-ce!18488
|
|
39549-label-list-page-redesign-with-draggable-labels
|
|
|
|
This is tricky: the query was being run in
`ObjectStorage::Extension::RecordsUploads#retrieve_from_store!`, but we can't
just add batch loading there, because the `#upload=` method there would use the
result immediately, making the batch only have one item.
Instead, we can pre-emptively add an item to the batch whenever an avatarable
object is initialized, and then reuse that batch item in
`#retrieve_from_store!`. However, this also has problems:
1. There is a lot of logic in `Avatarable#retrieve_upload_from_batch`.
2. Some of that logic constructs a 'fake' model for the batch key. This should
be fine, because of ActiveRecord's override of `#==`, but it relies on that
staying the same.
|
|
Add background migrations to archive legacy job traces
Closes #46642
See merge request gitlab-org/gitlab-ce!19194
|
|
'46452-nomethoderror-undefined-method-previous_changes-for-nil-nilclass' into 'master'
Resolve "NoMethodError: undefined method `previous_changes' for nil:NilClass"
Closes #46452
See merge request gitlab-org/gitlab-ce!19190
|
|
Perform pull request IO work outside a transaction
See merge request gitlab-org/gitlab-ce!19372
|
|
Support rails5 in postgres indexes function and fix some migrations
Closes #46236
See merge request gitlab-org/gitlab-ce!19400
|
|
39549-label-list-page-redesign-with-draggable-labels
|
|
Optimise pages service calling
See merge request gitlab-org/gitlab-ce!19388
|
|
Eliminate N+1 queries for CI job artifacts in /api/projects/:id/pipelines/:pipeline_id/jobs
See merge request gitlab-org/gitlab-ce!19353
|
|
|
|
Support presigned multipart uploads
See merge request gitlab-org/gitlab-ce!18855
|
|
|
|
|
|
Remove N+1 query for author in issues API
See merge request gitlab-org/gitlab-ce!19345
|
|
|
|
Adjust insufficient diff hunks being persisted on NoteDiffFile
See merge request gitlab-org/gitlab-ce!19399
|
|
Include all ancestors milestones in json list & autocomplete
Closes #36862
See merge request gitlab-org/gitlab-ce!19317
|
|
|
|
This currently causes 500's errors when loading the MR page
(Discussion) in a few scenarios.
We were not considering detailed diff headers such as
"--- a/doc/update/mysql_to_postgresql.md\n+++ b/doc/update/mysql_to_postgresql.md"
to crop the diff. In order to address it, we're now using
Gitlab::Diff::Parser, clean the diffs and builds Gitlab::Diff::Line objects
we can iterate and filter on.
|
|
Additionally the current application setting is also updated to disable
the usage of DSA keys.
|
|
/api/projects/:id/pipelines/:pipeline_id/jobs
|
|
This was being masked by the statement cache because only one author was used
per issue in the test..
Also adds support for an Rspec matcher `exceed_all_query_limit`.
|
|
This was being masked by the statement cache because only one author was used
per issue in the test..
Also adds support for an Rspec matcher `exceed_all_query_limit`.
|
|
We show a blue flash banner if the user already accepted, and show a
button allowing them to continue to the application.
|
|
|
|
When importing a GitHub pull request we would perform all work in a
single database transaction. This is less than ideal, because we perform
various slow Git operations when creating a merge request. This in turn
can lead to many DB connections being used, while just waiting for an IO
operation to complete.
To work around this, we now move most of the heavy lifting out of the
database transaction. Some extra error handling is added to ensure we
can resume importing a partially imported pull request, instead of just
throwing an error.
This commit also changes the specs for IssueImporter so they don't rely
on deprecated RSpec methods.
|
|
|
|
Update email_spec to 2.2.0
Closes #46845
See merge request gitlab-org/gitlab-ce!19164
|
|
Rails5 fix arel from
Closes #46281
See merge request gitlab-org/gitlab-ce!19340
|
|
|
|
|
|
Fix N+1 with source_projects in merge requests API
See merge request gitlab-org/gitlab-ce!19346
|
|
Bump gitlab-shell to 7.1.3
See merge request gitlab-org/gitlab-ce!19358
|
|
Fix attr_encryption key settings
Closes #47166
See merge request gitlab-org/gitlab-ce!19341
|
|
This includes the change that prints the @username of a user instead
of the full name.
https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/204
|
|
|
|
|
|
|
|
|
|
|
|
Now that we are checking `MergeRequest#for_fork?`, we also need
the source project preloaded for a merge request.
|
|
|
|
|
|
attr_encrypted does different things with `key` depending on what mode you are using:
1. In `:per_attribute_iv_and_salt` mode, it generates a hash with the salt:
https://github.com/attr-encrypted/encryptor/blob/c3a62c4a9e74686dd95e0548f9dc2a361fdc95d1/lib/encryptor.rb#L77.
There is no need to truncate the key to 32 bytes here.
2. In `:per_attribute_iv` mode, it sets the key directly to the password, so
truncation to 32 bytes is necessary.
Closes #47166
|
|
|
