I am trying to use https://github.com/amzn/pecos in amazon sagemaker. I follow the readme of pecos to install it using amazon terminal. Then one can see the package is installed from terminal:
However, the package can not be used in a sagemaker:
So, why this happened and how to fix it?
P.S. I use the same way to install https://github.com/facebookresearch/fastText and it can run in a sagemaker jupyter notebook.
It seems like the latest 2.6.1 version is not yet available at Docker Hub
I defined it as follows in Dockerfile and it fails to pull it:
FROM ruby:2.6.1
The official repo for Docker ruby image was updated just 2 days ago to 2.6.1.
Any ideas ? Thank you.
You can get old ruby image form PPC64le.
https://hub.docker.com/r/ppc64le/ruby/tags?page=1
PPC64 explain that in this article.
https://en.wikipedia.org/wiki/Ppc64
I am using "MacOS High Sierra".
I installed the aws cli tool a long time ago, don't remember how I installed it.
The installation is a little unusual.
I can run aws from any folder, this is working
$ aws --version
aws-cli/1.11.121 Python/2.7.13 Darwin/17.4.0 botocore/1.7.12
However running
$ which aws
this returns nothing.
I thought it might be an alias, but running
$ alias | grep aws
This also returns nothing.
Its not installed with homebrew either
$ brew list | grep aws
The reason why this is a problem, because there have now been a few cli programs I have ran (Including "AWS Sam" and a build script from my work) which are complaining because aws is not in the path.
I would much rather have a "regular installation" of the aws cli, where I put the executable in some bin folder and then put it in the environment path.
But instead its using some "magic" which I am unfamiliar with. And not even AWS owns tools ("AWS Sam") seem to like the way its installed.
Any advice would be appreciated.
I solved the problem by running
$ pip uninstall awscli
$ brew upgrade
$ brew install awscli
Now I get this result
$ which aws
/usr/local/bin/aws
"AWS Sam" and the other build script I use at work are now working.
I want to install duckling to work on Rasa nlu training but it is giving issue as mentioned in below image please help me to fix this.enter image description here
As a suitable alternative would you consider running Rasa NLU in docker. The rasa/rasa_nlu:latest-full docker image includes duckling. If you wanted to get started with it and you have docker installed you should be able to just run
docker run rasa/rasa_nlu:latest-full
Then you can interact with Rasa over it's HTTP API https://github.com/RasaHQ/rasa_nlu#example-use
The docker file allow's more complicated setups like over writing the default config file and saving the logs/models/etc to a persistent disk
https://github.com/RasaHQ/rasa_nlu#advanced-docker
I had the same issue! This is basically the issue of jpype modules.
You need to first install the jpype in your environment.
you can use conda install -c conda-forge jpype1
For installing the jpype you can also refer to
official link for jpype installation.
On successful installation of jpype duckiling can be installed using
pip install duckling -U
I hope this would help!
You should download VC+ compiler for windows and then try the pip install.
You can download it here
https://download.microsoft.com/download/7/9/6/796EF2E4-801B-4FC4-AB28-B59FBF6D907B/VCForPython27.msi
I have installed elastic search and its plugin head but when i enter the
**url
"localhost:9200/_plugin/head/"**
It does not shows any thing?
And I have also install marvel/SENSE for monitoring purpose.
I have installed plugin/head using
sudo elasticsearch/bin/plugin -install mobz/elasticsearch-head
But its also not working .
Error: console not found on url
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/sense_widget.html?snippets/010_Intro/10_Info.json
BTW I am new to elastic search.
So if you could tell me why it is not showing anything or have i made any mistake.
Thank in advance!
If someone tries with version 5 or else:
for Elasticsearch 5.x: plugins are not supported. Run elasticsearch-head as a standalone
for Elasticsearch 2.x – 4.x:
sudo elasticsearch/bin/plugin install mobz/elasticsearch-head
for Elasticsearch 1.x:
sudo elasticsearch/bin/plugin -install mobz/elasticsearch-head/1.x
for Elasticsearch 0.9:
sudo elasticsearch/bin/plugin -install mobz/elasticsearch-head/0.9
From GitHub
I've just installed ES using 1.4.4. on windows. Please check if you've got the confirmation that the plugging is installed. Also double check your commands. See below.
The following are what I used on my Ubuntu 14.04 elasticsearch 2.0.0.
instead of -i, you need to use the word install ( without dash )
with proxy:
/opt/elasticsearch/bin/plugin install -DproxyPort=80 -DproxyHost=www.example.com mobz/elasticsearch-head
without proxy:
/opt/elasticsearch/bin/plugin install mobz/elasticsearch-head
Updating the already existing answers for CentOS/RHEL 7.
Since v5.x the ElasticSearch Head plugin is deprecated and es-head must be run as a standalone server. Here's how to install on CentOS/RHEL 7.
First, install Node.js and Git.
Then run these commands:
git clone git://github.com/mobz/elasticsearch-head.git
cd elasticsearch-head
npm install
npm run start
Assuming that your ES installation runs on http://localhost:9200/, you can now access es-head on http://localhost:9100/.
If you have to use proxy to access external websites, you can the following command to install it:
bin/plugin -i -DproxyPort=80 -DproxyHost=www.example.com mobz/elasticsearch-head
You can also run elastic-search head as a chrome extension "ElasticSearch Head". Click the extension icon in the toolbar of your web browser after installing.
If you are on Ubuntu 16.04 or any other version, This command will surely run,
elasticsearch/bin/plugin install -DproxyPort=80 -DproxyHost=www.example.com mobz/elasticsearch-head
You can create systemd unit with npm run start. Like this:
[Unit]
Description=Elasticsearch-head
After=syslog.target
After=network.target
[Service]
ExecStart=/usr/bin/npm run start
WorkingDirectory=/usr/share/elasticsearch/elasticsearch-head
Restart=always
StandardOutput=syslog
StandardError=syslog
User=user
Group=user
[Install]
WantedBy=multi-user.target