node --watch --watch-path #55189

Activity

1. avivkeller commented on Sep 30, 2024

   

   avivkeller

   on Sep 30, 2024

   Member

   More actions

   Are you able to reproduce outside of Docker? I can't seem to reproduce locally.
2. avivkeller

   added

   watch-modeIssues and PRs related to watch mode.Issues and PRs related to watch mode.

   on Sep 30, 2024
3. 0xMIEL commented on Sep 30, 2024

   

   0xMIEL

   on Sep 30, 2024

   Author

   More actions

   Yes, I was able to reproduce this error when I edited the http server.
   

   👀React with 👀1Reacted by Aviv Keller
4. geeksilva97 commented on Oct 7, 2024

   

   geeksilva97

   on Oct 7, 2024

   Last edited by geeksilva97

   Contributor

   More actions

   I tried to reproduce it on branch v20.17.0 but I couldn't.

   My env: Darwin LM-JNVH7RPW6J 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030 arm64.

   I executed the following script to change the server.js thousands of times but I couldn't see this Waiting for graceful termination message.

   import { writeFileSync } from 'fs';
   
   const fileContentVersion1 = `import http from 'http';
   
   const server = http.createServer((req, res) => {
     res.writeHead(200, { 'Content-Type': 'text/plain' });
     res.end('First version');
   });
   
   server.listen(1234, () => {
     console.log('Server is running at http://localhost:1234/', (new Date()).toString());
   });
   `;
   
   const fileContentVersion2 = `import http from 'http';
   
   const server = http.createServer((req, res) => {
     res.writeHead(200, { 'Content-Type': 'text/plain' });
     res.end('New version');
   });
   
   server.listen(1234, () => {
     console.log('Server is running at http://localhost:1234/', (new Date()).toString());
   });
   `;
   
   const versions = [fileContentVersion1, fileContentVersion2];
   let counter = 0;
   
   setInterval(() => {
     writeFileSync('./server.js', versions[counter++ % 2]);
     if(counter % 1000  === 0) console.log('File updated', { counter });
   }, 200);

   Command

   ./node --watch ./server.js --watch-path=./
   
5. avivkeller

   closed this as not plannedon Oct 8, 2024
6. avivkeller commented on Oct 8, 2024

   

   avivkeller

   on Oct 8, 2024

   Member

   More actions

   As this cannot be reproduce, I've closed this issue. If this changes, I'll adjust the issue.
7. muratgozel commented on Nov 29, 2024

   

   muratgozel

   on Nov 29, 2024

   More actions

   im having a similar issue in my computer (macos and no docker). i have this simple command
   infisical run --env=${INFISICAL_ENV:-dev} -- node --watch --watch-path dist --enable-source-maps dist/index.js
   and after certain amount of time it says "Waiting for graceful termination..." and doesn't reflect the updates. looks like the exec having a timeout? it shouldn't timeout because it has a server running inside. (No problem in production which the server started with node --enable-source-maps index.js)
8. OliverJAsh commented on Feb 18, 2025

   

   OliverJAsh

   on Feb 18, 2025

   More actions

   I'm running into a similar issue. Curiously, removing --watch and only specifying --watch-path fixes the issue for me. Does that work for anyone else?

   This might be related as well: #57124
9. RB-Lab commented on Aug 30, 2025

   

   RB-Lab

   on Aug 30, 2025

   More actions

   I had similar issue. I turned out, that I had a highly optimized http connection hanging and undici didn't want to close before the timeout (which was 5 min in my case) runs out. So for now I replaced httpClient.close() with process.exit(0):

       // was
       process.on('SIGTERM', async () => {
           await httpClient.close()
       })
       // now
       process.on('SIGTERM', () => {
           process.exit(0)
       })

   This probably will backfire at some point, but for now it solves the problem.