You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that having a running dask client scheduler means that the individual workers cannot get called (get_workers() returns None), and trying to load a spacy/scispacy model installed in the activated environment means the workers cannot access the model. Running the non-client dask routines seems to work fine, if slower.
This seems in contrast with the "closed" issue/workaround here: explosion/spaCy#5111
The Code here is built around trying to use that workaround for a decorator factory, to allow arbitrary functions. Not currently working (may have to wait for spacy v3?).
The text was updated successfully, but these errors were encountered:
It appears that having a running dask client scheduler means that the individual workers cannot get called (
get_workers()
returnsNone
), and trying to load a spacy/scispacy model installed in the activated environment means the workers cannot access the model. Running the non-client dask routines seems to work fine, if slower.This seems in contrast with the "closed" issue/workaround here: explosion/spaCy#5111
The Code here is built around trying to use that workaround for a decorator factory, to allow arbitrary functions. Not currently working (may have to wait for spacy v3?).
The text was updated successfully, but these errors were encountered: