-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add default timeout to cache memoize #46
base: master
Are you sure you want to change the base?
Conversation
Can't you just leave it instead? I.e. if you do:
it will apply whatever's in |
Oh I see. I think you can just use:
is the exact same as not specifying it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually. It makes sense.
Personally, I never use the default because if you're caching properly you probably need to have better understanding and control over the value because it depends on business logic and the application.
I can't merge this because the CI tests aren't running. Any idea why? |
Hello,
I can't find the CI tests, can you please show me the logs? |
Let's see if this restarts the CI tests. |
Can you merge in the latest upstream |
Let's try if close and re-opening triggers the CI tests. |
What the heck?! I don't know why the tests aren't running. I'll have to take a look some day when I have time. |
@KarimTayie @peterbe my update in #48 should make the tests run via 8470d5b |
@KarimTayie can you merge in |
Hey, can we get this done? I can create a similar PR and get the CI to run if needed. Would that be okay? |
Yeah, start a fresh one. |
Here it is #68 |
No description provided.