Closed aamkye closed 2 months ago
don't manage git with mise, it's a bad idea
@jdx can you elaborate on that? And/or may it be related to this issue?
the asdf plugin is calling git which since it's managed by mise requires launching mise then git again ending up in an endless loop
Ahhhh, so the loop comes from there.., got it, issue, to be closed. You could use this issue in the documentation as a caution for others, "what could happen".
Describe the bug I've noticed that when entering a repository with top-level
.mise.toml
that has “outdated” versions against system-wide.mise.toml
it starts creating system forks, that easily hits max processes limit, and forces me to reboot my system. It seems like Mise is trying to fetch the newest versions — which is okay. But the problem starts whenever there is a network change event — like VPN server switching IPs.I've figured it out, to raise the limits:
But I think this is not expected behavior to spam this number of forks.
It seems like this might be a problem:
To Reproduce Steps to reproduce the behavior.
Expected behavior Mise does not create such number of forks/subprocesses.
mise doctor
outputAdditional context
This is usually around 660-700:
However, can raise up to this: