I tried to install the Google Assistant onto my new Raspberry Pi. I watched and followed the instruction online (Google developer). I have done exactly what the instruction says. However, at the end, I typed 'google-assistant-demo' to run it. The console answered: 'command not found'
I tried to find the solution online, but I could not find any suitable solution for this situation.
Can anyone help me?
The online instructions create a virtual python environment to keep the dependencies required by the assistant in a separate location.
Try activating the virtual environment before running this command. Here's how to -
pi#raspberrypi:~ $ source env/bin/activate
(env) pi#raspberrypi:~ $ google-assistant-demo
Related
I'm trying to setup GoLand to use WSL 2 as in this guide: https://www.jetbrains.com/help/go/how-to-use-wsl-development-environment-in-product.html
I've installed Go in the Ubuntu distro following the linux instructions on the GoLang website, and go version prints outs the version I downloaded, so it appears that Go is working inside WSL.
So now I tried to create a new project in GoLand, and I'm getting errors, which appear to come from the fact that the SDK isn't loaded in GoLand. The guide doesn't offer much guidance on this, so I just tried to add a local SDK.
When I select /usr/local/go I get an error that it's not a valid SDK.
So I created the ~/go directory, and then updated my .zshrc file to export the GOPATH and GOROOT environment variables, even though they already showed up when I ran go env, doing this got them to show up on a simple env call.
But I'm still getting the invalid SDK error like above.
Is there a configuration step I'm missing that isn't spelled out in the guide? I came across this old post about creating symlinks to fake the expected directory structure. I haven't done this because it's a really old post, has comments that say this has been fixed, and seems like a really odd solution.
Support for Go SDK in WSL2 will be available in the next 2021.3 release, please see GO-10618.
October 2021 update.
2021.3 reaches Early Access Program at the moment. GoLand suggests selecting Go SDK on WSL2 mount if the location of the project is on WSL2 as well.
I experienced this on my Debian machine and I wasn't using WSL2. I found that the actual cause of the issue is that Goland is unable to read the directory /usr/local/go/bin due to inadequate permission.
A possible solution is to run the goland.sh script as root. The script can be found in the bin/goland.sh directory of the Goland IDE folder. Here is a simple command to do run Goland as the root
export HISTIGNORE='*sudo -S*' && echo "sudo-password-here" | sudo -S /absolute-path-to-goland.sh
export HISTIGNORE='*sudo -S*' tells bash history to ignore caching any command matching sudo -S* to bash history. This way, your sudo-password isn't saved into the bash-history file.
echo "sudo-password-here" | pipes your sudo password as input to the next command.
sudo -S tells bash to read input for password prompt from stdin, which has been provided through the echo command.
Alternatively, you can just install the latest version of Goland. Hopefully, it doesn't come with this bug
I am trying to flash my google coral dev board on the macos. I learned that Catalina wouldn't function for using the board, so I downgraded to Mojave. Everything goes smoothly, except when I type the command
bash flash.sh
Onto my terminal in the process of flashing my board. The terminal returns the command:
Couldn't find fastboot on your PATH -- did you install it?
I am sure I installed it. When I type fastboot devices or version on my terminal, it shows up correctly. And, when I echo path, this comes up
/Users/name/Downloads/fastboot:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
So I am sure that it is on my path also. Does anyone know the solution to this?
Try opening a new terminal and see if it is still in your path. If it is not in your path you can add it to ~/.bash_profile
sudo vim ~/.bash_profile
Add the line:
export PATH=${PATH}:~/.local/bin
Then when you open a new terminal it will still be in $PATH and bash flash.sh should work
I faced the very same issue as you, and the way I could run flash.sh to "flash" my Coral dev was by modifying the file (flash.sh) and added the path where fastboot was located.
(I'm a Mac user) This is how I did it:
I went to check the version of fastboot (It also gives you where is the file located at)
cd ~/.local/bin
then:
./fastboot --version
Command results:
fastboot version 30.0.4-6686687
Installed as /Users/jegamboafuentes/.local/bin/./fastboot.
Then I went to the flash.sh file, open it and modify the line 19:
FASTBOOT_CMD="$(which fastboot)"
for:
FASTBOOT_CMD="/Users/jegamboafuentes/.local/bin/./fastboot"
I re-run, and BOOM! it worked, my Coral Dev Board was flashed.
Check your model number using the reference here. If it was manufactured before April 10, 2019, then there are some steps for you to follow.
Similarly, make sure you download the latest fastboot version here. Fastboot should be version 28.0.2 or higher. Hope this helps.
I'm following the tutorial on https://mjml.io/documentation/#basic-layout-example
And followed these instructions to install https://mjml.io/download
But whenever I want to use ./node_modules/.bin/mjml index.mjml or mjml index.mjml I get the following error:
Command 'sed' is available in '/bin/sed'
The command could not be located because '/bin' is not included in the
PATH environment variable.
sed: command not found
/usr/bin/env: 'node': No such file or directory
I have no idea what I'm doing wrong and Google hasn't been helpful so far.
Any idea why this is happening? Thanks for your time :(
Seems you have messed your PATH environment variable. The sed program is there as is part of the core packages. You can try to do something like the mentioned here.
Also try to reach the mjml support group in slack
I think you have not installed node properly. Try reinstalling it.
If you reinstalled the node and then also you are facing the problem then there is some problem with Windows because a few days ago I was facing a problem when I was running the npm run build command then I switch to my Virtual box Linux OS there it works fabulously.
I have been trying to get the NIST Biometric Image Software downloaded and running on a mac as I saw it would be easier than doing it on windows. I have it downloaded and have been trying to use the terminal to set it up, but it keeps saying it is unable to find it in the directory. I haven't worked with terminals much or anything of this magnitude. The input I am putting into the terminal is:
sh setup.sh <FINAL INSTALLATION DIR> [--without-X11]
With the final installation dir being the one I copied from the path where it is located. I am not sure if anyone has worked with this before, or had any similar issues to the one I have above. Any help would be greatly appreciated as I am kind of lost on this.
Open terminal then cd /Path /to/where/your/NISTsoftware/directory/is
Afterwards give it execute permussions by running this on terminal chmod 755 setup.sh
Then execute it so that you can install your NIST software by running ./setup.sh
I've been trying to figure out this problem for a while now and I thought I'd ask it here on stackexchange in case somebody out there has tried this and successfully got it to work.
I'm trying to install a RAD webapp tool called AppFlower through Xampp for Linux.
I am also experiencing issues with the command below:
symfony afs:init
symfony: command not found
This is the final command used to start up the AppFlower Studio dev environment, but this command doesn't work.
I have tried using:
./symfony afs:init
Same error as above
php ./symfony afs:init
gives a php error saying it isn't installed, but this is Xampp for Linux, so that command won't apply
/opt/lampp/etc/php.ini ./symfony afs:init
it will give a permission denied error, but even with 'sudo' in front, it says 'command not found'
The solution posted on the appflower forum is for xampp itself, but the problem I have is that they use the php.exe command to run the 'symfony afs:init' command, which xampp for linux doesn't have. The closest thing I could think of was to use the php.ini file, but (as seen above) that doesn't work.
Hopefully somebody can assist regarding this issue.
Regards,
Note. The process to run appflower on a manual version of lamp (one in which php, mysql, apache are all downloaded separately) is a lot more complex and the xampp installation is supposed to be much easier (in fact it is) but at the last point of this installation, this 'symfony afs:init' command is the only problem.
If you are already using Linux, why not install AppFlower directly. It's pretty straightforward, maybe i lost something on the way, understanding why you use XAMMP for Linux.
Installation instructions for AppFlower on Ubuntu,
http://www.appflower.com/doc/1_2/learn_install_git_on_ubuntu