Kevin Stillhammer
Kevin Stillhammer
Since there was no update I guess your issue was solved. Feel free to reopen if it persists
Hi. You are mixing up two things. This action will save the downloaded rye executable to `RUNNER_TOOL_CACHE` which on most runners is set to `/opt/hostedtoolcache`. If you want to use...
Given that it finds the tool somewhere in /opt but not the cache under /tmp I strongly suspect the Docker setup at fault here. I have the exact same configuration...
Try setting it to `opt/hostedtoolcache/setup-rye-cache` can't think of a reason why this should break something. But if you find something outside of `opt/hostedtoolcache` that works it would still be preferable
FYI: https://github.com/eifinger/setup-rye/releases/tag/v3.0.0
@my1e5 that looks strange. Can you please provide me the full log of the setup-rye and the Post setup-rye step? There is some cache-key mismatch
Thank you. I pushed a fix that will set `cache-hit` to true. I started out this action by copying the `setup-python` action which handles partial cache matches. That is not...
Have you tried the core integration? Support for Broadlink Thermostats was added a while ago https://www.home-assistant.io/integrations/broadlink/#climate
I just encountered the same problem in a project using rye with uv enabled. 1. Have a project using a dependency in `pyproject.toml` in the form of ` @ git+ssh://[email protected]//.git@`...
Temporary workaround for me is `UV_NO_CACHE=true rye sync`. I have not yet used `uv` directly but for the initial problem @elupus reported this should work `UV_NO_CACHE=true uv pip install --verbose...