Remove restrict_within_concurrent_ruby after checking
requested to merge 427701-remove-restrict_within_concurrent_ruby-inraise_if_concurrent_ruby into master
What does this MR do and why?
We are removing restrict_within_concurrent_ruby to prevent infinite loop
when ConcurrentRubyThreadIsUsedError is rescued and sent to Sentry.
Gitlab::ErrorTracking may have Gitaly or DB calls,
which will raise this error again.
For example: Feature.enabled? may check DB for feature flag.
- More info: #432145 (comment 1671305713)
- Related to: #427701 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Furkan Ayhan