-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
spacy 2.0.12 / thinc 6.10.3 crashing django on heroku #2631
Comments
@honnibal - does something obvious jump out at you? |
I was able to track down the underlying issue. It turns out that Heroku had simply aborted the thread because it was taking too long. I'll close this issue. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This may be a bug in my code somehow or it may be that I've run across a bug in spacy or thinc. I'm not sure yet.
I'm having an issue with
v2.0.12
that I've traced intothinc
.pip list
shows me:I have code that works fine on my Mac, but fails in production. The stack trace goes into
spacy
and then intothinc
-- and then django literally crashes. This all worked when I used an earlier version of spacy -- this has only come about since I'm attempting to upgrade tov2.0.12
.My requirements.txt file has these lines:
The last line pulls the
en_core_web_sm
down during deployment. I'm doing this so I can get those models loaded on Heroku during deployment.I then load the parser like this:
Then the stack trace shows the problem here in
thinc:
Again -- this all works on my laptop.
Is there something wrong with how I'm loading? Or is my version of
thinc
out of date? If so, what should myrequirements.txt
file look like?The text was updated successfully, but these errors were encountered: