You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
When used in some circumstance the proxy object does not clean itself up in a sensible manor, for example if you create a proxy global object in Flask or Django, use it for the duration of the request and then kill it during request tear down the response queue remains indefinitely until the application is recycled.
Proposed fix: Add a destructor to the proxy class to clean up proxy objects in a suitable fashion.
The text was updated successfully, but these errors were encountered:
When used in some circumstance the proxy object does not clean itself up in a sensible manor, for example if you create a proxy global object in Flask or Django, use it for the duration of the request and then kill it during request tear down the response queue remains indefinitely until the application is recycled.
Proposed fix: Add a destructor to the proxy class to clean up proxy objects in a suitable fashion.
The text was updated successfully, but these errors were encountered: