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. (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:455:19)
at FSWatcher. (/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

[basarat]

/home/xxx/xxx/tests/baselines/reference/project/sourceRootAbsolutePathSubfolderNoOutdir/amd/ref ENOSPC

So question : paulmillr/chokidar#294 (comment) ENOSPC means that there is no space on the drive. Is that the case?

[basarat]

Also give 2.0.5 a go npm install alm -g as I just updated chokidar to see if it fixes it 🌹

Just retried with 2.0.5. Alas same result; no UI appears. This time I noticed that when installing npm WARNs about chokidar. I don't know if this is relevant. Terminal transcripts follow.

<<<<< deleted long npm module listing here as proved not to relevant >>>>

Now in project directory

Observation: While my current directory in this instance is ~/workspace/myproject , it seems strange that alm is looking at a sibling directory ~/workspace/TypeScript/ in the trace below where it says 'Error: watch'. Strikes me as odd that it would do that.

`

xxx@xxx-VirtualBox ~/workspace/myproject $ alm
Version: 2.0.5
DASHBOARD: http://localhost:4444
TSCONFIG: All Good! /home/xxx/workspace/myproject/tsconfig.json
[TSC] Started Initial Error Analysis: /home/xxx/workspace/myproject/tsconfig.json
[LINT] No tslint configuration found.
[TSC] Error Analysis Duration: 1s
[TSC] FileCount: 3 Errors: 2
[TSC] Incremental Error Analysis /home/xxx/workspace/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/workspace/TypeScript/tests/baselines/reference/project/sourceRootAbsolutePathModuleSubfolderSpecifyOutputDirectory/amd/outdir 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. (/home/xxx/lib/node_modules/alm/node_modules/chokidar/lib/nodefs-handler.js:455:19)
at FSWatcher. (/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
`

Now in empty directory
`

xxx@xxx-VirtualBox ~/tmp $ alm
Version: 2.0.5
DASHBOARD: http://localhost:4444
[TSCONFIG]: No active project
`

Again no UI appears; just stares me back. :-(

[basarat]

Now in empty directory

That one is actually expected. You need to open the dashboard URL DASHBOARD: http://localhost:4444 in chrome yourself. Or if you want you can run alm -o which will open chrome for you. Its a nodejs web app in the true sense i.e nodejs backend and chrome frontend. Sorry about any confusion there but its menioned in the usage : https://github.com/alm-tools/alm#usage and the quickstart : https://basarat.gitbooks.io/alm/content/quickstart.html

However why the ENOSPC happens in the first case is still not understood. That said, I think the UI is functional in that case too (you just need to open it ... or run alm -o) 🌹

Yeah, sorry, I just realised that. My expectation was that some UI would happen just like when you launch Atom editor from the command line. Mia culpa for not reading the docs; but then again one cannot assume people will read the docs so at least a clear message in the terminal output on start up might be a good idea. (Yes, it did say DASHBOARD: http://etc, but you know.) At least I can get sort of going with it now.

[basarat]

then again one cannot assume people will read the doc

Agreed 🌹 Fixed and released with 2.0.6 ❤️

(Screenshot shows 2.0.5 as that is the version I had while adding this fix).

Good on you. While I feel like a goose, I don't really think I'm a goose. Thinking about the psychology of it though, probably had I run it the empty directory scenario first up and didn't see all the stack trace messages, I would have opened up the browser straight away. Still like you allude to, the ENOSPC issue in the first case needs understanding as to why.