Bump the CACHE_COMMONMARK_VERSION

See merge request gitlab-org/gitlab-ce!32935

(cherry picked from commit 4200a917)

ae862960 Bump the CACHE_COMMONMARK_VERSION

Winnie Hellmann authored 5 years ago and Paul Slaughter committed 5 years ago

Fixes https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32400

For zero-downtime deployed in a mixed code environment between 12.2 and
12.3, the branch and tag name cache is incorrectly invalidated - a push
to an old machine will not clear the redis set version of the cache on
the new machine.

This commit ensures that, in 12.3, both set and non-set versions of the
cache are invalidated, but does not write or consult the set version of
the cache. . In 12.4, it will be safe to switch branch and tag names to
the redis set cache both it and the legacy cache will be invalidated
appropriately in such a mixed code environment.

This delays the full implementation of the feature by one release, but
in the absence of a credible feature-flagging strategy, and amidst an
abundance of caution about the effects of too-eager cache expiration, I
believe this is the best approach available to us.

- Avoid N+1 queries for authors and comment counts
- Avoid an additional snippet existence query

This reverts commit c6ccc07f.

In case the source and the target project are the same, the
source branch is the default branch, and the target branch
is not present, we will avoid prefilling the target branch
with the repository default branch. Letting the user decide.

Utilize `json_fields` to expose fields via
`Service#as_json(only: json_fields)`.

Add MR to changelog entry
Adjust to give margin bottom to details instead of last-child
Remove trailing whitespace

The carets will function as a button that will allow the panels
from the monitoring dashboard to collapse and show panels

Add changelog

ActiveModel::Serialization is simple in that it recursively calls
`as_json` on each object to serialize everything. However, for a model
like a Project, this can generate a query for every single association,
which can add up to tens of thousands of queries and lead to memory
bloat.

To improve this, we can do several things:

1. We use `tree:` and `preload:` to automatically generate
   a list of all preloads that could be used to serialize
   objects in bulk.

2. We observe that a single project has many issues, merge requests,
   etc. Instead of serializing everything at once, which could lead to
   database timeouts and high memory usage, we take each top-level
   association and serialize the data in batches.

For example, we serialize the first 100 issues and preload all of
their associated events, notes, etc. before moving onto the next
batch. When we're done, we serialize merge requests in the same way.
We repeat this pattern for the remaining associations specified in
import_export.yml.

Lowering the limit when performing search from 1001 to 101.
This will allow us to speed this process.

Manoj M J authored 5 years ago and Ash McKenzie committed 5 years ago

This change implements Application
Statistics API

Just replace RSA.new with PKey.read

Marcel Amirault authored 5 years ago and Paul Slaughter committed 5 years ago

Add missing shortcuts, remove shortcuts that don't exist,
and reorder as needed

Expose id field in the serializer in order
to store comments content in the localStorage
under the correct key

Wiki attachments can be workhorse accelerated.
This commit is backward compatible with older workhorse

Will Chandler authored 5 years ago and Thong Kuah committed 5 years ago

Most of the project templates bundled with GitLab have an empty string
set for `external_authorization_classification_label` in their
`project.json`. When imported this overrides the default label set on
the instance, causing the label to appear empty.

This change sets empty labels to nil during import, allowing the
default label to override it and be applied to the project.

When a pipeline fails to create in `PostReceive`, the error is silently
discarded, making it difficult to understand why a pipeline was not
created. We now add a Sidekiq warning message for this. Adding a Sentry
exception when this happens would generate a lot of noise for invalid CI
files.

Relates to https://gitlab.com/gitlab-org/gitlab-ee/issues/14720

- Show Knative install button on group/instance cluster pages
- Allow Knative to be installed on group/instance clusters
- Add feature specs for installing applications on group/instance
  clusters
- Add changelog entry
- Update docs to reflect that Knative can now be installed on
  group-level and instance-level clusters

  to doc

Since it is not possible to dynamically detect if a job is automatically
cancellable or not, a this new attribute is necessary. Moreover, it let
the maintainer of the repo to adjust the behaviour of the auto cancellation
feature to match exactly what he needs.

Patches ChronicDuration to use our custom conversions
when parsing months

Jacopo authored 5 years ago and Peter Leitzen committed 5 years ago

Those feature flags were always enabled so we can remove them safely.

Francisco Javier López authored 5 years ago and Thong Kuah committed 5 years ago

Now, when the dns rebinging setting is disabled, we will
allow urls that are not resolvable.