Skip to content

Remove restrict_within_concurrent_ruby after checking

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.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Furkan Ayhan

Merge request reports

Loading