[FrameworkBundle] Using existing services as lock/semaphore resources #20738

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

javiereguiluz merged 1 commit into symfony:7.2 from HypeMC:use-service-as-lock-or-semaphore-resource

Mar 10, 2025

Merged

[FrameworkBundle] Using existing services as lock/semaphore resources #20738

[FrameworkBundle] Using existing services as lock/semaphore resources

The logs for this run have expired and are no longer available.