tronbox unbox metacoin
Downloading...
Unpacking...
Setting up...
Error: Command failed: bash post-unpack.sh && rm post-unpack.sh && npm install
'bash' is not recognized as an internal or external command,
operable program or batch file.
at ChildProcess.exithandler (child_process.js:289:12)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:962:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
I have tried the command tronbox unbox metacoon in windows 10.
How to solve the above mentioned error? Same error is coming on trying command tronbox init. What can be the possible reasons for this bash error?
'bash' is not recognized as an internal or external command,
operable program or batch file'
This error comes when you try to run a shell script directly in window's command prompt.
If this error comes while unboxing metacoin DApp of tron, there is nothing to worry about. Metacoin DApp will be unboxed properly in your specified directory.
In case of IDEs Truffle or Tronbox, Shell scripts are basically used for running some javascript file. So, if you using truffle or tronbox on Windows, you can run javascript file direclty without running shell script for it first.
Solution for running javascript directly from window's command Prompt:-
Open shell script in an editor and try to locate the name of the javascript file in it. Now you can run this javascipt file directly from window's command prompt.
You need to use the following command in Window's command prompt (pre-requisite:- node.js is installed in your system:-
node filename.js
I have tried this for both the IDEs, truffle and tronbox. It works just fine.
Related
So I am attempting to install some files from Send Grid via Composer usind the CommandLine.
I am following a tutorial with the link here https://www.youtube.com/watch?v=fEobqi3N7zw
The guy in the video has no problem using Composer via the Command Line in the Windows Command Prompt, but when I input the command $ go_www, my PC whines and stamps it's feet, giving me the following line:
'$' is not recognized as an internal or external command,
operable program or batch file.
In a nutshell, why?
System Information:
Windows 10 64x
I have looked at other posts on here, to no avail, I have tried opening the Command Line too as System Administrator, but to avail. I have tried restarting the system, to no avail, I can confirmed I have composer installed into the correct directory, to no avail .
$ in a shell indicates the shell is not owned by a superuser, it is not part of the command. Try running go_www. Also, the video you linked seems to be using a bash shell, whereas you appear to be running a Windows command prompt from the error message you included in your question, which might be a problem too.
In any case, go_www is an alias the video author uses to quickly navigate to the folder of interest. Try manually navigating there using cd.
Im having trouble following the tutorial for the node start on Ethermint.
After passing in the cmd: make install, i get the following error.
In my work computer, is not working, but in my personal computer is ?
What seems to be the issue ?
'sed' is not recognized as an internal or external command,
operable program or batch file.
process_begin: CreateProcess(NULL, which docker, ...) failed.
Makefile:29: pipe: Bad file descriptor
Makefile:187: *** missing separator. Stop.
I tried to install a windows version of "sed" but cant find a proper version.
I am beginner and I'm trying to connect my GitHub profile with my local machine.
I'm following the steps but my git cmd does not recognise eval.
I have generated a key and am trying to add an SSH key to the ssh-agent.
This is the message I get:
'eval' is not recognized as an internal or external command,
operable program or batch file.
The command I run is:
eval "$(ssh-agent -s)"
You are running the command in the wrong console.
Open Powershell, Git Bash console or WSL bash - depending on how you installed Git - because this is just Command Prompt (cmd.exe) which doesn't support even the syntax you're trying (Bash).
Or alternatively, ensure ssh-agent's folder is in the PATH environment variable. Then you'll be able to call it even from a different console, that is, a part of the eval $(ssh-agent -s) command.
What that part does is nevertheless incompatible with the Command Prompt console:
-s Generate Bourne shell commands on stdout. This is the default if
SHELL does not look like it's a csh style of shell.
and outputs something like this:
SSH_AUTH_SOCK=/tmp/ssh-jR0WcW41z0yX/agent.1918430; export SSH_AUTH_SOCK;
SSH_AGENT_PID=1918431; export SSH_AGENT_PID;
echo Agent pid 1918431;
which might be worked around by using Command Prompt's SET command like this:
set SSH_AUTH_SOCK=c:\some\path\agent.1918430
set SSH_AGENT_PID=<the number you got>
and then run the commands following that eval $(ssh-agent -s) instruction.
I have an issue in Cmder: when I type the touch command in the command line then it displays the following error message (Screenshot):
'touch' is not recognized as an internal or external command,
operable program or batch file.
You Must Install touch
npm install touch-cli -g
I have been trying to pip install psycopg2 for some time now
I have just updated to python 3.7.4, before this problem started.
To set my path to a specific python version I used the code below.
nano .bash_profile
I thought that it would now be easy for my system to identify the path of the newly installed python, as to enable it to install psycopg2. Then the below started happening.
The second line of system terminal or python terminal is now always showing:
-bash: zzzzz#: command not found on my terminal
No matter what I type on my terminal, I am always getting command not found
This would mean you literally have "zzzzz" somewhere in the bash_profile. Bash is seeing "zzzzz" as just another command to run at startup like the rest of the profile script. As there is nothing in your PATH matching that string, bash reports the issue back to you.
Either remove the extra line from your .bash_profile. OR use a terribly wasteful work-around!
ln -s /bin/true /bin/zzzzz
This will create a symbolic link to the "true" binary (all it ever does is return true) from zzzzz. Now bash can find zzzzz and run it during start up, which does nothing. No more error and an absurd work around. You should fix the file.