-
Notifications
You must be signed in to change notification settings - Fork 143
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
uv: unrecognized subcommand 'self'
#942
Comments
Thanks for the report! cc @lucaspar, from the doc, looks like the self-update feature is only available if your
Hopefully, we can find a way to check if an installation is done in such a way, or we have to remove this operation🤔. |
This issue is quite similar to #892, see this comment. |
Oh, I just realized that even though this issue is similar to that one, but this one is pretty easy to fix, we can simply check if the self update sub-command exists or not, and only involve it if exists |
You should use the package manager that installed
See the comment in https://github.com/topgrade-rs/topgrade/blob/main/src/steps/generic.rs#L1034-L1044 |
Hmm, just found we already ignored the execution result of that command, perhaps we should hide the output as well? |
I chose to not hide it because
If we're trying to improve UX, maybe we can add a custom log message from topgrade on error to tell the user that this "error" is (probably) ok. |
A different route is to try |
This is what I think, we try the command |
I think the current solution is good. But personally, I'd rather ── 16:07:35 - uv ───────────────────────────────────────────────────────────────
error: uv was installed through an external package manager, and self-update is not available. Please use your package manager to update uv.
Nothing to upgrade |
It's listed because uv-installed tools are updated regardless of uv's installation mode. |
This is also feasible as we can check if it is installed through the official scrip via |
Erroneous Behavior
It's trying to update
uv
withself update
Expected Behavior
Update
uv
Steps to reproduce
topgrade run uv
Possible Cause (Optional)
I don't believe
self
is an option foruv
Problem persists without calling from topgrade
Did you run topgrade through
Remote Execution
If yes, does the issue still occur when you run topgrade directlly in your
remote host
Configuration file (Optional)
Additional Details
macOS 15.0.1
homebrew
topgrade -V
)topgrade 16.0.1
Verbose Output (
topgrade -v
)The text was updated successfully, but these errors were encountered: