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
I noticed that they exist because the lack of a hash value is causing the setup-micromamba GitHub action to fail with the following error:
Empty environment created at prefix: /home/runner/micromamba/envs/pudl-dev
critical libmamba either package 'package.info.hash.md5' or 'package.info.hash.sha256' must be specified, found none
Error: The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1
However, no packages named __osx or __glibc appear in the conda-lock.yml when I generate it locally using a similar command. The only obvious differences between the two environments are:
The GitHub runners are running Linux, and my local environment is on an M1 Macbook Pro
On the GitHub runner it is using conda-lock --micromamba while locally I'm using conda-lock --mamba. The command being used to generate the conda lockfiles / environment files:
zaneselvans
changed the title
Temporary local packages unexpectedly appearing in conda-lock.yml
Invalid/Temporary local packages unexpectedly appearing in conda-lock.yml
Nov 20, 2023
Checklist
What happened?
After updating to
conda-lock
v2.5.0 some odd new packages are showing up in ourconda-lock.yml
when it is regenerated via a GitHub action:I noticed that they exist because the lack of a
hash
value is causing thesetup-micromamba
GitHub action to fail with the following error:However, no packages named
__osx
or__glibc
appear in theconda-lock.yml
when I generate it locally using a similar command. The only obvious differences between the two environments are:conda-lock --micromamba
while locally I'm usingconda-lock --mamba
. The command being used to generate the conda lockfiles / environment files:conda-lock \ --${mamba} \ --file=pyproject.toml \ --lockfile=environments/conda-lock.yml
However, running the above commands locally using
--micromamba
does not result in the__glibc
or__osx
packages appearing inconda-lock.yml
Conda Info
Conda Config
Conda list
Additional Context
The text was updated successfully, but these errors were encountered: