Name |
Last commit
|
Last update |
---|---|---|
.. | ||
admin | ||
dashboard | ||
explore | ||
group | ||
profile | ||
project | ||
snippets | ||
steps | ||
support | ||
abuse_report.feature | ||
groups.feature | ||
invites.feature | ||
search.feature | ||
snippet_search.feature | ||
user.feature |
BigW Consortium Gitlab
Revert "Optimistic locking for Issue and Merge Requests" The migration to add `lock_version` in !5146 to every issue and merge request takes too long on GitLab.com since it has to add a default value of 0 to every row. Unfortunately, Rails 4.2 doesn't work properly if the value is left as `nil`; anything using optimistic locking cannot be edited. This bug was fixed in Rails 5.0 via this commit: https://github.com/rails/rails/commit/13772bfa49325a8dc26410d2dcb555665a320f92. I suggest we revert this change for now, and when we upgrade to Rails 5.0 we can reintroduce this feature. See merge request !5245
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
admin | Loading commit data... | |
dashboard | Loading commit data... | |
explore | Loading commit data... | |
group | Loading commit data... | |
profile | Loading commit data... | |
project | Loading commit data... | |
snippets | Loading commit data... | |
steps | Loading commit data... | |
support | Loading commit data... | |
abuse_report.feature | Loading commit data... | |
groups.feature | Loading commit data... | |
invites.feature | Loading commit data... | |
search.feature | Loading commit data... | |
snippet_search.feature | Loading commit data... | |
user.feature | Loading commit data... |