ENOSPC on linux

Whilst mostly a Babel user, I got interested in TypeScript a few weeks ago and started following @basarat on Twitter. Seeing his tweet about Alm last night prompted me to check out Alm. In subsequent communication, @thebabelion I mentioned to @basarat, that all did not go well and he requested I log issue here. Here is relevant terminal output (my own path names anonymized).

In both cases no UI appeared.

Terminal session in my TypeScript project directory ` xxx@xxx-VirtualBox ~/xxx/myproject $ cat /etc/*-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=18 DISTRIB_CODENAME=sarah DISTRIB_DESCRIPTION=“Linux Mint 18 Sarah” NAME=“Linux Mint” VERSION=“18 (Sarah)” ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME=“Linux Mint 18” VERSION_ID=“18” HOME_URL=“http://www.linuxmint.com/” SUPPORT_URL=“http://forums.linuxmint.com/” BUG_REPORT_URL=“http://bugs.launchpad.net/linuxmint/” UBUNTU_CODENAME=xenial cat: /etc/upstream-release: Is a directory

xxx@xxx-VirtualBox ~/xxx/myproject $ node --version v6.6.0

xxx@xxx-VirtualBox ~/xxx/myproject $ npm --version 3.10.7

xxx@xxx-VirtualBox ~/xxx/myproject $ alm Version: 2.0.3 DASHBOARD: http://localhost:4444 TSCONFIG: All Good! /home/xxx/xxx/myproject/tsconfig.json [TSC] Started Initial Error Analysis: /home/xxx/xxx/myproject/tsconfig.json [LINT] No tslint configuration found. [TSC] Error Analysis Duration: 1s [TSC] FileCount: 3 Errors: 2 [TSC] Incremental Error Analysis /home/xxx/xxx//myproject/tsconfig.json [TSC] Error Analysis Duration: 1s [TSC] FileCount: 3 Errors: 2 events.js:160 throw er; // Unhandled ‘error’ event ^

Error: watch /home/xxx/xxx/tests/baselines/reference/project/sourceRootAbsolutePathSubfolderNoOutdir/amd/ref ENOSPC at exports._errnoException (util.js:1036:11) at FSWatcher.start (fs.js:1429:19) at Object.fs.watch (fs.js:1456:11) at createFsWatchInstance (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:37:15) at setFsWatchListener (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:80:15) at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:228:14) at FSWatcher.NodeFsHandler._handleDir (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:407:19) at FSWatcher.<anonymous> (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:455:19) at FSWatcher.<anonymous> (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:460:16) at FSReqWrap.oncomplete (fs.js:123:15) fileListingWorker worker restarting. Don’t know why it stopped with code: 1 `

Terminal session in an empty directory ` xxx@xxx-VirtualBox ~ $ mkdir tmp xxx@xxx-VirtualBox ~ $ cd tmp xxx@xxx-VirtualBox ~/tmp $ alm Version: 2.0.3 DASHBOARD: http://localhost:4445 [TSCONFIG]: No active project

`

Trusting this information is helpful.

Justin Johansson Twitter: @thebabelion GitHub: @johanssj

[ishigami]

About the ENOSPC error on Linux, I’ve tried the following code and fixed the error

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

More info at: https://github.com/typicode/json-server/issues/361

[basarat]

Still like you allude to, the ENOSPC issue in the first case needs understanding as to why.

Editing the issue to track that better. This is external stuff but googling around the following shows up:

• Hows the space in /tmp: http://stackoverflow.com/a/22476114/390330
• Seems to be helping a lot of people (upvotes) : http://stackoverflow.com/a/32600959/390330 / http://stackoverflow.com/a/17437601/390330

Just as an estimate how many files are in that project folder? 🌹