fix(): otp number no accurate #7
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
boranseckin/2fa-utils!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/otp-number-no-accurate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
fix for loop incorrect condition
Codecov Report
100.00% <100.00%> (ø)Continue to review full report at Codecov.
Thank you for contributing to this project @geraldlee2001. To observe the problem, I have written a better test that checks the function with random variables 10000 times (
f2b0364805). And I was able to confirm that your solution works. To fix the problem, however, I will instead use the built-inpadStartfunction (f6379e80f1). I think it will be more obvious and straightforward.As a side note, it would be more beneficial if you had explained the problem and your suggested fixes better when opening a pull request. Also, the conflicting commits did not help when trying to understand the changes.
i found that the otp digit some times with come out inaccurate requested amount. For example, I put 6 digits to the function but sometime will appear 5 digits only with a very rare chance after checking is the issue from library. After I changed to this code and the issue doesn't appear again
Pull request closed