experiment: hack in notify-debouncer-full to test Windows build #2499
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
|
Passed all CI and served its purpose, so will close. |
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.
Introduction
This MR is not meant to be merged. The implementation is a hack to test whether upgrading
notify*will fix the Windows build CI issue encountered in #2498 . If this fixes the CI issue, I will overhaul the implementation and open a different MR to land thenotifyversion bump.(Currently the implementation works locally on Linux but is too sensitive, often not refreshing the site correctly because we react to multiple events too quickly. Implementation overhaul should explore batching.)