-
Notifications
You must be signed in to change notification settings - Fork 338
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 could not initialize, unable to get Debug Scenario option #882 #2323
Comments
I upgraded my VDI machine configuration (from 2 core to 4 cores) and then I was able to load the project successfully. Is there any minimum system requirement to run the gauge smoothly? I also noted that Debug Scenario doesn't show up if the project is loaded with multiple different applications running in the background (Teams, outlook, chrome, edge) and occupying the CPU utilization. |
@zabil Can you please check and respond? |
There is no easy way for me to to test or replicate this. Hope someone else who faces this issue can respond. |
Description
I am unable to get
Debug Scenario
option on the spec files. This issue occurs in a specific scenario and I am able to reproduce the same multiple times.Environment Details
Extensions
Debugger for Java
v0.47.0
Extension Pack for Java
v0.25.7
Gauge
v0.1.0
Language Support for Java(TM) by Red Hat
v1.13.0
Maven for Java
v0.40.3
Project Manager for Java
v0.21.1
Test Runner for Java
v0.37.1
IDE
VS Code -
v1.74.3
Steps to reproduce
Unsuccessful attempt --
Successful attempt --
current runner is not compatible with gauge LSP
is not displayed inlsp.log
Expected Result
Debug Scenario should be displayed always, irrespective of CPU utilization.
Actual Result
Debug Scenario is not displayed always and project load depends on CPU utilization.
The text was updated successfully, but these errors were encountered: