Remove the usePolling chokidar option in generate-assets.js.
#924
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
With node version 20 the `usePolling` option is resulting in high cpu usage. Interestingly enough, the PG generate-assets.js script is the one that actually has high cpu usage with this option, not the webwork2 generate-assets.js script. Something to do with links not actually existing?
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.
With node version 20 the
usePollingoption is resulting in high cpu usage.Interestingly enough, the PG generate-assets.js script is the one that actually has high cpu usage with this option, not the webwork2 generate-assets.js script. Something to do with links not actually existing?
This replaces #923 which was accidentally created with the
developbranch name.