Issues with cached poetry installation: bad interpreter, no such file

[snok]

Issues with cached poetry installation: bad interpreter, no such file

[miigotu]

I think if you specify your python version explicitly rather than 3.x, and set a new restore key for the cache your problem will go away. When you have one version of python installed and create an environment with that, and then a new python is added to GitHub actions your env breaks. Set 3.9.12 for example in your inputs.

[sondrelg]

Yeah that makes sense. Thanks @miigotu, I'll update my workflows too 😄

[connortann]

Thanks @miigotu and @sondrelg for the tips, I'll do as you suggest!

[JonasKs]

Awesome, thanks @miigotu 😊

[sondrelg]

Think this is a Github actions cache issue. It happens to me every few weeks 👍

[connortann]

Huh! Strange. Do you have any recommendations for preventing this failing in future, other than incrementing the cache?

[sondrelg]

Was on my way out and answered a little more briefly than I should have; what I should have said was:

I'm not exactly sure what happens, but it seems like the cache expires or something alone those lines. I don't think it has anything to do with Poetry, as Poetry in this equation is only the tool we use to generate and configure our virtual environment. The storing of the venv is wholly the responsibility of the cache action. At least that's how I see it 👍

I'm sure there are ways to auto-increment the counter if the cache actions fails, but I don't have a ready solution to suggest 🙂