-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python -m spacy.en.download no longer valid? #45
Comments
Hi, yep spaCy moved to v2.0. If it works, could you please submit a pull request with the changes in the setup file? |
I see. I'll try to get it working, although in the file Does this mean though that if a language doesn't have the "_md" module it won't be possible to use the bot with that specific language? |
Also, even changing all files where the outdated command was used (6, IIRC), I'm still getting an error when launching
And then the script restarts 10 times until it fails. In the log file (production.log, since development.log is empty) I have this:
|
oh that's no longer a spacy issue, it's now a token issue with the config file. What services are you using? (slack bot, ngrok, fb messenger)? |
I'm using slack, following your blog's advice. You think the issue might be with the bot's token? |
ahh, unlikely it's Slack. On the config file |
I get the same output |
did some digging, seems like an error towards your slack token. See the source of error method |
gotta run will look again evening if it's still erroring, thanks for ur patience |
My token starts with |
Okay, I managed to "move on", and get new error messages. I did a clean reset (recloned the aiva folder and -hopefully- fixed most of the python code related to the outdated linguistic models), and now the
[Thu Nov 16 2017 08:05:14 GMT+0000 (utc)] ERROR Traceback (most recent call last):
File "/home/scevola/aiva/lib/py/convo_classifier.py", line 5, in
I highlighted the ones I think are the 2 main errors (hope it doesn't look too ugly). The first still has to do with spaCy's module. I didn't know how to fix line 2 of This is the content of
|
great to see u made progress :)
if which conda >/dev/null; then
echo "Conda is already installed"
else
curl -O https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash Miniconda3-latest-Linux-x86_64.sh -b -u
fi
conda create -n aiva python=3.6 -c conda-forge -y
# every time when u use it, active the python3 environment in your terminal session:
source activate aiva
# now u can run the installations and AIVA commands from.
pip install -r requirements.txt
# ... install spacy and things u did earlier
# to deactivate, just do this from within the environment
source deactivate Shd fix problem 1.
Let me know how this goes! |
I'm unsure at what point I should run the code you sent. I tried running it in the terminal, but line 7 gives an error |
oh just start a new terminal session to install Conda, it's from this. You're on linux right?
Then open a new bash session and check |
Yes, I'm on Linux, Ubuntu 16.04 :) |
rerunning the setup file is fine, it only updates on existing ones. The bottom of this issue had similar encounter with socketIO, might be worthwhile to look. Meanwhile let's debug it in a hacky way.
show the logs from both windows pls? |
I am now getting an error at step 1. In terminal it shows (sending only the last lines)
And in the npm log file
|
Also, I checked out issue #22 and (to the best of my skills, not being familiar with the python environment), I excluded python from
In the second one I get this
Every time I send a message to the bot |
Any new ideas/suggestions? |
could u update |
I think I'm bumping into a related bug. I cloned the repo, followed the setup without deviating. npm start fails with
|
Is it supposed to be |
looks like websocket is installed If I open a python shell with |
yeah it's |
I have not tried that. I'm pretty inexperienced with python, so this is probably just an issue with my system, rather than a bug with the project. I haven't done anything with virtualenv. But no worries about sorting this one out. I'm working with Rasa atm. |
@kengz - looks like i have a similar problem. I did follow the instructions mentioned above to update scripts as per spaCy 2.0. and use custom conda env But still getting this error
|
Running the line of code no longer download the spaCy's models, because there are now three different ones: en_core_web_sm, en_core_web_md, en_core_web_lg, en_vectors_web_lg.
Which one (if any) is the correct one to download during setup, and should the setup file be changed at line 125 in order to follow the change?
The text was updated successfully, but these errors were encountered: