-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix: always use slice() for applying offset and limit in loki storage instance, fixing the fuzzing test run #5757
Conversation
…ance, fixing the fuzzing test run
…ance, fixing the fuzzing test run
0daa350
to
8e8a0e5
Compare
Hi. The changes look good. Can you add one test to the query-correctness tests which contains the broken fuzzed query+documents combination? |
Sure! I'm currently trying to track down another loki related bug, then I'll add the test for this one. |
…nto fix/lokijs-fuzzing
…ance, fixing the fuzzing test run
252521f
to
cca6c1f
Compare
Test has been added and verified that it fails before the fix and passes after. |
I guess the failing example-graphq jobl must have been a hiccup during |
Yes I will just retry the CI until it works. |
Merged. Thank you for that great contribution. |
…
This PR contains:
A BUGFIX
Describe the problem you have without this PR
The fuzzy testing failed for the LokiJS storage, because sometimes there were less documents returned than expected. After quite some investigation, I found
limit()
andoffset()
to be the culprits, so instead of using those, slice() is now always used for limit and offset values, just as it already was whenmustRunMatcher
wastrue
.Todos