-
-
Notifications
You must be signed in to change notification settings - Fork 459
mise use
adding tool options from backend
#4842
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
Comments
mise up
adding tool options from backendmise use
adding tool options from backend
What exactly is the expected behaviour? Currently the default backend for
The Is this issue about applying these registry options automatically by default? |
ok I was able to repro on a different machine (mise 2025.4.4): ![]() Looks like for some reason doctor:
|
it's 384e35e:
|
Fixes #4749 --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
it's very weird this seems to be importing backend options from the non-default and default registry backends. I added
So I think this exposed 2 bugs, first that we're using more backends than we should but also that backend options are ending up in mise.toml. |
I think fixing this is going to be tricky since it basically means our method of adding the backend tool options on the tool will import things into the file |
AFAIR backend options from |
I'll think about this one a bit unless you have a good idea. I'm wondering if we should abort this plan to merge and instead find a way to pull in the tool options in the version listing |
though... in theory you could have a mise.toml like this: [tools]
foo = [
{version = "1", options = "x"},
{version = "2", options = "y"},
] so our data model may not support putting the options in version listing at all |
update: neither me nor @roele can repro in a container. I'm going to see if I can repro in a container or e2e test. |
I thought this was fixed but apparently not
The text was updated successfully, but these errors were encountered: