-
Notifications
You must be signed in to change notification settings - Fork 74
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
Sporadic :badarg error #52
Comments
Let me try to reproduce the error to see what could be happening. |
I've been trying to reproduce the error but nothing, perhaps you should give me more details about how are you testing it, did you run the app with the cache and then executing some commands via console? The error itself is because the |
Thanks for looking into this. Unfortunately I cannot share a link to the codebase in which I'm experiencing this issue, as it is a private application that relies on several other private applications and libraries to do its work. However, through some further experimentation, I have found a simple way to reproduce the issue consistently. All I need do is, in the console, call the Can you try to reproduce by setting up a multi-level cache as described above, then calling Thanks! |
Yes, absolutely, that's enough info, I'll try, thanks :) !! |
I found the issue, just pushed the fix to master. Please try it out and let me know if it works. Stay tuned! |
Awesome! Thank you very much. |
I tested the fix on master and all is good! Thanks again. |
Awesome! I will close the issue then! Thanks! |
We are getting the same behaviour in the latest version 1.1.1 with the same way of reproducing call the flush() function on the cache, either on the level 1 cache (Cache.L1.flush()) or on the multi-level cache (Cache.flush()). consistently outputs the error Note: it does clear the cache but still outputs the error
|
I'll take a look at it, thanks! |
@hugomatinho trying to reproduce the error using near_cache example which uses the multi-level adapter but it works (calling |
Still have error even though config looks fine according to example
Amphora.Cache module Cache definition
Application.ex
Cache population
terminal output with the filled cache terminal output on error
|
@cabol any idea regarding the above ? |
Hey @hugomatinho , sorry, I haven't had time to look into it. I will try to check it out as soon as I can, hopefully during this week but for sure this weekend. Thanks and I'll get back to you soon! |
Hey, @hugomatinho good news, I found the bug, thank you so much for reporting it, I will push a fix today, I'll let you know when it is ready! |
@hugomatinho I just pushed the fix on the master branch, in the meantime, you'll need to point there – I'm aiming to release On the other hand, checking out your config, I don't understand why or how you are using this:
For the 2-level cache you want, you just need:
Let me know if now it works for you, stay tuned! Thanks 👍 |
Hey, any update on this? did it work for you? |
@cabol just tested it, it worked! awesome! thank you so much :) i'll have a look at the fix so i can learn as well |
I'm experimenting with Nebulex multi-level caching with the following structure:
and the following configuration:
This configuration seems to work fine for the most part, but I get occasional error messages in my console that look like this:
Any idea what the issue might be?
The text was updated successfully, but these errors were encountered: