| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is to prepare for supporing image type position tracing
|
|
|
|
| |
https://gitlab.com/gitlab-org/gitlab-ee/issues/10564
|
|\
| |
| |
| |
| | |
CE port of "Require session with smartcard login for Git access"
See merge request gitlab-org/gitlab-ce!30384
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'58409-increase-graphql-complexity-for-fields-that-make-gitaly-calls' into 'master'
Increase GraphQL complexity for fields that make Gitaly Calls
Closes #58409
See merge request gitlab-org/gitlab-ce!28814
|
| |
| |
| |
| |
| |
| | |
- Remove Gitaly call check for fields that have a constant complexity
declared
- Add associated test
|
| |
| |
| |
| |
| |
| | |
- Add 1 for all fields that call Gitaly (with resolvers or without)
- Clarify comment regarding Gitaly call alert
- Expose predicate `calls_gitaly?` instead of ivar
|
| |
| |
| |
| |
| |
| | |
- Add `calls_gitaly: true` to some fields missing (hey, it works!)
- Clarify proc wrapping
- Add kwargs argument to `mount_mutation`
|
| |
| |
| |
| |
| |
| |
| | |
- Move `calls_gitaly_check` to public
- Add instrumentation for flagging missing CallsGitaly declarations
- Wrap resolver proc in before-and-after Gitaly counts to get the net
Gitaly call count for the resolver.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Stop using two separate lists for the conditions which files require a
database review.
Related discussion:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30156#note_187732053
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
The "running" state is ambiguous. Clarify that it covers both enqueued
and actually running jobs.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | | |
Previously we were recording process start time as seconds from boot.
This makes it so we record as epoch time.
|
|/ /
| |
| |
| |
| | |
Some general code has been added/removed in EE version
which needs to be backported in CE
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make Housekeeping button do a full garbage collection
Closes #63349
See merge request gitlab-org/gitlab-ce!30289
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously the Housekeeping button and API would use the counter of last
pushes to determine whether to do a full garbage collection, or whether
to do one of the less comprehensive tasks: a full repack, incremental
pack, or ref pack. This was confusing behavior, since a project owner
might have to click the button dozens of times before a full GC would be
initiated.
This commit forces a full GC each time this is initiated. Note that the
`ExclusiveLease` in `HousekeepingService` prevents users from clicking
on the button more than once a day.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63349
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Add GetCommitSignatures feature flag
See merge request gitlab-org/gitlab-ce!29288
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds feature flag for GetCommitSignatures which
got ported to go.
More info: https://gitlab.com/gitlab-org/gitaly/merge_requests/1283
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Enable AsciiDoc syntax highlighting (using Rouge)
Closes #32635
See merge request gitlab-org/gitlab-ce!29835
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove old migration specs that violate FactoriesInMigrationSpecs
See merge request gitlab-org/gitlab-ce!30280
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This removes old migrations that violate the
FactoriesinMigrationSpecs cop
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add Redis call details in Peek performance bar
See merge request gitlab-org/gitlab-ce!30191
|
| | | |_|_|/
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since Redis timings appear to be increasing in production, this change
makes it easier to see what exactly which queries are being called and
where.
This is done by prepending modules in peek-redis to store the call
details.
This commit redact values for all SET commands (e.g. HMSET, GETSET,
etc.).
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
This will make it more obvious to anyone looking to customize these
files what the source code actually is.
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Cache Flipper persisted names directly to local memory storage
See merge request gitlab-org/gitlab-ce!30265
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that application settings are no longer dominating network traffic,
we see that the Feature#persisted_names is using a significant amount of
CPU and network bandwidth for Redis. Move this cache into the
thread-local memory storage to reduce Redis overhead.
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Squash old migrations
Closes #59177
See merge request gitlab-org/gitlab-ce!30226
|
| | | | | |
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On the assumption that a background migration whose specs need a schema
older than 2018 is obsoleted by this migration squash, we can remove
both specs and code for those that fail to run in CI as a result of the
schema at that date no longer existing.
This is true for all but the MigrateStageStatus background migration,
which is also used from the MigrateBuildStage background migration.
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a memory cache local to the thread to reduce Redis load
Closes #63977
See merge request gitlab-org/gitlab-ce!30233
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Loading `ApplicationSetting` from Redis was responsible for at least 50%
of the CPU load of the Redis cluster on GitLab.com. Since these values
generally don't change very much, we can load this from the database and
cache it in memory, skipping Redis altogther. We use
`ActiveSupport::Cache::MemoryStore` as a drop-in replacement for
`RedisCacheStore` even though we probably don't need synchronized access
within `Thread.current`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63977
|
| |\ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Don't show image diff note on text file
See merge request gitlab-org/gitlab-ce!30221
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix a typo in lib/gitlab/search/found_blob.rb
See merge request gitlab-org/gitlab-ce!30219
|
| | |/ /
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
CE backport for "Show design boards at previous versions in GraphQL"
See merge request gitlab-org/gitlab-ce!30151
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
EE MR https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14292
https://gitlab.com/gitlab-org/gitlab-ee/issues/9491
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We want to call master_restart callback on start too - this callback
is used for cleaning up prometheus files. It has been added to
Omnibus already:
https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350
So make sure that Unicorn example configs are up-to-date and that
the same callback is called for Puma too.
|
| |\ \ \ \
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix attachments using the wrong URLs in e-mails
Closes #63910
See merge request gitlab-org/gitlab-ce!30197
|