When building environments where are the package h...
# ask-metaflow
c
When building environments where are the package hashes stored locally? I can't figure out where to clear whatever cache it's using.
Copy code
Pretty-printed STDERR:
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    eru==0.1.1 from <https://valar-pypi-server.com/eru/eru-0.1.1-cp38-abi3-macosx_11_0_arm64.whl#sha256=81bd73394af489f7377aa2f247d9b4448b5778c029959ba02296fa68ffeb43fe>:
        Expected sha256 81bd73394af489f7377aa2f247d9b4448b5778c029959ba02296fa68ffeb43fe
             Got        d05270c62dee5bccbaac5ccba9f72b8db7c8fc9d9bbfe4d00c5a24f398fb77a5
1
a
the packages are in s3. you may want to check your local .metaflow folder for local metadata cache
@dry-beach-38304 any pointers - this is likely using nflx-extensions
d
this is not an error from the nflx-extensions. This looks like a pip error directly.
and indeed:
Copy code
(metaflow-ossdev310) --($:~/Downloads)---$ gsha256sum eru-0.1.1-cp38-abi3-macosx_11_0_arm64.whl                                                                                                                                                                                                <aws:assume-oleg2>
d05270c62dee5bccbaac5ccba9f72b8db7c8fc9d9bbfe4d00c5a24f398fb77a5  eru-0.1.1-cp38-abi3-macosx_11_0_arm64.whl
what are you doing to get this error?
I don’t know where 81bd… is coming from.
c
We are working in building some rust libraries and then installing them. At the moment we are iterating and often create a new wheel with the same version number. However it has a different hash, and I can't figure out where pip is storing the cache because it says cache is disabled.
d
but are you installing it with the @conda or just manually?
if you are using @conda `and the netflix extensions, please re-run with METAFLOW_DEBUG_CONDA=1 and that may give a few more insights.
c
It's definely a pip thing, I can recreate it outside of metaflow. pip is somehow storing the hash of the package somewhere and using it when doing a new install. Even if I uninstall the package and reinstall it has a hash mismatch.