Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
code-server exit automatically.
See original GitHub issue[IPC Library: File Watcher (chokidar)] Unhandled Promise Rejection: Canceled: Canceled
at Object.canceled (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:111:23)
at Delayer.cancel (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:2320:38)
at ThrottledDelayer.cancel (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:2356:26)
at Object.stop (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:12182:46)
at ChokidarWatcherService.stop (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:12286:25)
at FSWatcher.<anonymous> (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/out/vs/platform/files/node/watcher/unix/watcherApp.js:12272:34)
at FSWatcher.emit (events.js:210:5)
at FSWatcher._handleError (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/index.js:625:10)
at NodeFsHandler._boundHandleError (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:302:43)
at createFsWatchInstance (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:120:5)
at setFsWatchListener (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:165:15)
at NodeFsHandler._watchWithNodeFs (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:330:14)
at NodeFsHandler._handleFile (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:360:23)
at NodeFsHandler._addToNodeFs (/code-server/build/code-serverdaily-vsc1.41.1-linux-x86_64-built/node_modules/chokidar/lib/nodefs-handler.js:620:21)
What happened? I was editing a file and it just exited. Please help me. Thank you.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
code-server exit automatically. · Issue #1412 - GitHub
This worked for code-server running directly on my VM, but I am still seeing the crash when running the docker container.
Read more >How to Exit a Process in Node.js: process.exit() Method
The code will automatically exit the process once it reaches the end and there is nothing to process further. For example, we create...
Read more >Developing inside a Container - Visual Studio Code
After the build completes, VS Code will automatically connect to the container. You can now interact with your project in VS Code just...
Read more >Why Does My Docker Container Stop? - Tutorial Works
An exit code or exit status of 0 generally means that the application successfully completed. But any other exit code indicates an unsuccessful...
Read more >Termux - code-server v4.8.0 docs - Coder
Set up NVM for multi-user. After installing NVM it automatically adds the necessary commands for it to work, but it will only work...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
try to increase system file watcher
it’s work for me
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.