-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unreliable isReliable check due to usage of next() #11
Comments
Oh..., you are right. I made a quick fix for ELD v2 and released v2.1.2 Also, since this was already solved for ELD v3 at dev-main, I made a pre-release v3.0.0-BETA |
Thank you for fixing this in 2.1.2. When I look at the master branch, it seems it has the same problem, as it also uses the next() solution. Did you fix this in another branch? |
To be extra sure, maybe I could also add a reset(), and don't assume at |
What I would do is make the The
|
Hello, we noticed something weird with your library. When calling
isReliable()
more than once (it depends on how many scores there are), it will sometimes return a different boolean than before making it... unreliable :). This happens due to the usage ofnext($this->score)
. It advances the internal pointer of the array. I am not sure on how it should work, there are no test cases for the 24% minimum, otherwise I would have created a merge request. Can you fix this?The text was updated successfully, but these errors were encountered: