npm install deepify -g on windows #247
Comments
|
@PaulStAmand Thank you for reporting this issue. I was wondering if you could follow below steps and let us know if it still works for you: https://github.com/MitocGroup/deep-microservices-todo-app/blob/master/src/DeepNgToDo/Docs/index.md |
|
Certainly, soon as I get off this conference call. On Wed, Feb 24, 2016 at 11:21 AM, eistrati notifications@github.com wrote:
|
|
Again, thank you for reporting this issue! We acknowledge that it's not properly documented, therefore we have updated the README.md file as follows: Note: If you want to use |
|
Hello, I had git installed but bash wasnt in my path. I upgraded and ran npm Looking over the git install process to ensure I didnt mistype something. On Wed, Feb 24, 2016 at 11:22 AM, Paul St. Amand <
|
|
ok the git installer puts program files\Git\cmd into the path but bash and I got further: C:\Users\user>npm install deepify -g
C:\Users\user\AppData\Roaming\npm npm ERR! Windows_NT 6.1.7601 npm ERR! Error: EPERM: operation not permitted, rename npm ERR! Please include the following file with any support request: C:\Users\user> On Wed, Feb 24, 2016 at 11:49 AM, Paul St. Amand <
|
|
To be honest, it worked for us on machines using default Windows. I think your version of Windows is customized for better security (to be read as more restrictions)... To the point, It looks like |
|
still the same. I see other references to similar errors. Some resolved it by temporarily disabling AntiVirus for some people on other packages npm cache clean worked as a user and also as admin running npm install deepify -g is running again as user same errors now running from git bash as admin Still getting not permitted on the rename as admin from git bash On Wed, Feb 24, 2016 at 12:26 PM, eistrati notifications@github.com wrote:
|
|
Its apparently a windows specific bug within npm that doesnt have a clear hopefully this works well on my other machine. clearing the npm cache didnt help, but I'm not alone with this error, not --force even after a complete removal of node and all the modules and On Wed, Feb 24, 2016 at 1:02 PM, Paul St. Amand <
|
|
@PaulStAmand Thanks for extensive research! We'll try to incorporate your feedback into our project as much as possible, but since we're primarily dependent on node and npm, we're limited in resources that can address them effectively. We'll keep this issue open and keep an eye on npm/npm#9696 As an alternative, could you please try to use node4-lts instead? It worked for us and hopefully it will work for you. Really curious to learn your experience, if you see the same issue or not. |
|
Under windows 10, also a faster machine, it worked with git-bash installed On Wed, Feb 24, 2016 at 6:03 PM, eistrati notifications@github.com wrote:
|
|
I've uninstalled nodejs 5.7.1 from the windows 7 machine and installed success. deepify installed without any complaints from node 4.3.1 LTS, all from 64 On Thu, Feb 25, 2016 at 1:22 AM, Paul St. Amand <
|
|
slowly making progress on windows deepify helloworld ~/deep-hello-world result in the home I'm trying to dig through why server looks for the AWS access keys and On Thu, Feb 25, 2016 at 8:40 AM, Paul St. Amand <
|
|
I started with deep-todo-app, helloworld aside from the ~/ might be working On Thu, Feb 25, 2016 at 1:18 PM, Paul St. Amand <
|
|
This is great news. Yes, ~ points to home in Unix-like environments. We'll have to make a notice for Windows-specific environments. Thank you and I'll keep this issue open, to be able to communicate when |
|
Is there a way to enable verbose debugging... deepify server On Thu, Feb 25, 2016 at 1:33 PM, eistrati notifications@github.com wrote:
|
|
Unfortunately, at this moment, |
|
To answer an earlier question regarding aws keys for Based on your feedback, we are planning to add an extra-step in |
|
on the windows 10 machine nothing displays after hitting enter. I may have to launch sysinternals to see what the process is doing. On Fri, Feb 26, 2016 at 9:14 AM, eistrati notifications@github.com wrote:
|
|
By the way, please keep updating to the latest version of |
|
I tried running from cmd instead of git-bash and rather than just sitting but I get: C:\Users\user>deepify server deep-hello-world -o On Fri, Feb 26, 2016 at 11:15 AM, eistrati notifications@github.com wrote:
|
|
Thank you! This helps a lot. We have recently discovered this bug as well, and will prioritize it. In summary, instead of using empty values, we'll put placeholders like YOUR_AWS_ACCES_KEY and YOUR_AWS_SECRET_KEY, as well as prompt interactive questions to ask for AWS keys at both For internal reference: MitocGroup/deepify#117 |
|
@PaulStAmand AWS keys issue was fixed, but we have identified another issue that might still block you from using We're working on fixing this as well, and I'll report back when we'll get the fix in place. |
|
Its unreal this path length limitation still exists within windows. I've On Tue, Mar 1, 2016 at 4:33 PM, eistrati notifications@github.com wrote:
|
|
this might be some of the windows functions not being re-entrant C:\Users\user>npm install deepify -g npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\user\AppData\Roamin npm ERR! Please include the following file with any support request: I can't disable anything on this windows 7 machine to see if its AV or active threat scanning related. I'll try it from the windows 10 machine later. I tried this from both user and admin. This might relate back to a known NPM issue around windows file locking issues. |
|
Thanks, @PaulStAmand. We have updated README.md with the following note: Note: If you want to use deepify on Windows, please follow the steps from Windows Configuration before running Can you please retry the same steps in Git Bash and let me know if above issues are replicated? |
|
Same results user@user-3 MINGW64 ~ npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\user\AppData\Roamin npm ERR! Please include the following file with any support request: user@user-3 MINGW64 ~ |
|
Ok, this is super helpful. Thanks a lot! Our team is trying to replicate and figure out a fix for it. And thank you for your patience. Windows is a pain to support, but with your help I hope we'll get it there. |
|
This appears to be an unresolved NPM issue that on windows keeps popping up. |
|
On the windows 10 machine with AVG from git-bash $ npm install deepify -g
Skipping code transpiling to ES5...
C:\Users\user\AppData\Roaming\npm\deepify -> C:\Users\user\AppData\Roaming\npm\node_modules\deepify\bin\deepify.js
Completion setup in /c/Users/user/.bashrc, skipping... |
|
Should this work on windows with 1.7.3... user@toshiba MINGW64 ~ user@toshiba MINGW64 ~ |
|
@PaulStAmand We were able to reproduce this issue again and working now to add more check points in place. Regarding the earlier issue with |
|
@PaulStAmand Here below is some more info we've learned recently: When We'll update Windows Configuration doc to reflect this requirement with explanations. Therefore, going forward, please make sure you're running Git Bash as Administrator ;) |
|
Ok, thanks, Might I also suggest looking at ionic and cordova to see how I think I tried as admin, but I'll verify that.
|
|
On the windows 10 mahcine I was I've updated npm, cache clean, and reinstalled deepify, which now completes Got a little further user@toshiba MINGW64 ~ |
|
On the windows 7 machine with git bash as admin user@user-3 MINGW64 ~ user@user-3 MINGW64 ~ user@user-3 MINGW64 ~ user@user-3 MINGW64 ~ user@user-3 MINGW64 ~ npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\user\AppData\Roamin npm ERR! Please include the following file with any support request: user@user-3 MINGW64 ~ |
|
@PaulStAmand We have recently introduced this new parameter |
|
@PaulStAmand It looks like this is a known issue and we'll keep monitoring it as well: npm/npm#7370 (some people suggest reboot, others npm cache clean; at this point we're dependent by |
|
Quick update: the |
|
ok from CMD I'm prompted for entry when launching deepify server deep-hello-world if I hit return enough times under git-bash I get to this point user@toshiba MINGW64 ~ 16:03:25 GMT-0500 (Eastern Standard Time) No init hook found for microservice hello.world.example Installing latest deep-framework from GitHub
npm ERR! tar.pack Could not write C:\Users\user\AppData\Roaming\npm-cache\local-dynamo\0.1.2\package.tgz
deep-framework@1.8.5 node_modules\deep-framework
deep-framework@1.8.5 node_modules\deep-framework |
|
DEEP Microservice: Hello World MyName |
|
user@toshiba MINGW64 ~ 16:03:25 GMT-0500 (Eastern Standard Time) No init hook found for microservice hello.world.example Installing latest deep-framework from GitHub
npm ERR! tar.pack Could not write C:\Users\user\AppData\Roaming\npm-cache\local-dynamo\0.1.2\package.tgz
deep-framework@1.8.5 node_modules\deep-framework
deep-framework@1.8.5 node_modules\deep-framework 16:13:52 GMT-0500 (Eastern Standard Time) Request / -> / |
|
Ok, we're really close, almost there :) I've acknowledged this issue and we'll get back to you asap. |
|
I tried deleting the deep-hello-world to just get a clean start and there may be a pathing issue or modules being installed into subfolders C:\Users\user\DEEP-H The path is much longer than this. |
|
@PaulStAmand Sorry for delay on our end. Using Git Bash, change directory to Next, reinstall deepify and hello-world: |
|
Removed and reinstalled deep if and the helloworld. Install from git bash If I run server from git bash I don't get any of the prompts I can continue to hit return so the input request takes and it will finally Serving file... I see them and can accept all the defaults and it Launches from cmd I notice after type your name and hitting send under Windows and aws linux null no longer appears After a humber of seconds A json output appears below the text entry field. The server windows says <2 seconds , there must be local npm init on Occasionally, null still appears but it's not every time.
|
|
Ok, much better now :) Looks like prompt is not working properly on Windows. We didn't have such issues, but I remember you've mentioned it with other occasions, so we'll check. Yes, unfortunately the performance of "Lambda" on localhost is slow. We have this issue on our radar, but it's not critical since you can see in logs the response time of 20 seconds (on my machine it's 15 seconds). When you deploy on AWS, it's MUCH faster and we'll continue improving it ;) Please feel free to let us know of any other issue you come across (and maybe in a separate ticket:) I'll close this ticket for now and will open separate ones that are strictly related to Thanks, @PaulStAmand! |
I first tried upgrading node using the binary installer, which given the error I didnt think would resolv the problem.
I have npm 3.6.0 and node .7.0 installed
I get to preinstall and it appears the installer is calling a bash script rather than rely only on node.
It get the following err:
c:\Users\user>npm install deepify -g
I get to the npm run compile
fail will occur on windows when
I see mention searching around on relying node to help with cross platform.
Am I the 1st to try instslling on windows?
The text was updated successfully, but these errors were encountered: