Skip to content
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

Gauge extension loses executable on vsCode version 1_92 #989

Open
spll19 opened this issue Aug 2, 2024 · 7 comments · May be fixed by #990
Open

Gauge extension loses executable on vsCode version 1_92 #989

spll19 opened this issue Aug 2, 2024 · 7 comments · May be fixed by #990
Labels

Comments

@spll19
Copy link

spll19 commented Aug 2, 2024

Type: Bug

Good day!
after update vsCode to version of https://code.visualstudio.com/updates/v1_92

gauge extension shows error like "vscode gauge executable not found"
and user loses an option of starting spec or scenario

this message is written from version https://code.visualstudio.com/updates/v1_91
windows 11 system
(executable works fine)

Best regards!

Extension version: 0.1.6
VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.22621
Modes:

@Zoupers
Copy link

Zoupers commented Aug 5, 2024

The official release doc https://code.visualstudio.com/updates/v1_92#_electron-30-update might help.

@chadlwilson
Copy link
Contributor

Thanks @Zoupers - that seems likely to be the problem here.

@chadlwilson chadlwilson added the bug label Aug 5, 2024
@Zoupers
Copy link

Zoupers commented Aug 5, 2024

@chadlwilson I have created a pr #990 to solve it and tested it on my local machine. Could you please help review it?

@Tochemey
Copy link

Hello, please how long will this fix take to be in the next release?

@chadlwilson
Copy link
Contributor

chadlwilson commented Aug 13, 2024

Not sure.

If you have a problem you can likely workaround it by installing gauge from zip or installer rather than npm package.

@usernamedd

This comment was marked as resolved.

@usernamedd

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

5 participants