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
Describe the bug
The generic cache class in module shared has a field max_size, which is - depending on the constructor used - initialized with -1. This is the case when the class is used in the scope of the rest-backend, and results in wrong behavior when cache entries are read (too many entries get deleted).
To Reproduce
Steps to reproduce the behavior: The wrong behavior (too many cache deletes) can be observed in the logs of the rest-backend.
Expected behavior
Do not impose a size limit if max_size==-1, use the provided size otherwise.
Vulas version
3.x before 3.0.10
The text was updated successfully, but these errors were encountered:
Describe the bug
The generic cache class in module
shared
has a fieldmax_size
, which is - depending on the constructor used - initialized with-1
. This is the case when the class is used in the scope of therest-backend
, and results in wrong behavior when cache entries are read (too many entries get deleted).To Reproduce
Steps to reproduce the behavior: The wrong behavior (too many cache deletes) can be observed in the logs of the
rest-backend
.Expected behavior
Do not impose a size limit if
max_size==-1
, use the provided size otherwise.Vulas version
The text was updated successfully, but these errors were encountered: