-
Notifications
You must be signed in to change notification settings - Fork 268
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
feat: show lima version #3748
feat: show lima version #3748
Conversation
let provider; | ||
if (fs.existsSync(socketPath) || fs.existsSync(configPath)) { | ||
provider = extensionApi.provider.createProvider({ | ||
name: 'Lima', | ||
id: 'lima', | ||
status: 'unknown', | ||
version, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be better to update the version when you've the result and not hold the activate method
activate method should be a 'fast call', (as we wait the ending of the activate method on all extensions before showing the UI)
so probably, in activate you register the provider, then asynchronously you grab the version and call provider.updateVersion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a local binary, but sure. (i.e. it takes 50 ms to run, unlike podman version
which takes 5 seconds)
af69b3b
to
88abcec
Compare
Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
88abcec
to
b5fd055
Compare
What does this PR do?
Finds the location of the
limactl
binary, and show the version of Lima.Screenshot/screencast of this PR
What issues does this PR fix or reference?
How to test this PR?
brew install lima
limactl start template://podman