Skip to content
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

[BUG] Error when tagging Sherpa due to spaCy trained pipeline for English not being installed #332

Closed
artificialfintelligence opened this issue Apr 6, 2024 · 2 comments · Fixed by #337
Labels
bug Something isn't working

Comments

@artificialfintelligence
Copy link
Contributor

Describe the bug
Manual installation instructions and Dockerfile are missing a newly required step: Downloading the spaCy trained pipeline for English.

To Reproduce

  1. Perform a fresh installation of Sherpa following the directions here or a fresh redeployment of the docker container.
  2. When you tag the Sherpa slack bot, it fails with the following error message in the console:
OSError: [E050] Can't find model 'en_core_web_sm'. It doesn't seem to be a Python package or a valid path to a data directory.

Also in Slack, you get the following error:
image

Additional context
The culprit is PR #273, specifically this commit.
It is easily fixed by performing the following command (to be added to the manual installation instructions, as well as, more importantly, the Dockerfile):

python -m spacy download en_core_web_sm
@artificialfintelligence artificialfintelligence added the bug Something isn't working label Apr 6, 2024
artificialfintelligence added a commit to artificialfintelligence/sherpa that referenced this issue Apr 6, 2024
@artificialfintelligence
Copy link
Contributor Author

@20001LastOrder I ran this by @Eyobyb and created a PR with the fix

20001LastOrder added a commit that referenced this issue Apr 7, 2024
@20001LastOrder
Copy link
Collaborator

Fixed by #333

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants