From d23e91fc7b8958c23e482209da51f3bb338788b1 Mon Sep 17 00:00:00 2001 From: Glenn Rice Date: Fri, 8 Sep 2023 17:40:10 -0500 Subject: [PATCH] Remove the `usePolling` chokidar option in generate-assets.js. 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? --- htdocs/generate-assets.js | 2 -- 1 file changed, 2 deletions(-) diff --git a/htdocs/generate-assets.js b/htdocs/generate-assets.js index 0feadbf350..4d6453c420 100755 --- a/htdocs/generate-assets.js +++ b/htdocs/generate-assets.js @@ -198,8 +198,6 @@ if (argv.watchFiles) console.log('\x1b[32mEstablishing watches and performing in chokidar.watch(['js'], { ignored: /\.min\.(js|css)$/, cwd: __dirname, // Make sure all paths are given relative to the htdocs directory. - usePolling: true, // Needed to get changes to symlinks. - interval: 500, awaitWriteFinish: { stabilityThreshold: 500 }, persistent: argv.watchFiles ? true : false })