Closed vrslev closed 2 days ago
I had exactly the same issue with a different tool.
After mise x -- tuist
and mise x -- sourcery
failing on me, I tried explicitly calling mise use tuist
which informed me that .mise.toml
wasn't trusted, and I could trust it with mise trust
in the directory.
Since doing that, mise x -- tuist
and mise x -- sourcery
are working again, thankfully!
I don't think that's the case here since it's showing up in mise dr
as a config file. Is there an empty install? What's in ~/.local/share/mise/installs/ripgrep/latest
?
I can't seem to reproduce this. I tried ctrl-c'ing during the install and every time it doesn't show up as an install if it only partially completes as it should.
@jdx I think the issue isn't what OP @vrslev initially thought, but is actually due to changes around trusting .mise.toml
files. I had the exact same error message, and it was resolved by running mise trust
in the directory which, as of Friday, was working OK.
if mise wasn't trusting a config file it wouldn't be listed in mise dr
I don't think that's the case here since it's showing up in
mise dr
as a config file. Is there an empty install? What's in~/.local/share/mise/installs/ripgrep/latest
?
It's contains an empty bin
folder
I'm not sure how that happened but does it occur if you reinstall? mise install -f ripgrep
?
That helped, thanks. Should I close the issue?
Describe the bug There's some issue with ripgrep in registry: it doesn't get installed
To Reproduce
Expected behavior Expected to install ripgrep. Now it outputs this:
mise doctor
output(really nice that I didn't have to strip sensitive data from
mise doctor
output 👍)Additional context Nope :)