| Age | Commit message (Collapse) | Author |
|---|
|
Allow ReactiveCaching to support nil value
See merge request gitlab-org/gitlab-ce!30456
|
|
The configuration is currently only specified in CI, by moving it into
`.mdlrc` we get immediate feedback locally in supported editors.
To ensure `mdl` is available it's also added to the `Gemfile`, though
CI will still use the version installed in the `gitlab-docs-lint` image.
|
|
|
|
When :calculate_reactive_caching returns a nil value
this caused ReactiveCaching to schedule a worker
every time the code using :with_reactive_cache was called.
This issue caused an increasing amount of Sidekiq jobs
being created continuously.
Implementing this fix behind feature flag
:reactive_caching_check_key_exists
|
|
Use Rugged if we detect storage is NFS and we can access the disk
See merge request gitlab-org/gitlab-ce!29725
|
|
Reduce N+1 queries in MergeRequestsController#ci_environment_status
See merge request gitlab-org/gitlab-ce!30224
|
|
Remove minimum required characters for fuzzy search if no trigram is used
See merge request gitlab-org/gitlab-ce!29810
|
|
Removes EE differences for app/views/admin/users/show.html.haml
Closes gitlab-ee#12533
See merge request gitlab-org/gitlab-ce!30407
|
|
Resolve "Removing an image via Web IDE shows binary data"
Closes #60856
See merge request gitlab-org/gitlab-ce!30314
|
|
- This enables us to use a scope to query all clusters in group
hierarchy order in one query, and also enables us to union to instance
clusters later.
- Handle case where clusters not present at level. In which case the
query should go ahead and return the next level's clusters.
- Swap with new CTE query behind Feature flag. This FF is default
disabled.
|
|
This improves query performance of
MergeRequestsController#ci_environments_status a lot.
However this means old deployments that deployed to kubernetes clusters
with prometheus installations will no longer show performance metrics as
we cannot backfill cluster_id from deployment_platform with certainty
(clusters may be edited/added/deleted, which changes the results of
deployment_platform).
|
|
Prevent amplification of ReactiveCachingWorker jobs upon failures
Closes #64176
See merge request gitlab-org/gitlab-ce!30432
|
|
This release includes continued improvements to the library, fixes for a
number of lexers and support for three new languages:
https://github.com/rouge-ruby/rouge/releases
|
|
When `ReactiveCachingWorker` hits an SSL or other exception that occurs
quickly and reliably, automatically rescheduling a new worker could lead
to excessive number of jobs being scheduled. This happens because not
only does the failed job get rescheduled in a minute, but each Sidekiq
retry will also add even more rescheduled jobs.
In busy instances, this can become an issue because large numbers of
`ReactiveCachingWorker` running can cause high rates of `ExclusiveLease`
reads to occur and possibly saturate the Redis server with queries.
We now disable this automatic retry and rely on Sidekiq to perform its 3
retries with a backoff period.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64176
|
|
|
|
Some services can raise OpenSSL::X509::CertificateError due
to an invalid SSL certificates, with OpenSSL::OpenSSLError
we can handle these errors.
|
|
Add a module we use as a singleton to determine whether or not rails is
able to access the disk
|
|
|
|
Removes EE differences for app/views/layouts/fullscreen.html.haml
Closes gitlab-ee#12550
See merge request gitlab-org/gitlab-ce!30403
|
|
Adding order by to list runner jobs api.
Closes #51794
See merge request gitlab-org/gitlab-ce!29629
|
|
Important to get file data for any file that has no content set yet: we
need this information in order to build a previe for changed/staged
files if they were not yet opened in the editor
|
|
CE Port: Extend `MergeToRefService` to create merge ref from an arbitrary ref
See merge request gitlab-org/gitlab-ce!30361
|
|
|
|
Removes EE differences for app/views/profiles/preferences/show.html.haml
Closes gitlab-ee#12553
See merge request gitlab-org/gitlab-ce!30397
|
|
|
|
This is to prepare for supporing image type position tracing
|
|
Currently, MergeToRefService is specifically designed for
createing merge commits from source branch and target branch of
merge reqeusts. We extend this behavior to source branch and any
target ref paths.
|
|
|
|
|
|
|
|
Fix race in forbid_sidekiq_in_transactions.rb
Closes #64088
See merge request gitlab-org/gitlab-ce!30359
|
|
If we're not using a trigram index, then ignore the
min_chars_for_partial_matching setting
|
|
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
|
Currently, we label items to be done as "Todo." This is grammatically
incorrect and (therefore) confusing—especially to our Spanish-speaking
users for whom "todo" has a specific and unrelated meaning.
We should use "To Do" and always use it as singular (not "To Dos").
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
|
|
Current code uses module attribute which stores value
global instead of locally (thread locally). This results
in concurrent accesses to overwrite the each other values
|
|
|
|
Previously we were recording process start time as seconds from boot.
This makes it so we record as epoch time.
|
|
|
|
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|
Make Housekeeping button do a full garbage collection
Closes #63349
See merge request gitlab-org/gitlab-ce!30289
|
|
Use GitlabUploader#filename when generating upload URLs
See merge request gitlab-org/gitlab-ce!29915
|
|
In https://gitlab.com/gitlab-com/gl-infra/production/issues/928, we saw
a significant amount of network traffic and CPU usage due to Redis
checking feature flags via Flipper. Since these flags are hit with every
request, the overhead becomes significant. To alleviate Redis overhead,
we now cache the data in the following way:
* L1: A thread-local memory store for 1 minute
* L2: Redis for 1 hour
|
|
Limit amount of JUnit tests returned
Closes #64035
See merge request gitlab-org/gitlab-ce!30274
|
|
Currently, we do not cap amount of tests returned to frontend,
thus in some extreme cases we can see a MBs of data stored in Redis.
This adds an upper limit of 100 tests per-suite.
We will continue showing the total counters correctly,
but we will limit amount of tests that will be presented.
|
|
We don't need to find the filename from the remote URL
|
|
|
|
|
|
Enable terminals button for group clusters
Closes #55487
See merge request gitlab-org/gitlab-ce!30255
|
|
|
|
Enable AsciiDoc syntax highlighting (using Rouge)
Closes #32635
See merge request gitlab-org/gitlab-ce!29835
|
