-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
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
KeyError: 'pkgs_dirs' #732
Comments
Hey there @valeriupredoi! Working on an OSS project with a visible workflow makes this a whole lot easier than usual to diagonse! 😁 I'd recommend adding a workflow dispatch trigger to give you the following button: I think this is probably due to Micromamba v2. Experiment in progress at |
ah interesting, cheers, Ben! Will go there now 🍺 |
It was indeed v2: ESMValGroup/ESMValTool#3771 I'm a bit concerned about the KeyError reported above. This needs more investigation. |
click
and conda-lock
on Github Actions machine
Thanks so much @valeriupredoi for the bug report! It turns out it was an obscure bug in conda-lock, triggered from a side-effect of the upgrade. In this case mamba v2 was not at fault. Once I release conda-lock v3 you can unpin mamba. |
excellent @maresb - glad I could help, and well done for figuring out what the actual problem was! Many thanks, I will make a note for us, so we unpin mamba as soon as v3 comes out. Also, close this then? 🍺 |
ah nvmd, just saw #733 is still open 👍 |
Hi @maresb Ben, we're seeing this failure at creating a linux64 conda lock file:
pyhd8ed1ab_0 conda-forge
unix_pyh707e725_0 conda-forge
conda-lock lock --platform linux-64 -f environment.yml --mamba --kind explicit
Unfortunately I can't reproduce this on my local machine (ie all works fine, with same dependencies), but it is 100% reproducible on the Github Actions machine. Any clues? Many thanks in advance! 🍻
The text was updated successfully, but these errors were encountered: