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.

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

Race condition due to DecoratingProxy in dev env #117

NiR- opened this Issue Oct 20, 2017 · 0 comments


None yet
1 participant
Copy link

NiR- commented Oct 20, 2017

Currently, in the cache-bundle, the DecoratingFactory creates a proxy class each time it is called if the CacheItemPoolInterface is built by a provider. This is a problem in the case multiple concurrent requests are sent, for example when used on an api called by a js frontend.

I forked and patched it (see here), but this part is pretty hacky because we don't have a proper way to know what CacheItemPoolInterface are created by each factory. I would be happy to finalise this patch, but I would need some help about what to do :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment