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
bug: do not cache mutations to object cache results #234
bug: do not cache mutations to object cache results #234
Conversation
- Add (failing) test for ensuring mutations are not cached
Co-authored-by: Jason Bahl <jasonbahl@mac.com>
Co-authored-by: Jason Bahl <jasonbahl@mac.com>
…ug-mutation-should-not-cache
…bug-mutation-should-not-cache
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.
@markkelnar per your question in Slack, if the test here seems valid and beneficial, let's pull it in. If it's a flaky test or otherwise unhelpful, we can close that PR and move on.
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.
@markkelnar I merged the PR that fixes the tests and then merged main back into this PR and tests are still failing.
I investigated a bit and thought I had found a bug where the filter was returning nothing instead of the default filtered value.
However this didn't fix the issue.
The BatchQueryTest is still failing.
@markkelnar I pushed up some more changes and got tests passing. |
When smart cache object cache is enabled to store results of queries, do not get/store mutation requests.
Fixes #196