6fa5f510e8
In https://gitlab.com/gitlab-org/gitlab-ce/issues/66482, we see that a project's `project_feature` association may be lazily loaded and hence return `nil` if the entry is deleted if the `Project` is already loaded in memory. To ensure we don't fail hard when this happens, assume all features are disabled. We can fix this issue by eager loading the `project_feature` in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32169, but we shouldn't have to depend on that. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66482 |
||
---|---|---|
.. | ||
application_setting | ||
ci | ||
clusters | ||
concerns | ||
namespace | ||
award_emoji_policy_spec.rb | ||
base_policy_spec.rb | ||
board_policy_spec.rb | ||
commit_policy_spec.rb | ||
deploy_key_policy_spec.rb | ||
deploy_token_policy_spec.rb | ||
environment_policy_spec.rb | ||
global_policy_spec.rb | ||
group_member_policy_spec.rb | ||
group_policy_spec.rb | ||
identity_provider_policy_spec.rb | ||
issuable_policy_spec.rb | ||
issue_policy_spec.rb | ||
merge_request_policy_spec.rb | ||
namespace_policy_spec.rb | ||
note_policy_spec.rb | ||
personal_snippet_policy_spec.rb | ||
project_policy_spec.rb | ||
project_snippet_policy_spec.rb | ||
project_statistics_policy_spec.rb | ||
protected_branch_policy_spec.rb | ||
user_policy_spec.rb |