You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is a bit out of scope for what the cookbook supports, but figured I'd raise an issue to see if anyone has seen this behavior. I'm currently using a homegrown cookbook to install NPM for windows. Given that npm is available via a shellout, I should be able to use the nodejs_npm resource to install NPM packages (nothing contained within this LWRP is OS-specific).
Using test-kitchen, when using resource nodejs_npm 'gulp' I find the debug output:
[2016-12-09T07:24:40+00:00] DEBUG: Providers for generic execute resource enabled on node include: [Chef::Provider::Execute]
[2016-12-09T07:24:40+00:00] DEBUG: Provider for action run on resource execute[install NPM package gulp] is Chef::Provider::Execute
[execute] npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls gr
aceful-fs' to find it in the tree.
C:\Users\azure\AppData\Roaming\npm\gulp -> C:\Users\azure\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js
C:\Users\azure\AppData\Roaming\npm
`-- gulp@3.9.1
D [WinRM] retrying receive request after timeout
When logging in locally and running the same command npm install -g gulp I get the below output:
PS C:\Users\azure> npm install -g gulp
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update t
o graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
C:\Users\azure\AppData\Roaming\npm\gulp -> C:\Users\azure\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js
C:\Users\azure\AppData\Roaming\npm
`-- gulp@3.9.1
PS C:\Users\azure>
Outputs are the same, it just seems that WinRM doesn't release the shell back to Chef after the command is done installing. Anyone seen this issue before? It may be nodejs specific.
The text was updated successfully, but these errors were encountered:
Appears to be an issue with the way nodejs_npm is checking for packages on windows; it's obviously not supported in this cookbook. I'm going to be forking this and making some changes to accommodate windows for my specific use case (won't likely result in a PR fix as I'm going to break some logic that makes linux installation nonfunctional).
I know this is a bit out of scope for what the cookbook supports, but figured I'd raise an issue to see if anyone has seen this behavior. I'm currently using a homegrown cookbook to install NPM for windows. Given that npm is available via a shellout, I should be able to use the nodejs_npm resource to install NPM packages (nothing contained within this LWRP is OS-specific).
Using test-kitchen, when using resource
nodejs_npm 'gulp'
I find the debug output:When logging in locally and running the same command
npm install -g gulp
I get the below output:Outputs are the same, it just seems that WinRM doesn't release the shell back to Chef after the command is done installing. Anyone seen this issue before? It may be nodejs specific.
The text was updated successfully, but these errors were encountered: