Closed liquidcarbon closed 1 year ago
just found that each execution attempt created a new environment in:
ll ~/micromamba/envs/metaflow/linux-64/ total 44 drwxr-xr-x 11 a a 4096 Oct 19 12:58 ./ drwxr-xr-x 3 a a 4096 Oct 19 12:34 ../ drwxr-xr-x 13 a a 4096 Oct 19 12:58 0d7472272e27b0c/ drwxr-xr-x 13 a a 4096 Oct 19 12:52 21a849a71a17fcd/ drwxr-xr-x 12 a a 4096 Oct 19 12:34 7264f22a78a4409/ drwxr-xr-x 13 a a 4096 Oct 19 12:35 7bd8def62c9d5d5/ drwxr-xr-x 12 a a 4096 Oct 19 12:57 91bcc23b46dd043/ drwxr-xr-x 13 a a 4096 Oct 19 12:39 9db3d6f40db3e76/ drwxr-xr-x 12 a a 4096 Oct 19 12:38 c0dca06c9139377/ drwxr-xr-x 12 a a 4096 Oct 19 12:34 d2bfadb458f041e/ drwxr-xr-x 13 a a 4096 Oct 19 12:48 db23aaf3108b082/
and in 0d7472272e27b0c/lib/python3.9/site-packages/
there is the requested editdistance
, but somehow metaflow is not actually using that environment
It's surprising that @pypi
is using micromamba pip to install things. Why not regular pip from the same environment as python
executable? Isn't it possible to steer clear of all serpents?
https://github.com/Netflix/metaflow/pull/1581 related? @savingoyal
@liquidcarbon we are triaging this
Tried to run two
@pypi
-decorated flows: 1) FractalFlow from https://docs.metaflow.org/scaling/dependencies/libraries 2) modified Playlist plus, swapping conda for pypiIn both cases, the flow errors out, saying the requested package is not found. What am I doing wrong?
thanks!
returns
Notice the printout for
sys.path
(marked with**
): the micromamba environment that attempts pip install is absent:(that's why I changed to
editdistance==0.6.2
)