Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-07-20Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42GitLab Bot
2021-04-21Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43GitLab Bot
2020-11-19Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42GitLab Bot
2020-09-19Add latest changes from gitlab-org/gitlab@13-4-stable-eeGitLab Bot
2020-06-18Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot
2020-03-05Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2020-01-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-16Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-20Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-04-22Always use internal ID tables in development and productionStan Hu
To avoid quiet failures that cause consistency errors in the database, we should now assume that the internal_ids table is available since we've had this table for close to a year. For tests that have migrations, we make this check thread-safe via SafeRequestStore. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60718
2019-04-16Rewind IID on Ci::PipelinesKamil Trzciński
If no pipeline is created we currently have IID gap. This is due to fact that we generate IID not on save, but rather ahead of time. This results, us, losing IIDs.
2019-03-28Inherit from ApplicationRecord instead of ActiveRecord::BaseNick Thomas
2019-01-29Flush InternalId records after importAndreas Brandl
After the import has finished, we flush (delete) the InternalId records related to the project at hand. This means we're starting over with tracking correct internal id values, a new record will be created automatically when the next internal id is generated. The GitHub importer assigns iid values by using supplied values from GitHub. We skip tracking internal id values during the import in favor of higher concurrency. Deleting any InternalId records after the import has finished is an extra measure to guarantee consistency. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54270.
2019-01-29Revert "Trigger iid logic from GitHub importer for milestones."Andreas Brandl
This reverts commit 358675d09f6ba0fdcc4a089c6d1da6df9ff6d092.
2018-08-16Trigger iid logic from GitHub importer for milestones.Andreas Brandl
2018-08-02Merge branch 'frozen-string-enable-app-models' into 'master'Rémy Coutable
Enable frozen string in app/models/*.rb See merge request gitlab-org/gitlab-ce!20851
2018-08-01Resolve "Allow issue's Internal ID (`iid`) to be set when creating via the API"Jamie Schembri
2018-07-27Enable frozen string in app/models/*.rbgfyoung
Partially addresses #47424.
2018-05-30Merge branch 'master' into per-project-pipeline-iidShinya Maeda
2018-05-28Remove double-checked internal id generation.Andreas Brandl
This was needed for a transition phase only. For details see #45389. Closes #45389.
2018-05-03Add per-project pipeline idShinya Maeda
2018-04-20Atomic internal ids for all modelsAndreas Brandl
2018-04-16Double-check next value for internal ids.Andreas Brandl
This is useful for a transition period to migrate away from `NoninternalAtomicId`. In a situation where both the old and new code to generate a iid value is run at the same time (for example, during a deploy different nodes may serve both versions), this will lead to problems regarding the correct `last_value`. That is, what we track in `InternalId` may get out of sync with the maximum iid present for issues. With this change, we double-check that and correct the `last_value` with the maximum iid found in issues if necessary. This is subject to be removed with the 10.8 release and tracked over here: https://gitlab.com/gitlab-org/gitlab-ce/issues/45389 Closes #45269.
2018-03-16Address review comments.Andreas Brandl
2018-03-16Address review comments.Andreas Brandl
2018-03-16Backwards-compat for migration specs.Andreas Brandl
The specs are based on a schema version that doesn't know about `internal_ids` table. However, the actual code being execute relies on it.
2018-03-16Refactor, extract class and improve comments.Andreas Brandl
2018-03-16More flexible way of internal id generation.Andreas Brandl
2018-03-16Atomic generation of internal ids for issues.Andreas Brandl