d9c4ebc5a0
And reuse `Gitlab::Utils::StrongMemoize`. There is a subtle behavior change required to reuse StrongMemoize in this case. The early fallback check now occurs *before* reading the memoized value instead of after. I think this is fine since a memoized value should only exist if `exists?` is also already memoized as `true`. |
||
|---|---|---|
| .. | ||
| api | ||
| backup | ||
| banzai | ||
| bitbucket | ||
| bitbucket_server | ||
| constraints | ||
| container_registry | ||
| gitaly | ||
| gitlab | ||
| google_api | ||
| json_web_token | ||
| mattermost | ||
| microsoft_teams | ||
| object_storage | ||
| omni_auth/strategies | ||
| rspec_flaky | ||
| system_check | ||
| after_commit_queue_spec.rb | ||
| event_filter_spec.rb | ||
| expand_variables_spec.rb | ||
| extracts_path_spec.rb | ||
| feature_spec.rb | ||
| file_size_validator_spec.rb | ||
| forever_spec.rb | ||
| gitlab_spec.rb | ||
| milestone_array_spec.rb | ||
| system_check_spec.rb | ||
| uploaded_file_spec.rb | ||