Failed to update dependencies: Current version of 'kubectl' binaries does not match expected version

[MartyPointer-HTA]

Updating plugin to version 2.0.120231128 stops Bridge to Kubernetes from running.

Mention the platform you are using
VS Code V1.84.2

To Reproduce
Steps to reproduce the behavior:

1. Install or upgrade to Bridge to Kubernetes plugin V2.0.120231128
2. Run Bridge to Kubernetes via a launch.json file
3. VS Code displays a toast showing the screen shot below (which contains the message "Failed to update dependencies. Current version of 'kubectl' binaries does not match the expected version")
4. Bridge to Kubernetes cannot be configured

Expected behavior
Bridge to Kubernetes should create a restore pod and redirect K8s traffic to the application hosted in VS Code

Screenshots

Logs:
Log files in C:\Users\Username\AppData\Local\Temp\Bridge To Kubernetes do not report any problems. bridge-mindarocli-yyyy-MM-dd-hh-mm-ss-xxxx.txt log files contain 2 entries for Command.Start and Command.End.
Command.End = "Result":"Succeeded"

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 119.0.6045.200

Additional context
Trying to manually install the dependencies via the supplied link does not fix the problem
Upgrading installed version of kubectl does not fix the problem
Seen on 3 separate dev PCs
Reverting to the previous version of Bridge to Kubernetes (V2.0.120231004) is the work-around

[hsubramanianaks]

@MartyPointer-HTA Thanks for raising this concern. Can you check now it is updated and should not give this error. Please let me know.

[hsubramanianaks]

@MartyPointer-HTA Can you please confirm this is working ? if so, we can close this issue. Please let us know if there are any other further issues. Thank you.

[erceth]

I'm having a similar issue. Isn't 2.0.120231128 the latest?

Mine says failed to update dependencies but doesn't give an error after.

I'm on an M1 mac.

[hsubramanianaks]

@erceth this is known issue, and it is caused due to codesign is required on M1 mac which is being worked on. Link here. Only work around for now is revert to older version or explicitly do codesign -s - ~/Library/Application\ Support/Code/User/globalStorage/mindaro.mindaro/../bridge/dsc and then retry the dependencies.

[MartyPointer-HTA]

@MartyPointer-HTA Can you please confirm this is working ? if so, we can close this issue. Please let us know if there are any other further issues. Thank you.

Hi @hsubramanianaks, apologies... I assumed the update would be in the form of a new release version and was waiting for it to appear. I can confirm I have re-insalled v2.0.120231128 and no longer see the problem.

Thanks
Marty

[credo7]

Hello, codesign worked, but have another error now
Everything goes fine but the last step

Waiting for EndpointManager to come up ...
An unexpected error occurred: 'Failed to launch EndpointManager.'

@hsubramanianaks

[hsubramanianaks]

@credo7 This is also known issue which is being investigated on. you are seeing this only after updating to latest, previous versions didn't give this error right ? Alternative you can use service environment variables approach which actually works fine. Apologies for this interruption, we will soon have a release to fix these issues. Thank you.

[hsubramanianaks]

@credo7 Can you please share your logs when EndpointManager fails. I am able to replicate it but trying to find the root cause of the failure. are you seeing this error ??

 | Library | TRACE | Launch output: 
 | Library | TRACE | Launch output: Process has exited with exit code 0
 | Library | TRACE | Waiting for EndpointManager to come up ...\n
 | Library | TRACE | Connecting to EndpointManager
 | Library | TRACE | EndpointManager is not running: 'Can't assign requested address'

Thank you.