Skip to content
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

addInternal() call expirationCheck() is not a good idea #54

Open
KR-Yuan opened this issue Jan 18, 2021 · 1 comment
Open

addInternal() call expirationCheck() is not a good idea #54

KR-Yuan opened this issue Jan 18, 2021 · 1 comment

Comments

@KR-Yuan
Copy link

KR-Yuan commented Jan 18, 2021

when create a cachetable to init expirationCheck() function , maybe better than call it in addInternal function

@JasonDevops
Copy link

yes,I know that you question was right,Last night I was trying to run the projects,When I tested expirationCheck() function, But I found that it has bugs,When accessedOn is almost greater now time(time := time.Now()),So that expirationCheck() function can't callback these cache which was expired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants