fix: issue in which problems remain after file is closed (again)#83
Merged
Conversation
Contributor
|
Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi, @hildjj. Thank you for continuous updates.
This is I think a trivial PR and so I'm posting here directly, without making an issue.
I found the problem that had been fixed at Issue #58 and PR #59 occurs again (but now it occurs sometimes, not always).
The problem tends to occur frequently when the debounce time is large, e.g., 1000 msec. This will be relate to the recent extension update that has made the debounce time configurable and has changed its default value from 150 to 200 msec. The fix is quite simple. Please check it.