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

Unable to run gauge in debug mode #2338

Open
deepesh1511 opened this issue May 10, 2023 · 3 comments
Open

Unable to run gauge in debug mode #2338

deepesh1511 opened this issue May 10, 2023 · 3 comments

Comments

@deepesh1511
Copy link

deepesh1511 commented May 10, 2023

Describe the bug
Unable to run gauge in debug mode when the first debug session is stopped or closed.
To Reproduce
Steps (or project) to reproduce the behavior:

  1. Initialise a gauge-java-maven project
  2. Run the scenario in debug mode using Debug Scenario option on spec file
  3. Let the debugger stop at a breakpoint.
  4. Stop the debugger.
  5. Run the scenario again (same or different) in debug mode using Debug Scenario option on spec file
  6. VS code wont allow to start the debugger again

Logs

Screenshots

Error Message
image
image

Launch JSON
image

Expected behavior
Debug Scenario on second run should work.

Screenshots

Versions:
image

  • OS - Windows 10 Version 21H2 for x64-based Systems (KB5026361)
  • Runner info - Java
  • IDE info - VS code 1.78.1
@deepesh1511
Copy link
Author

@zabil Can you please look into this issue and suggest?

@zabil
Copy link
Member

zabil commented May 12, 2023

@deepesh1511

Thank you for reaching out.

I wanted to let you know that as the project is currently not actively maintained by me, my personal time to delve into specific issues is quite limited. The project largely depends on the contributions and support of our amazing community of volunteers.

We have a wonderful community here, and I'm confident that others who may be facing this same issue will soon chime in with their insights or solutions. Your patience while waiting for these responses is greatly appreciated.

In the meantime, any attempts to debug or fix the issue on your end would be immensely helpful. Not only would this possibly provide a quicker resolution for you, but it could also greatly benefit others who may encounter the same issue in the future.

Thank you again for understanding and participating.

@deepesh1511
Copy link
Author

Thank you @zabil

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

No branches or pull requests

2 participants