-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Error getting latest version for python: git failed #2962
Comments
Appears to be fixed with: rm -r ~/Library/Caches/mise/python/pyenv And running any mise command, such as |
The same solution works for the following warning:
I’m posting it here for those looking for the same problem and for historical consistency. Yet I don’t think it’s a good UX to expect users to know it’s a whole Pyenv repo cached somewhere underneath, often responsible for Python update hiccups. So, if we rely on the 3rd-party repo, should we consider Mise cleaning it occasionally then? But I’m not sure it’s enough of a suggestion for a separate feature request since “automagically” is never simple. |
the question is why is this happening. I don't know. If we could figure that out we could probably fix it. I'm certainly not in favor of just deleting it if it misbehaves. That's a good debugging step. It's not a good thing for mise to do it automatically.
I mean, if the issue is a missing remote we could probably fix it by adding the the remote without resorting to something so drastic |
Got the same message as a warning on ❯ git fetch --prune --update-head-ok origin master:master
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
❯ git remote -v
❯
❯ ls .git
FETCH_HEAD HEAD hooks index info logs objects refs |
I have this issue happening quite often. It seems that pyenv gets broken somewhat easily? |
I've noticed this happening when I try to get the latest python version in multiple processes/terminal tabs. I am seeing this error
I (think) I've fixed it by falling back to the git CLI by setting the |
I had to remove |
it could probably be fixed by adding a LockFile: https://github.com/jdx/mise/blob/main/src/lock_file.rs like we do for erlang: mise/src/plugins/core/erlang.rs Lines 39 to 48 in 5750630
|
I'm not super familiar with your codebase yet, but it sounds reasonable to me. Seems as though it would at least prevent the error from occurring. Does this mean the root cause relates to upstream dependencies (e.g., build tools such as |
Same issue after I switched to fish shell today. I don't even use |
Describe the bug
After updating to mise
2024.11.4
, I've started seeing the below error onmise ls
,mise doctor
, etc.To Reproduce
And run commands that require the Python checkout:
mise doctor
outputAdditional context
stderr
from abovemise doctor
withRUST_BACKTRACE=full
The text was updated successfully, but these errors were encountered: