diff options
author | Stan Hu <stanhu@gmail.com> | 2019-08-25 07:20:17 -0700 |
---|---|---|
committer | Stan Hu <stanhu@gmail.com> | 2019-08-26 13:37:42 -0700 |
commit | 6fa5f510e83a91e19a1601bf6c01a9cffe6fd5c9 (patch) | |
tree | 8317880ef28f90f0d0688dcc7f925826eca541cd /spec/policies | |
parent | fc08d48cf0a596dc151cb7bc7ab0f7d2721f3333 (diff) | |
download | gitlab-ce-6fa5f510e83a91e19a1601bf6c01a9cffe6fd5c9.tar.gz |
Guard against deleted project feature entry
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
Diffstat (limited to 'spec/policies')
-rw-r--r-- | spec/policies/project_policy_spec.rb | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/spec/policies/project_policy_spec.rb b/spec/policies/project_policy_spec.rb index 8fd54e0bf1d..71ba73d5661 100644 --- a/spec/policies/project_policy_spec.rb +++ b/spec/policies/project_policy_spec.rb @@ -94,6 +94,19 @@ describe ProjectPolicy do permissions.each { |p| is_expected.not_to be_allowed(p) } end + context 'with no project feature' do + subject { described_class.new(owner, project) } + + before do + project.project_feature.destroy + project.reload + end + + it 'returns false' do + is_expected.to be_disallowed(:read_build) + end + end + it 'does not include the read_issue permission when the issue author is not a member of the private project' do project = create(:project, :private) issue = create(:issue, project: project, author: create(:user)) |