We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
causes [Errno 57] Socket is not connected error on multiple calls (at least on OSX).
You can "fix" this by removing the shutdown code in ner/utils, but perhaps it should be addressed more methodically.
The text was updated successfully, but these errors were encountered:
changed the way that SocketNER retrieves data from the socket server;…
42ed5c8
… may address issue dat#14 and issue dat#11.
No branches or pull requests
causes
[Errno 57] Socket is not connected
error on multiple calls (at least on OSX).
You can "fix" this by removing the shutdown code in ner/utils, but perhaps it should be addressed more methodically.
The text was updated successfully, but these errors were encountered: