{"action":"created","issue":{"url":"https://api.github.com/repos/sass/node-sass/issues/1579","repository_url":"https://api.github.com/repos/sass/node-sass","labels_url":"https://api.github.com/repos/sass/node-sass/issues/1579/labels{/name}","comments_url":"https://api.github.com/repos/sass/node-sass/issues/1579/comments","events_url":"https://api.github.com/repos/sass/node-sass/issues/1579/events","html_url":"https://github.com/sass/node-sass/issues/1579","id":158843075,"number":1579,"title":"Error: ENOENT: no such file or directory, scandir '**/node_modules/node-sass/vendor'","user":{"login":"mrking","id":1445219,"avatar_url":"https://avatars.githubusercontent.com/u/1445219?v=3","gravatar_id":"","url":"https://api.github.com/users/mrking","html_url":"https://github.com/mrking","followers_url":"https://api.github.com/users/mrking/followers","following_url":"https://api.github.com/users/mrking/following{/other_user}","gists_url":"https://api.github.com/users/mrking/gists{/gist_id}","starred_url":"https://api.github.com/users/mrking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrking/subscriptions","organizations_url":"https://api.github.com/users/mrking/orgs","repos_url":"https://api.github.com/users/mrking/repos","events_url":"https://api.github.com/users/mrking/events{/privacy}","received_events_url":"https://api.github.com/users/mrking/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-06-07T05:40:49Z","updated_at":"2016-10-04T17:00:57Z","closed_at":"2016-06-07T08:33:10Z","body":"Followed the troubleshooting guide. I'm having an intermittent build issue with one of our projects. The appearance is that it happens randomly. \r\n\r\n_**See comment for solution**_\r\n\r\nI'm using `gulp-sass@2.1.0` which has this as a dependency. \r\n\r\nI suspect there might be some sort of concurrency issue with the download of binaries in that specific folder. I've tried switching to several different node and npm versions now to see if the problem is related but hasn't resolved the issue. \r\n```\r\nNode v4.4.5\r\nNPM 3.5.3\r\n{ http_parser: '2.5.2',\r\n  node: '4.4.5',\r\n  v8: '4.5.103.35',\r\n  uv: '1.8.0',\r\n  zlib: '1.2.8',\r\n  ares: '1.10.1-DEV',\r\n  icu: '56.1',\r\n  modules: '46',\r\n  openssl: '1.0.2h' }\r\nlinux\r\nx64\r\n```\r\n\r\nUbuntu 16.04\r\n\r\n**On builds that do run successfully, I'll get the following message before NPM quits**\r\n```\r\n\r\nBinary downloaded and installed at /home/jenkins/development/node_modules/node-sass/vendor/linux-x64-46/binding.node\r\n\"/home/jenkins/development/node_modules/node-sass/vendor/linux-x64-46/binding.node\" exists. \r\n testing binary.\r\nBinary is fine; exiting.\r\n\r\n```\r\n**Otherwise this error will happen during the build**\r\n\r\n```\r\n[01:09:46] 'sass' errored after 16 ms\r\n[01:09:46] Error: ENOENT: no such file or directory, scandir '/home/jenkins/development/node_modules/node-sass/vendor'\r\n    at Error (native)\r\n    at Object.fs.readdirSync (fs.js:808:18)\r\n    at Object.getInstalledBinaries (/home/jenkins/development/node_modules/node-sass/lib/extensions.js:74:13)\r\n    at foundBinariesList (/home/jenkins/development/node_modules/node-sass/lib/errors.js:20:15)\r\n    at foundBinaries (/home/jenkins/development/node_modules/node-sass/lib/errors.js:15:5)\r\n    at Object.module.exports.missingBinary (/home/jenkins/development/node_modules/node-sass/lib/errors.js:45:5)\r\n    at Object.<anonymous> (/home/jenkins/development/node_modules/node-sass/lib/index.js:14:28)\r\n    at Module._compile (module.js:409:26)\r\n    at Object.Module._extensions..js (module.js:416:10)\r\n    at Module.load (module.js:343:32)\r\n\r\nnpm ERR! Linux 3.13.0-85-generic\r\nnpm ERR! argv \"/usr/local/bin/node\" \"/usr/local/bin/npm\" \"run-script\" \"build\"\r\nnpm ERR! node v4.4.5\r\nnpm ERR! npm  v3.5.3\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! lexi@1.0.0 build: `gulp testfail lintfail babel sass hb`\r\nnpm ERR! Exit status 1\r\nnpm ERR! \r\nnpm ERR! Failed at the lexi@1.0.0 build script 'gulp testfail lintfail babel sass hb'.\r\nnpm ERR! Make sure you have the latest version of node.js and npm installed.\r\nnpm ERR! If you do, this is most likely a problem with the lexi package,\r\nnpm ERR! not with npm itself.\r\nnpm ERR! Tell the author that this fails on your system:\r\nnpm ERR!     gulp testfail lintfail babel sass hb\r\nnpm ERR! You can get information on how to open an issue for this project with:\r\nnpm ERR!     npm bugs lexi\r\nnpm ERR! Or if that isn't available, you can get their info via:\r\nnpm ERR!     npm owner ls lexi\r\nnpm ERR! There is likely additional logging output above.\r\n\r\nnpm ERR! Please include the following file with any support request:\r\nnpm ERR!     /home/jenkins/development/npm-debug.log\r\n```\r\n\r\n\r\n\r\n\r\nGulp Sass installation doesn't seem to be catching the Vendor binaries every time even manually installing. \r\n```\r\n\r\nsudo npm install gulp-sass\r\nnpm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!\r\n- lru-cache@4.0.1 node_modules/cross-spawn-async/node_modules/lru-cache\r\nlexi@1.0.0 /home/jenkins/development\r\n├─┬ gulp@3.9.1\r\n│ └─┬ vinyl-fs@0.3.14\r\n│   └─┬ glob-watcher@0.0.6\r\n│     └─┬ gaze@0.5.2\r\n│       └─┬ globule@0.1.0\r\n│         └─┬ minimatch@0.2.14\r\n│           └── lru-cache@2.7.3 \r\n├─┬ gulp-sass@2.3.1\r\n│ └─┬ node-sass@3.7.0\r\n│   ├─┬ cross-spawn-async@2.2.4\r\n│   │ └── lru-cache@4.0.1 \r\n│   ├─┬ gaze@1.0.0\r\n│   │ └─┬ globule@0.2.0\r\n│   │   └─┬ minimatch@0.2.14\r\n│   │     └── lru-cache@2.7.3 \r\n│   └─┬ node-gyp@3.3.1\r\n│     └─┬ minimatch@1.0.0\r\n│       └── lru-cache@2.7.3 \r\n├─┬ jshint@2.9.2\r\n│ └─┬ cli@0.6.6\r\n│   └─┬ glob@3.2.11\r\n│     └─┬ minimatch@0.3.0\r\n│       └── lru-cache@2.7.3 \r\n└─┬ mocha@2.5.3\r\n  └─┬ glob@3.2.11\r\n    └─┬ minimatch@0.3.0\r\n      └── lru-cache@2.7.3 \r\n\r\nnpm WARN optional Skipping failed optional dependency /chokidar/fsevents:\r\nnpm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12\r\nnpm WARN enoent ENOENT: no such file or directory, open '/home/jenkins/development/node_modules/languages.css/package.json'\r\nmike@lexi3:/home/jenkins/development$ ls node_modules/node-sass/\r\nbin  binding.gyp  lib  node_modules  package.json  README.md  scripts  src\r\n```\r\n\r\nBut installing node-sass manually seems to force the binaries to get downloaded\r\n```\r\nmike@lexi3:/home/jenkins/development$ sudo npm install node-sass@3.4.2\r\nnpm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm\r\nnpm WARN deprecated cross-spawn-async@2.2.4: cross-spawn no longer requires a build toolchain, use it instead!\r\n\r\n> node-sass@3.4.2 install /home/jenkins/development/node_modules/node-sass\r\n> node scripts/install.js\r\n\r\nBinary downloaded and installed at /home/jenkins/development/node_modules/node-sass/vendor/linux-x64-46/binding.node\r\n\r\n> spawn-sync@1.0.15 postinstall /home/jenkins/development/node_modules/spawn-sync\r\n> node postinstall\r\n\r\n\r\n> node-sass@3.4.2 postinstall /home/jenkins/development/node_modules/node-sass\r\n> node scripts/build.js\r\n\r\n` /home/jenkins/development/node_modules/node-sass/vendor/linux-x64-46/binding.node ` exists. \r\n testing binary.\r\nBinary is fine; exiting.\r\n- lru-cache@4.0.1 node_modules/cross-spawn-async/node_modules/lru-cache\r\n- minimatch@3.0.0 node_modules/node-sass/node_modules/glob/node_modules/minimatch\r\n- glob@7.0.3 node_modules/node-sass/node_modules/glob\r\n- minimatch@0.3.0 node_modules/node-sass/node_modules/globule/node_modules/glob/node_modules/minimatch\r\n- glob@3.2.11 node_modules/node-sass/node_modules/globule/node_modules/glob\r\n- lodash@2.4.2 node_modules/node-sass/node_modules/lodash\r\n- minimatch@0.2.14 node_modules/node-sass/node_modules/minimatch\r\n- globule@0.2.0 node_modules/node-sass/node_modules/globule\r\n- gaze@1.0.0 node_modules/node-sass/node_modules/gaze\r\n- in-publish@2.0.0 node_modules/in-publish\r\nlexi@1.0.0 /home/jenkins/development\r\n├─┬ babel-cli@6.9.0\r\n│ └─┬ request@2.72.0\r\n│   └─┬ bl@1.1.2\r\n│     └── readable-stream@2.0.6 \r\n├─┬ gulp-autoprefixer@3.1.0\r\n│ └─┬ through2@2.0.1\r\n│   └── readable-stream@2.0.6 \r\n├─┬ jshint@2.9.2\r\n│ └─┬ cli@0.6.6\r\n│   └─┬ glob@3.2.11\r\n│     └─┬ minimatch@0.3.0\r\n│       └── lru-cache@2.7.3 \r\n├─┬ mocha@2.5.3\r\n│ └─┬ glob@3.2.11\r\n│   └─┬ minimatch@0.3.0\r\n│     ├── lru-cache@2.7.3 \r\n│     └── sigmund@1.0.1 \r\n└─┬ node-sass@3.4.2 \r\n  ├─┬ cross-spawn@2.2.3 \r\n  │ ├─┬ cross-spawn-async@2.2.4\r\n  │ │ └── lru-cache@4.0.1 \r\n  │ └─┬ spawn-sync@1.0.15 \r\n  │   ├─┬ concat-stream@1.5.1 \r\n  │   │ ├── readable-stream@2.0.6 \r\n  │   │ └── typedarray@0.0.6 \r\n  │   └── os-shim@0.1.3 \r\n  ├─┬ gaze@0.5.2\r\n  │ └─┬ globule@0.1.0\r\n  │   └─┬ minimatch@0.2.14\r\n  │     ├── lru-cache@2.7.3 \r\n  │     └── sigmund@1.0.1 \r\n  ├─┬ node-gyp@3.3.1\r\n  │ └─┬ minimatch@1.0.0\r\n  │   └── lru-cache@2.7.3 \r\n  └─┬ npmconf@2.1.2 \r\n    ├─┬ config-chain@1.1.10 \r\n    │ └── proto-list@1.2.4 \r\n    └── uid-number@0.0.5 \r\n\r\nnpm WARN optional Skipping failed optional dependency /chokidar/fsevents:\r\nnpm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12\r\nnpm WARN enoent ENOENT: no such file or directory, open '/home/jenkins/development/node_modules/languages.css/package.json'\r\n```"},"comment":{"url":"https://api.github.com/repos/sass/node-sass/issues/comments/251448403","html_url":"https://github.com/sass/node-sass/issues/1579#issuecomment-251448403","issue_url":"https://api.github.com/repos/sass/node-sass/issues/1579","id":251448403,"user":{"login":"saper","id":248374,"avatar_url":"https://avatars.githubusercontent.com/u/248374?v=3","gravatar_id":"","url":"https://api.github.com/users/saper","html_url":"https://github.com/saper","followers_url":"https://api.github.com/users/saper/followers","following_url":"https://api.github.com/users/saper/following{/other_user}","gists_url":"https://api.github.com/users/saper/gists{/gist_id}","starred_url":"https://api.github.com/users/saper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saper/subscriptions","organizations_url":"https://api.github.com/users/saper/orgs","repos_url":"https://api.github.com/users/saper/repos","events_url":"https://api.github.com/users/saper/events{/privacy}","received_events_url":"https://api.github.com/users/saper/received_events","type":"User","site_admin":false},"created_at":"2016-10-04T17:00:57Z","updated_at":"2016-10-04T17:00:57Z","body":"@PixnBits thank you, this is good to know. How did you manually publish node-sass? How can one reproduce this?"}}
{"actor":{"display_login":"saper"}}