I'm trying to create a new environment from file, when i run conda env export > environment.yml the file is created but when running vim environment.yml i get this error
vim : The term 'vim' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
when trying to run conda env create --prefix .\env -f ..\environment.yml on my new project directory i get An unexpected error has occurred.
Related
I have read the documentation and followed the steps to run mongodump on windows machine, but still getting this error.
I tried to set the path using this command set path="C:\Program Files\MongoDB\Server\4.4\bin" and added the path in environmental variables but still getting the error. What should I do ?
I need to create Greengrass group and core in aws iot(windows).
I have referred with the document https://docs.aws.amazon.com/cli/latest/reference/greengrass/create-group.html
I have tried with powershell script aws greengrass create-group \ --name ggawsgreen
Gets error when executing above powershell script . error => aws : The term 'aws' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again
How to create Greengrass group and core(aws iot) in windows powershell
the error appears because you haven't installed the AWS Command Line Interface or aws cli for short.
Or ´aws cli´ is not in your path.
download here
I'm using PowerShell to set up a test instance that is running on Windows. When the instance is up and running it will then run a few commands to get Hadoop set up and will then run a Spark job.
This all works fine when done manually from within the instance itself. I'm now trying to translate those commands into powershell.
These two for example are failing with the message that it is not a recognised cmdlet or function etc:
& $env:HADOOP_HOME + "\bin\winutils.exe" chmod 777 /tmp/hive
& $env:HADOOP_HOME + "\bin" hadoop namenode -format -force
The error I receive is:
& : The term 'c:\hadoop\bin' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:3
I've then tried various combinations of wrapping in quotes, using iex, assigning it to a variable, but all fail.
PowerShell interprets the expanded value of $env:HADOOP_HOME as the command to execute, which fails, because a folder isn't a cmdlet, function, script file, or operable program. Do the concatenation in a subexpression:
& ($env:HADOOP_HOME + "\winutils.exe") chmod 777 /tmp/hive
or put the environment variable directly in the command string:
& "$env:HADOOP_HOME\winutils.exe" chmod 777 /tmp/hive
I ran the command to install Ember.js:
npm install -g ember-cli
Then when I run:
Ember -v
I get error: "The term ember is not recognized as the name of a cmdlet, function, script file or operable program ..."
I added the system environment variable $NODE_PATH = %AppData%\npm\node_modules
I see ember-cli folder in the $NODE_PATH
This is a newly imaged machine so this may be an issue with my npm setup/configuration. How can I install ember globally?
I added %AppData%\npm (use the full path which in my case is C:\Users\bmackey\AppData\Roaming\npm) to the system Path environment variable. I had to remove C:\Program Files\Microsoft DNX\Dnvm\ from my Path in order to stay under the 260 character limit; hopefully I won't need this. I do not know a way around the 260 character limit.
Now ember -v works.
You need to add the path to the ember.cmd file into the powershell environment variable, note that this is different to the standard PATH environment variable.
For those that don't know, the reason you can run ember (a node module) simply by running the command ember is because when you install ember it create a ember.cmd file in your AppData folder:
this file typically looks like this and just bootstraps node and runs the ember js file:
#IF EXIST "%~dp0\node.exe" (
"%~dp0\node.exe" "%~dp0\node_modules\ember-cli\bin\ember" %*
) ELSE (
#SETLOCAL
#SET PATHEXT=%PATHEXT:;.JS;=;%
node "%~dp0\node_modules\ember-cli\bin\ember" %*
)
so when you run ember from your command window or powershell it just looks for a cmd file in its PATH variable. If this doesn't have an entry pointing at the location of this cmd file it won't be able to run it.
To fix this in powershell just run the following:
[Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:\Users\<user>\AppData\npm", [EnvironmentVariableTarget]::Machine)
Most of this is taken from the answer here.
Make sure C:\Users\<user>\AppData\npm is where NPM has deployed your ember.cmd file. I have seen this also deploy in C:\Users\<user>\AppData\Roaming\npm so it can vary.
When I run "php composer.phar update" command, I got
"'git' is not recognized as an internal or external command,
operable program or batch file."
I have installed Git client and added PATH environment variable.
If you run "git" command in terminal, it works?
Maybe your PATH variable it's wrong.