Put an upper limit on the time KeyInFileError takes to print itself #595
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…about 20 ms) by limiting damerau_levenshtein to 1000 strings.
Closed
jpivarski
deleted the
jpivarski/upper-limit-on-time-to-print-KeyInFileError
branch
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(about 20 ms) by limiting damerau_levenshtein to 1000 strings.
I seem to remember this being an issue for you, @kratsg, because something was using
try-except KeyInFileErrorto determine whether a key exists in files with lots of keys. The damerau_levenshtein algorithm is for helping users find a mistyped key, but we don't want it hurting automated processes.